Module assess 

Classify a target repository before anything lands.

The assessment is read-only evidence plus one classification computed from it by an explicit rule: greenfield when the target carries no release mechanism and no release history, brownfield when a release mechanism is already in place — a tool’s configuration, a landed destination, a landed block — and needs-decision when the target shows release activity that no recognized mechanism explains: tags with no tool behind them, or a second long-lived branch. The rule lives here so a routing skill reads a verdict it can cite instead of judging “some release setup” by feel. The gathering spawns git and reads the disk; the rule itself is pure and unit-tested.

Structs

Evidence

The evidence the classification is computed from.

Facts

The repository’s facts alone, with no record read: what the planner gathers beside its own read of the record.

Landing

The landing record’s presence, the one fact rk status owns that the routing needs before it reads the full report.

OwnLanding

What marks release-kit’s own landing at a target that carries no record: the evidence the adoption detector reads.

Enums

Classification

What the target is, for routing: the corpus verdict, computed from the repository’s evidence alone.

Standing

Where a target with no record stands, by the precedence rk status reads it with.

Unrecorded

Where a target with no record stands, by the one rule above and the adoption detector before it.

Constants

LONG_LIVED_BRANCHES

Branch names that conventionally outlive a topic.

RELEASE_MARKERS

Files that mark a release mechanism, whichever tool owns it.

Functions

classify

Compute the verdict from the evidence. Pure, so the rule is testable without a repository.

classify_unrecorded

Classify a target with no record.

gather

Gather the evidence at target, reading and never writing.

gather_facts

Gather the repository’s facts at target, the record aside.

git_work_tree

Whether target sits in a non-bare Git work tree.

long_lived_among

The long-lived branch names among refs, given as full ref names.

own_landing

Find release-kit’s own landing at target, reading and never writing.

standing

Read where a target with no record stands: an open migration first, then the adoption detector and the assessment’s rule.