Skip to content

NapkinStack v0.6.0 → v0.6.1 - #29

Merged
napkinstack-agent[bot] merged 1 commit into
mainfrom
nstack/update-v0.6.1
Sep 23, 2026
Merged

napkinstack-agent[bot] merged 1 commit into
mainfrom
nstack/update-v0.6.1

Conversation

@napkinstack-agent

Copy link
Copy Markdown
Contributor

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.yml and the install command in README.md.

  • This pull request touches a single module — n/a, it touches none
  • ⚠️ Cross-module

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

-_commit: v0.6.0
+_commit: v0.6.1
-uv tool install "napkinstack==0.6.0" --with-executables-from pre-commit
+uv tool install "napkinstack==0.6.1" --with-executables-from pre-commit

That is the whole diff. nstack update merged it with the project's adaptations and reported no
conflict; git grep over the branch finds no conflict marker.

Why now and not earlier. Upgrading the CLI without nstack update turns doctor's L1 red, and
upgrading 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, then nstack update, then
nstack doctor — and the reason to check at every boundary: the framework moved 0.3.0 to 0.6.1
in 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 why
the commit has no Agent-Session trailer. ADR-0001's split is about the calls an agent makes.

nstack update branched from wherever HEAD was, which was cycle/03-framing, so the branch it
created carried cycle 03's framing commit as well. It has been rebased onto main, and this pull
request is the two lines above and nothing else. Worth knowing before the next update: check out
main first, or expect to replant the branch.


Oracle

  • The success criterion was written before the implementation — nstack doctor's L1, which
    compares the installed CLI against the version recorded in .copier-answers.yml
  • It was seen failing, for the right reason — L1 is what goes red if the CLI is upgraded
    without this commit, which is the sequence the handover warns about
  • It passes now — nstack doctor reports 0 gaps, L1 to L7 OK, judged by 0.6.1 with the
    project recorded at v0.6.1

Kind of oracle: fitness function · nstack doctor

Review budget

  • Lines changed: 2
  • Files touched: 2
  • Within budget

Contracts

  • No contract affected

Definition of Done

  • Oracle green — nstack doctor 0 gaps
  • Lint, format, types — nstack check screening exit 0 on this branch, read on its own exit
    status
  • Fitness functions — nstack fitness exit 0, compliant
  • Everything else — n/a, no code
  • Affected documentation updated — the README's install line is part of the diff
  • Diff self-reviewed line by line

Test 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 doctor 0 gaps with L1 to L7 OK; nstack fitness exit 0; nstack check screening exit 0.
No conflict marker on the branch.

ASSUMED
That 0.6.1 changes nothing this project depends on beyond these two lines. nstack update merged
the 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 doctor reported them NOT VERIFIED rather than OK because
the 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

  • I had to look at another module's implementation
  • A kernel or playbook rule got in my way for no good reason
  • A quality gate blocked without improving quality
  • A rule applied by hand would be worth automating

The signal. nstack update builds its branch from the current HEAD without saying so, so
running 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.

@napkinstack-agent
napkinstack-agent Bot merged commit 8e5dac8 into main Sep 23, 2026
7 checks passed
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.

2 participants