Skip to content

Version 0.29.1 — an update and an attested record, each step said - #401

Merged
napkinstack-agent[bot] merged 1 commit into
mainfrom
version-0.29.1
Nov 15, 2026
Merged

napkinstack-agent[bot] merged 1 commit into
mainfrom
version-0.29.1

Conversation

@napkinstack-agent

Copy link
Copy Markdown
Contributor

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 update generates the skills again (D220): where the person generated skills (.claude/skills/), the update regenerates them from the updated playbooks and says so. A first nstack attest no longer fails Fitness on S3. nstack skills removes a generated skill whose playbook is gone, and never removes one a person wrote.
  • A required record status keeps an attested pull request moving (D221, A record made after the PR's last run never re-runs « Test sheet and cycle »: the merge stays blocked until the description is edited #399): the record is made after the description's last edit, and its notes start no run. Where the base branch's ruleset requires nstack / local checks, the status nstack attest posts 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 by nstack agent add gets 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): requiring nstack / local checks in an attested project, and the token that posts it.

Migration

  • An attested project on GitHub (D221): add nstack / local checks to 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 last nstack attest.
  • An agent App made before this version (D221): give it Commit statuses: write in its settings, and accept the change on its installation. Without it, nstack attest says the status is not shown, and a ruleset requiring the status waits.

Checks

  • Oracle uv run bash platform/tests/run.sh: 1308 passed, scenarios OK. Fitness compliant.

🤖 Generated with Claude Code

Agent-Session: nstack-os-v0291
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@napkinstack-agent
napkinstack-agent Bot requested a review from a team as a code owner November 14, 2026 21:25
@napkinstack-agent
napkinstack-agent Bot merged commit 539a7a5 into main Nov 15, 2026
3 checks passed
@napkinstack-agent
napkinstack-agent Bot deleted the version-0.29.1 branch November 15, 2026 08:57
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