Expand description
The feature list of a task: its locked acceptance tests (process-v1 §4,
contracts/process-v1/feature-list.schema.json).
The Spec Writer writes the list until G2. Once G2 has passed (Hive sets
spec_commit) the list is locked: only features[].passes may change, and
only the G6 gate writes it, from its own re-run. Any other change is a spec
change and goes back to spec; LeanCTX refuses it.
LeanCTX enforces the lock in two places:
crate::core::session_rightsrefuses every session write to a locked feature list file, whatever the role (a session is never the gate);apply_gate_passesis the one writer ofpasses, andvalidate_transitionrefuses any other difference between two versions.
Structs§
- Feature
- One acceptance criterion.
- Feature
List - A feature list as the contract defines it.
Enums§
- Writer
- Who writes a new version of the list.
Constants§
- MAX_
FILE_ BYTES - Largest feature list read.
- SCHEMA
- Schema id of a feature list.
Functions§
- apply_
gate_ passes - The gate’s write of
passes: set each named feature’s result and store the list atomically. Refuses a list that is not locked yet (no G2), an unknown feature id, and any result set that is not complete. - is_
repo_ relative - A repo-relative path or glob: not absolute, no
..component. - validate_
transition - Decide whether
writermay turnbeforeintoafter.