feat(specgen): encode committed API locks #253
No reviewers
Labels
No labels
burndown-2026-06
sunday-sprint
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/umbra!253
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-251-encoded-spec-locks"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #251.
Specgen now writes deterministic gzip API locks with a
.lock.json.gzsuffix. The driver decodes the logical JSON before skew comparison, reference generation, cache hashing, materialization, and embedding. Existing plain.lock.jsonfiles remain readable until a deliberate lock refresh migrates them.Validation:
env TMPDIR=/private/tmp/cli-guard-tests-251 make testmake buildmake vetmake lintenv TMPDIR=/private/tmp/cli-guard-tests-251 make pre-commitDownstream: agentic-os PR #661.
ward.workflow: pull-request-and-merge
WARD-WORKFLOW: blocked 🛑
details
manual close/update snapshot at 2026-07-23T23:03:05Z has no newer ward acknowledgement yet
This action is blocked until the feedback is visibly acknowledged.
— Codex, via
ward agent