Expand description
The target-side landing model: file kinds, parameter rendering, and the routing block.
Every landable file has a declared kind — rendered files release-kit
owns and may rewrite, seeded files the target tunes, state files
the release automation maintains — and a rendered file’s bytes are a
deterministic function of the payload plus the landing parameters, so
a later command can compare what is on disk against what would be
written. The kinds are declared here, beside the payload, never
inferred at runtime; a test holds the table closed over every snippet.
Modules§
- invariants
- The invariants a seeded file still carries.
- manifest
- The landing record:
.release-kit/manifest.json.
Structs§
- Entry
- One artifact of the payload projection: what would land at one destination, with the payload bytes it was rendered from.
- Resolved
- What one detection pass resolved for a target-side verb, with the override flags applied.
Enums§
- Kind
- Who owns a landed file’s bytes after landing.
- Placement
- How a projected artifact occupies its destination.
Constants§
- AGENTS_
DESTINATION - The destination the routing block splices into.
- BLOCK_
BEGIN - The block’s opening marker.
- BLOCK_
END - The block’s closing marker.
- HOOKS_
BEGIN - The hook block’s opening marker, a YAML comment at column zero.
- HOOKS_
DESTINATION - The destination the hook block splices into.
- HOOKS_
END - The hook block’s closing marker.
- HOOK_
TYPES_ LINE - The top-level key the fresh hook file carries and the skills verify on an existing one: the commit-msg and pre-push hooks run only where their hook types are installed.
- OWNER_
TOKEN - The mechanical substitution sites in
renderedfiles. - SCOPES_
CSV_ TOKEN - The scope list, comma-joined: hook arguments and prose.
- SCOPES_
PIPE_ TOKEN - The scope list, pipe-joined: the title checks’ regular expression.
Functions§
- block_
markers - The markers of a block destination, or
Nonefor a whole-file one. - extract_
block - The marked block inside a document, markers included, or
Nonewhere the text carries no complete block. - hooks_
block - The hook block template, markers included, without a trailing newline and with its scope token unrendered.
- hooks_
file_ defect - The hook file’s defect, read from the target:
Nonefor a missing file or one the block can land in. - hooks_
marker_ defect - The one definition of an ill-formed hook file, shared by the splice and every reader that judges one.
- hooks_
splice_ refusal - The refusal a landing verb answers before writing anything, where the target’s hook file offers the block no place.
- kind_of
- The declared kind of a destination, or
Nonefor a file the payload does not classify. - pair_
files - The landable files of one
(technology, forge)pair, as(destination, payload bytes). - parse_
scopes - The
--scopesargument parsed into the recorded list. - projection
- The whole payload projection for one pair under the
repoandscopesparameters: every snippet with its kind and rendered bytes, plus the routing block and the hook block, sorted by destination. - read_
destination - The bytes an entry’s destination currently holds: the whole file, or
the marked block extracted from the target’s
AGENTS.md.Nonemeans the file — or the block — is absent. - read_
recorded - The bytes a recorded destination currently holds, by the placement its name implies.
- render
- Substitute the landing parameters into a
renderedfile’s bytes. - repo_
unresolved - The refusal a verb answers when it needs the
repoparameter and neither a flag nor the remote supplies one. - resolve
- Resolve forge and repository in one pass: the flags override, the
originremote answers otherwise. - routing_
block - The routing block template, markers included, without a trailing newline and with its scope token unrendered.
- splice_
agents_ block - The whole
AGENTS.mdcontent after splicing the rendered block. - splice_
hooks_ block - The whole
.pre-commit-config.yamlcontent after splicing the rendered hook block. - write_
destination - Land one entry: the whole file through the temp-plus-rename writer, or the block spliced into its document and the whole document rewritten the same way.