Skip to content

NapkinStack v0.5.0 → v0.6.0 - #43

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

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

Conversation

@napkinstack-agent

Copy link
Copy Markdown
Contributor

NapkinStack v0.5.0 → v0.6.0

The framework's update, laid on a branch by nstack update and merged with this project's
adaptations. No module code changes.


Module

None — the foundation's files.

  • This pull request touches a single module
  • ⚠️ Cross-module

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.yml now lists the modules to verify
with --with-contract-sides: a change to a contract version runs the checks of the module that
provides it and of every module that declares it in consumes. Measured here before
pushing: a change to catalog-api v1 used to run the contracts module's checks alone, and now
runs catalog's and loans' as well. That is what docs/os/03-contracts.md §5 has always
promised.

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.

  • A charter, a cycle, a deliverable or a module responsibility still holding its template's
    words is refused (C2, C4, C7, M2). For a module the rule waits until its first file of code.
  • A deprecated module's consumers are named with the removal date (B8) — a warning; M5 is what
    turns red.
  • A Copier refusal keeps the line saying what happened, with an action to match.

The handbook gains the corrections that go with them: 02-modules.md §6 names the rule
behind each of its four verdicts, 03-contracts.md §5 says what the CI actually runs, and three
stale 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

  • Lines changed (excluding generated): 48
  • Files touched: 9
  • Within budget

Contracts

  • No contract affected

Definition of Done

  • Fitness functions — nstack fitness compliant on the published v0.6.0 engine
  • Affected documentation updated — the update brings it
  • Diff self-reviewed line by line

Summary

DONE

  • .copier-answers.yml records v0.6.0; the module workflow asks for the contract's sides;
    the handbook receives v0.6.0's corrections.

VERIFIED

  • nstack update on 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.
  • The effect of the new listing, measured on this repository: catalog, loans and contracts
    where only contracts ran before.

ASSUMED

  • Nothing.

NOT VERIFIED

  • The wall-clock cost of the extra jobs: CI on this pull request is the first measurement, and
    this pull request changes no contract, so it will not show it. The first contract change will.

RISKS

  • A later pull request touching contracts/ runs more jobs than it used to. Intended, and
    bounded by what the manifests declare.

🤖 Generated with Claude Code

@napkinstack-agent
napkinstack-agent Bot requested a review from a team as a code owner September 20, 2026 15:09
@napkinstack-agent
napkinstack-agent Bot merged commit 253136e into main Sep 20, 2026
7 checks passed
@napkinstack-agent
napkinstack-agent Bot deleted the nstack/update-v0.6.0 branch September 20, 2026 15:17
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