Repository navigation
Version 0.29.1 — an update and an attested record, each step said - #401
Merged
Merged
Conversation
Agent-Session: nstack-os-v0291 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
napkinstack-admin
approved these changes
Nov 15, 2026
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.
The version pull request for v0.29.1: D220 and D221.
A patch: nothing green turns red (semver rule in CHANGELOG.md). D221 needs a gesture at the forge to help, written in Migration.
v0.29.1 — 2026-11-14
D220–D221, from the same multi-agent project taking v0.29.0: an update and an attested record, each of which left a step to someone's memory.
This is a patch: nothing green turns red. D221 helps only once a gesture at the forge is made (Migration).
In the engine
nstack updategenerates the skills again (D220): where the person generated skills (.claude/skills/), the update regenerates them from the updated playbooks and says so. A firstnstack attestno longer fails Fitness on S3.nstack skillsremoves a generated skill whose playbook is gone, and never removes one a person wrote.nstack / local checks, the statusnstack attestposts with the record, the pull request's run leaves A1 and A2 to that status and says so. Otherwise it judges the record as before, and A1's action names both ways out. An agent's App made bynstack agent addgets Commit statuses: write.In your project — 2 files, text
.github/workflows/pull-request.yml: a comment, the record's status as its event (D221)..nstack/handbook/07-governance.md§7 (D221): requiringnstack / local checksin an attested project, and the token that posts it.Migration
nstack / local checksto the required status checks of the default branch's ruleset (Settings → Rules → the ruleset → Require status checks). Until then, the author still edits the description after the lastnstack attest.nstack attestsays the status is not shown, and a ruleset requiring the status waits.Checks
uv run bash platform/tests/run.sh: 1308 passed, scenarios OK. Fitness compliant.🤖 Generated with Claude Code