Skip to content

Expand old-coder skills and make evidence reproducible - #12

Merged
AmazingAng merged 6 commits into
mainfrom
agent/publish-old-coder-updates
Aug 17, 2026
Merged

Expand old-coder skills and make evidence reproducible#12
AmazingAng merged 6 commits into
mainfrom
agent/publish-old-coder-updates

Conversation

@AmazingAng

Copy link
Copy Markdown
Owner

What changed

  • make old-coder the primary README focus
  • add the old-coder API design skill and composition guidance
  • fix API idempotency evidence
  • replace ambient-filesystem source hashing with a deterministic, fail-closed tracked manifest
  • add source-state negative controls and bind the final Evidence Report to the reproducible source state

Why

The previous source-state hash included ignored editable-install artifacts, so a clean checkout could not reproduce the published evidence binding. These changes make the binding reproducible while preserving the broader documentation and API-skill updates already prepared locally.

Validation

  • full gauntlet passed at the implementation commit and final evidence commit
  • 47 tests passed with 100% statement and branch coverage
  • 6/6 source-state negative controls passed
  • 22/22 mutants killed
  • 10/10 randomized suite-health runs passed
  • old-coder skill validation passed

@AmazingAng
AmazingAng merged commit 57ebbbb into main Aug 17, 2026
1 check passed
@AmazingAng
AmazingAng deleted the agent/publish-old-coder-updates branch August 17, 2026 20:12
AmazingAng added a commit that referenced this pull request Aug 17, 2026
Source state is now `49e8762` / `2226ed2dfeddb76c`, with the two-tier
guarantee stated: the tree hash is the required content identity whenever a
binding is produced, the source commit is provenance available only with
complete history.

Honest notes record what the defect actually cost: CI published a wrong source
commit twice — `a4276a2` on the PR #12 check and `57ebbbb` after merge,
where the truth was `d45cc2f` — at exit 0 with the gauntlet green, because
no control covered a truncated history. Also records that three REVISION 5
controls asserted only a non-zero exit and one of them mis-described which
guard it exercised, and that the fixture-guard removal is a diagnosability fix
no control can prove.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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