Skip to content

feat: backlog lifecycle sync (030), transactional pack refresh (031), and agent YAGNI directives - #9

Merged
E-G-C merged 4 commits into
mainfrom
backlog-lifecycle-sync
Aug 11, 2026
Merged

feat: backlog lifecycle sync (030), transactional pack refresh (031), and agent YAGNI directives#9
E-G-C merged 4 commits into
mainfrom
backlog-lifecycle-sync

Conversation

@E-G-C

@E-G-C E-G-C commented Aug 11, 2026

Copy link
Copy Markdown
Owner

Four commits on backlog-lifecycle-sync, base main.

Feature 030 — backlog lifecycle sync (fd62232)

Committed .dude/backlog.md / .html went stale after task-state mutations, so the backlog showed no active work while features were in flight. Adds mechanical refresh at the three task-state mutation chokepoints plus a terminal resolved idea lifecycle. Acceptance caught and fixed a live defect where recovery.mjs accepted only draft/defined, breaking inspect() once a resolved ledger existed.

Idea resolution (43415f7)

Resolves good-enough-delivery; its intent was already covered by existing YAGNI, materially-ready, and escalation rules.

Agent YAGNI directives (4097ec8)

The Tester and Reviewer were the only two agents missing the YAGNI governing rule their siblings carry — the two roles that decide how many edge cases get written and how much rework gets demanded. Tester gets a tailored clause: cover reachable inputs and real caller paths, not contrived permutations.

Feature 031 — transactional pack refresh (3aaa6b7)

Editing a pack source made that pack unrefreshable. remove refuses on the Feature 028 recorded-source digest guard; add --force early-returns as already installed. The documented remove-then-add path was unusable in exactly the case it documented.

Adds compose refresh <pack>: proves installed-side authority (exact profile bytes, whole-profile currency, files-to-inventory congruence, per-artifact recorded hashes), stages the current source through the canonical add pipeline, applies the destination-set difference, and updates the profile in one all-or-restored transaction. It deliberately does not apply the uninstall digest guard, because it expects the source to have changed. That guard and add --force semantics are unchanged.

Verified end-to-end in a throwaway real bundle: the edited-source case that fails remove returns [OK] refreshed pack "coding" (5 replaced, 0 added, 0 removed).

Verification

2308 tests, 2304 pass, 0 fail, 4 pre-existing skips · lint 0/0 · compose verify 16 packs clean · build-dev idempotent with source/generated parity · release build 64 files, single lint warning identical at HEAD · git diff --check clean.

Each task received independent review before close.

E-G-C added 4 commits August 11, 2026 12:39
Adds a dedicated 'compose refresh <pack>' subcommand that updates an
installed pack's .github/ projection from its current authoritative
source in one all-or-restored transaction.

Editing a pack source previously made that pack unrefreshable: 'remove'
refuses on the Feature 028 recorded-source digest guard, and 'add --force'
early-returns as already installed. The documented remove-then-add path
was unusable in exactly the case it documented.

Refresh proves installed-side authority (exact profile bytes, whole-profile
currency, files-to-inventory congruence, per-artifact recorded hashes),
stages the current source through the canonical add pipeline, applies the
destination-set difference, and updates the profile in the same
transaction. It does not apply the uninstall digest guard, because it
expects the source to have changed. That guard and 'add --force' semantics
are unchanged.
@E-G-C E-G-C changed the title feat(030): auto-refresh backlog projections and add resolved lifecycle feat: backlog lifecycle sync (030), transactional pack refresh (031), and agent YAGNI directives Aug 11, 2026
@E-G-C
E-G-C merged commit 1f6bc5a into main Aug 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant