Repository navigation
NapkinStack v0.6.1 → v0.6.2 - #31
Merged
Merged
Conversation
napkinstack-admin
approved these changes
Sep 24, 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.1 → v0.6.2
Taken at the same boundary as #29, and deliberately before cycle 03 is accepted (#30): once that
merges, the project is inside a cycle and the next check is owed at 2026-10-15.
Module
None. Two lines:
.copier-answers.ymland the install command inREADME.md.Deliverable
Out of cycle: a framework update.
What it changes
That is the whole diff, and it is what the release said it would be. v0.6.2's changelog states
"In your project — nothing":
skeleton/is unchanged since v0.6.1, sonstack updatelays down abranch that bumps the recorded version and merges no file. No conflict was reported and
git grepfinds no marker.
Checked rather than taken on trust. The nine files that changed between the two tags are all in
the engine or in its own governance documents; none is under
skeleton/, and none isplan.pyorpull_request.py— so nothing already merged becomes non-compliant under the newjudge.
What the engine gains, and why it is worth a boundary
section is missing and posts that section as the tag's release page.
nstack updatesays where to read it, and names every version crossed, not the targetalone. This landed for us immediately: the command printed the changelog URL and "every section
above v0.6.1".
errnonames the filesystem instead of reporting everyOSErroras"Template unreachable" with an action about
--source,--refand the network.The second one is the reason not to wait. Checking this boundary turned up something worth knowing:
v0.6.1's changelog says it changed
.gitignoreand that a project with its own agent ignore ruleswould conflict — and our v0.6.1 update (#29) produced two lines and no conflict. That could have
been a skeleton change silently dropped. It was not: our
.gitignoreis the v0.6.1 skeleton's plusour own two
.coveragelines, the D58 rules are all present, and.claude/settings.jsonand.claude/hooks/are deliberately not ignored. The conflict never happened because #4 had alreadywritten the same rules. From now on the tool reports that instead of leaving it to be
reconstructed by hand.
The sequence, kept and now twice recorded
Cycle 02 closed (#27) → framework to v0.6.1 (#29) → this → cycle 03 accepted (#30). A cycle
accepted under a framework version the project has not recorded would be a cycle judged by
something the repository does not declare.
nstack updatewas run frommainthis time, so unlike #29 there was no feature-branch commit toreplant.
Oracle
nstack doctor's L1, whichcompares the installed CLI against the version recorded in
.copier-answers.ymlupdate during the v0.6.1 round, exactly as the handover warns
nstack doctor: 0 gaps, L1 to L7 OK, judged by 0.6.2 with the projectrecorded at v0.6.2
Kind of oracle: fitness function ·
nstack doctorReview budget
Contracts
Definition of Done
nstack doctor0 gapsnstack check screeningexit 0 on this branchnstack fitnessexit 0, compliantTest sheet
Not required: this pull request changes no module.
Summary
DONE
The project is recorded at NapkinStack v0.6.2 and the README installs it.
VERIFIED
nstack doctor0 gaps with L1 to L7 OK;nstack fitnessexit 0;nstack check screeningexit 0;81 tests pass on this branch. The claim that nothing changes in the project was checked against the
tag diff, not only against the changelog.
ASSUMED
Nothing. The changelog's "In your project — nothing" was confirmed by listing the files that
changed between the tags.
NOT VERIFIED
The thirteen GitHub settings:
nstack doctorreports themNOT VERIFIEDbecause the shell had notoken — what cannot be read is never reported as guarded.
doctorexits non-zero in that state,so the gap count is what to read. Nothing here touches those settings.
RISKS
None identified. The rollback is one commit. The framework has published three versions in four
days, so the next check is owed at the 2026-10-15 boundary and not before — chasing releases
mid-cycle is what the rule exists to prevent.
Signals to report
The signal raised in #29 — that
nstack updatebranches from the current HEAD without saying so —still stands, and this round avoided it by checking out
mainfirst rather than by the toolchanging.