Repository navigation
v0.3.117
Design-lane hardening, found by a live stockflow run and fixed on evidence:
- Fan-out + browse gates now actually fire. The test-strategist fan-out and ux-designer browse provenance are spec-gate conditions that read the PERSISTED
.consort/agent-log.jsonl. The 0.3.116 fan-out gate was a live no-op (wired to a meta-channel output the executor skips, so a solo-authored test-list sailed to the gate). Both are idempotent-safe (a clean rerun passes; only a never-fanned-out / never-browsed turn blocks) and were verified against a real run's log. requires_e2eis preserved.STORY_ALLOWED_KEYSis derived from story.schema.json, so the story.json normalizer stops stripping valid fields (which had silently disabled the per-story E2E spec gate).- Blocked-past-retry-budget escalates cleanly (a recorded HIL escalation + exit 3) instead of a silent exit-1 abort with no escalation record.
- Architecture canon captures NFR posture (reads brief/requirement/statement, not just requirement, which had left the canon's NFR posture empty), and repairs NUL-byte corruption in two source files' dedup-key templates.
- The DBA's
db-design.jsonis logged (anartifact.writtenreconcile event; it was the one design artifact with no log trace). - The per-story-view postTurn traces its master/scoped counts to the agent-log, so a lingering double-dispatch is diagnosable on the next run.
Consort-only (pins scm-utils 0.2.51).