Repository navigation
NapkinStack v0.5.0 → v0.6.0 - #43
Merged
Merged
Conversation
napkinstack-admin
approved these changes
Sep 20, 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.5.0 → v0.6.0
The framework's update, laid on a branch by
nstack updateand merged with this project'sadaptations. No module code changes.
Module
None — the foundation's files.
Deliverable
A NapkinStack update changes no module beyond its description, so it is not delivery work and
names no deliverable (PDR-0003, clarified 2026-09-17).
What it changes for this project
One workflow, and it will run more jobs.
module-checks.ymlnow lists the modules to verifywith
--with-contract-sides: a change to a contract version runs the checks of the module thatprovides it and of every module that declares it in
consumes. Measured here beforepushing: a change to
catalog-api v1used to run thecontractsmodule's checks alone, and nowruns
catalog's andloans' as well. That is whatdocs/os/03-contracts.md§5 has alwayspromised.
Three new refusals, none of which fires on this project. Judged by v0.6.0 before the update,
this repository is already compliant: no placeholder left in the charter, the cycle or the three
manifests, and no deprecated module.
words is refused (C2, C4, C7, M2). For a module the rule waits until its first file of code.
turns red.
The handbook gains the corrections that go with them:
02-modules.md§6 names the rulebehind each of its four verdicts,
03-contracts.md§5 says what the CI actually runs, and threestale statements are fixed.
Oracle
Not applicable: no behaviour of this project changes. The engine's own rules carry their tests
in the framework's repository; what matters here is that the project still passes them.
Review budget
Contracts
Definition of Done
nstack fitnesscompliant on the published v0.6.0 engineSummary
DONE
.copier-answers.ymlrecordsv0.6.0; the module workflow asks for the contract's sides;the handbook receives v0.6.0's corrections.
VERIFIED
nstack updateon a clean clone: no conflict, 9 files, 48 lines.nstack fitness --root .on the published v0.6.0 engine: manifests, boundaries, skills,plan and hygiene all compliant.
catalog,loansandcontractswhere only
contractsran before.ASSUMED
NOT VERIFIED
this pull request changes no contract, so it will not show it. The first contract change will.
RISKS
contracts/runs more jobs than it used to. Intended, andbounded by what the manifests declare.
🤖 Generated with Claude Code