Module landing 

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

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.

OWNER_TOKEN

The mechanical substitution site in rendered files.

Functions

extract_block

The marked block inside a target’s AGENTS.md, markers included, or None where the file carries no complete block.

kind_of

The declared kind of a destination, or None for a file the payload does not classify.

pair_files

The landable files of one (technology, forge) pair, as (destination, payload bytes).

projection

The whole payload projection for one pair under one repo parameter: every snippet with its kind and rendered bytes, plus the routing 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. None means the file — or the block — is absent.

read_recorded

The bytes a recorded destination currently holds, by the placement its name implies: the marked block for AGENTS.md, the whole file otherwise. None means the file — or the block — is absent.

render

Substitute the landing parameters into a rendered file’s bytes: the repository’s owner — the project path’s first segment — replaces every OWNER occurrence.

repo_unresolved

The refusal a verb answers when it needs the repo parameter and neither a flag nor the remote supplies one.

resolve

Resolve forge and repository in one pass: the flags override, the origin remote answers otherwise.

routing_block

The routing block, markers included, without a trailing newline.

splice_block

The whole AGENTS.md content after splicing the block.

write_destination

Land one entry: the whole file through the temp-plus-rename writer, or the block spliced into AGENTS.md and the whole document rewritten the same way.