Repository navigation
NapkinStack v0.6.0 → v0.6.1 - #29
Merged
Merged
Conversation
napkinstack-admin
approved these changes
Sep 23, 2026
This was referenced Sep 23, 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.
NapkinStack v0.6.0 → v0.6.1
Received at the cycle boundary, which is the only place it belongs.
Module
None. Two lines:
.copier-answers.ymland the install command inREADME.md.Deliverable
Out of cycle: a framework update. A pull request that changes no module beyond its description is
not delivery work (
docs/project/README.md).What it changes
That is the whole diff.
nstack updatemerged it with the project's adaptations and reported noconflict;
git grepover the branch finds no conflict marker.Why now and not earlier. Upgrading the CLI without
nstack updateturns doctor's L1 red, andupgrading mid-cycle changes the judge while a cycle is being judged. Cycle 02 closed on 2026-09-23
(#27) and cycle 03 is proposed but not accepted (#28), so this is the boundary. The handover in #27
carries the sequence for the next time —
uv tool install, thennstack update, thennstack doctor— and the reason to check at every boundary: the framework moved 0.3.0 to 0.6.1in three days.
Two things worth recording about how this landed
It was run by the decider, in their own shell, and the commit carries their identity rather
than the
napkinstack-agent[bot]one. That is correct — a human made this change — and it is whythe commit has no
Agent-Sessiontrailer. ADR-0001's split is about the calls an agent makes.nstack updatebranched from wherever HEAD was, which wascycle/03-framing, so the branch itcreated carried cycle 03's framing commit as well. It has been rebased onto
main, and this pullrequest is the two lines above and nothing else. Worth knowing before the next update: check out
mainfirst, or expect to replant the branch.Oracle
nstack doctor's L1, whichcompares the installed CLI against the version recorded in
.copier-answers.ymlwithout this commit, which is the sequence the handover warns about
nstack doctorreports 0 gaps, L1 to L7 OK, judged by 0.6.1 with theproject recorded at v0.6.1
Kind of oracle: fitness function ·
nstack doctorReview budget
Contracts
Definition of Done
nstack doctor0 gapsnstack check screeningexit 0 on this branch, read on its own exitstatus
nstack fitnessexit 0, compliantTest sheet
Not required: this pull request changes no module, and a framework update is named as such in
docs/project/README.md.Summary
DONE
The project is recorded at NapkinStack v0.6.1 and the README installs it.
VERIFIED
nstack doctor0 gaps with L1 to L7 OK;nstack fitnessexit 0;nstack check screeningexit 0.No conflict marker on the branch.
ASSUMED
That 0.6.1 changes nothing this project depends on beyond these two lines.
nstack updatemergedthe template and produced no other change, which is the evidence for it — not a reading of the
release notes.
NOT VERIFIED
The thirteen GitHub settings.
nstack doctorreported themNOT VERIFIEDrather thanOKbecausethe shell it ran in had no token: what cannot be read is never reported as guarded. They were
readable and compliant when last checked with a token, and nothing in this pull request touches
them.
RISKS
None identified. The rollback is one commit.
Signals to report
The signal.
nstack updatebuilds its branch from the current HEAD without saying so, sorunning it from a feature branch silently mixes the update with that branch's commits. It already
knows the branch name it wants to create; branching from the default branch, or refusing when HEAD
is not on it, would remove a step that has to be caught by hand and could easily be merged unnoticed
in a small diff.