Skip to content

NapkinStack v0.4.0 -> v0.5.0 - #42

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

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

Conversation

@napkinstack-agent

Copy link
Copy Markdown
Contributor

NapkinStack v0.4.0 -> v0.5.0

Part of the validation log, #1. Copier's merge, unchanged by hand.


Module

None: a NapkinStack update changes no module beyond its description (D24).

  • This pull request touches a single module
  • ⚠️ Cross-module — the cross-module label is required, justification below

Deliverable

Out of cycle: a framework update. Cycle 1 is closed and no cycle is framed after it.

What it changes

What v0.5.0's release notes announce, and nothing else:

  • commits-on-main.yml, new: a commit that reaches main outside a pull request is
    named by a failing run. It records; it refuses nothing, and asks for no write access.
  • module-checks.yml: the compat step runs under if: ${{ !cancelled() }}, so V1's
    verdict is no longer hidden when an earlier step failed (D46); its closing step says
    "changed" where the job that lists them says "Changed modules" (D47).
  • The handbook: where a contract proof runs — in the base's tree, handed exactly one
    file of the change (D44) — and what remains when the forge can enforce nothing.
  • The README: the two words this project's diagnosis now answers with, guarded or
    unguarded, and the record.

Nothing was asked of this project. The v0.4.0 update needed the contracts module's
check and test written before it could pass; this one merges and passes as it stands.

Oracle

  • The success criterion was written before the implementation — the update merges
    with no conflict, and every check passes with no label and no sheet (D24, PDR-0001)
  • It was seen failing, for the right reason — an engine at 0.3.1 refuses to update
    a project recorded at v0.4.0: "no going back (PDR-0001)"
  • It passes now

Kind of oracle: other: the project's own checks, on the update branch


Review budget

  • Lines changed (excluding generated): 77
  • Files touched: 6
  • Within budget

Contracts

  • No contract affected

Definition of Done

  • Oracle green
  • Lint, format, types — untouched by this update
  • Unit tests — untouched
  • Build — nothing is built
  • Contract tests (when there is a contract) — untouched
  • Fitness functions
  • Integration tests (per risk)
  • Security analysis — the project's hooks, gitleaks
  • Accessibility (when there is UI)
  • E2E on critical journeys — untouched
  • Observability added
  • Rollback verified
  • Affected documentation updated — the update brings it
  • Diff self-reviewed line by line

Summary

DONE

  • The framework moves from v0.4.0 to v0.5.0; _commit follows.

VERIFIED

  • nstack fitness: manifests, boundaries, skills, plan and hygiene compliant.
  • nstack pr-check: compliant, with no label and no sheet — the update changes no
    module beyond its description.
  • nstack pr-scope: 84/400 lines, 6/15 files.
  • The merge is Copier's, with no hand edit: the same branch produced twice, from the
    published engine, gives the same tree.
  • The barrier this version exists for, replayed here before the branch was cleaned: with
    catalog-api v1 broken consistently, V1 refuses — "did not prove the change compatible
    (exit 1)"
    — with oasdiff's two errors visible above the verdict. The probe commit was
    removed; this branch carries the update alone.

ASSUMED

  • Nothing.

NOT VERIFIED

  • The new record has never fired here: nothing has reached main outside a pull request
    since it arrived. Its first firing will be a probe, logged like the others.

RISKS

  • A compat command that depended on a file of the pull request's tree would break with
    this version. This project's is self-contained, which is why nothing was asked of it.

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 — moving a workstation to the
    project's new version: uv tool upgrade silently does nothing on a pinned install, and
    uv tool install napkinstack@latest is what works. Found by the maintainer, reported
    upstream.

🤖 Generated with Claude Code

Copier's merge, unchanged by hand. What the release notes announce, and nothing else:
the record of what reaches main, the compat step that runs even after a failed one, and
the handbook passages on where a contract proof runs and on what remains when the forge
can enforce nothing.

Agent-Session: 6bb049af-0a74-454b-9876-233c8368d806
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@napkinstack-agent
napkinstack-agent Bot requested a review from a team as a code owner September 20, 2026 04:52
@napkinstack-agent napkinstack-agent Bot added the out-of-cycle Work outside the cycle — an incident, a production defect — justified in the description label Sep 20, 2026
@napkinstack-agent
napkinstack-agent Bot merged commit 36f1adf into main Sep 20, 2026
8 checks passed
@napkinstack-agent napkinstack-agent Bot mentioned this pull request Sep 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

out-of-cycle Work outside the cycle — an incident, a production defect — justified in the description

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant