Repository navigation
Release 1.0.84: project changelog at finish, corrected README - #84
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Lock the real init->plan->build->continue->seal->entomb flow, an already-archived shell from 1.0.79-1.0.82, and resetColonyStateForEntomb so a finished project never reads as damaged again. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
entomb's field-list reset missed Phase 200's plan-authority fields and the specification, so an archived shell failed the strict planning reader and status/resume disagreed with a finished project. Clear the whole Plan struct plus Specification on entomb, and tolerate the same residue in memory for shells already written by 1.0.79-1.0.82. Also fixes two bugs in the Part A tests themselves (next-action id vs runtime command string; output-mode env leaking from the shared lifecycle-to-seal helper). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A public-path spec item ID was a fixed prefix plus the whole path against a 40-character cap, so any entry point deeper than ~22 characters made discuss refuse the project. Long paths now get a short stable digest; short paths keep their existing IDs. Resume on a finished-and-archived project now says there is nothing to resume instead of reporting conflicting recovery evidence. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Status and resume named the next step by hand, which the hardcode ratchet refuses. They now render the shared what-next card, and that card no longer claims a saved goal or an unwritten handover for an archived project. Also derive the 'newer version' in three Codex skill tests from the real source version; typed 1.0.80/1.0.81 literals went red when the source passed them. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The runtime lazily installs the TS host's packages into the hub, and npm writes shortcut links under node_modules/.bin. The update planner's hub walk refused any link, so one lazy install locked out every later update. The walk now skips node_modules (never synced anyway) and still refuses a link anywhere else. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
After the seal commits, add a dated entry (goal plus one line per phase) to the project's CHANGELOG.md, creating the file when missing. Honest about a forced-incomplete finish, idempotent on replay, never writes through a link, and can never fail or undo the finish. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Audit found 13 wrong, 9 stale, 8 missing and 6 unverifiable claims. Install is now honest (npm 1.0.22 and the v1.0.43 tag are behind source), the one-builder default replaces the four-worker example, watch is one inline screen, dead commands and nonexistent folders are gone, unverifiable reliability figures are removed, and the history reaches 1.0.83. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
calcosmic
added a commit
that referenced
this pull request
Sep 21, 2026
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CHANGELOG.md, newest first and never above a hand-kept Unreleased section; the file is created when missing. Honest about a forced-incomplete finish, idempotent on replay (transaction-id marker), refuses to write through a symlink or over a non-regular file, written atomically, and structurally unable to fail or undo the seal. Locked by a test that runs the real init-to-seal path, so a writer nothing calls fails by name.go install …@latestresolves to v1.0.43), one-builder default replaces the four-worker example,watchis one inline screen, dead commands and nonexistent folders removed, unevidenced reliability figures removed, history brought current. Test-locked sections kept byte-for-byte; version literals removed from install prose so they cannot rot.Verification
Full suite in a pinned worktree: 5830/5830 executed; 29 failing, identical to the accepted pre-existing list, none new. All README-reading tests pass. Publish verified: binary and hub agree, integrity 5/5.
🤖 Generated with Claude Code