Skip to content

Clarify nonclaim ordering and protect materialized evidence - #113

Merged
iperev merged 4 commits into
mainfrom
fix/cli-nonclaims-guide
Sep 8, 2026
Merged

Clarify nonclaim ordering and protect materialized evidence#113
iperev merged 4 commits into
mainfrom
fix/cli-nonclaims-guide

Conversation

@iperev

@iperev iperev commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Clarify the existing sorted/unique nonClaims rule in lazy CLI input help; preserve argv order.
  • Verify ordered multi-item nonClaims through child admission, approved materialization and stored re-admission. Reject duplicate/unsorted input before writes.
  • Prepare compatible patch 0.14.6, refresh source-bound contract fingerprints and retain the independent exact release-note oracle.

Verification

  • Complete npm run check passed on 829fb6f; final tree clean. This includes 315 browser tests across Chromium, Firefox and WebKit, native/static/package/self-hosting and release-closeout gates.
  • Targeted app, command-contract generator and release-change tests passed.
  • An isolated serializer mutation that drops inventory-entry nonClaims survived the previous assertion and is now rejected in all three adoption intents; source bytes were restored by construction, not rewritten.
  • Four final independent review dispositions closed their assigned repair obligations without further findings. Campaign-wide host isolation and open-world completeness remain unproven.
  • git diff --check passed.

Boundaries

Accepted inputs, request/report identities, schema versions, native authority and platform requirements are unchanged. Local validation does not prove GitHub CI, registry publication, consumer adoption or global roadmap completion. All applicable exact-head GitHub checks remain mandatory before squash merge.

@iperev
iperev merged commit 10d8bd0 into main Sep 8, 2026
9 checks passed
@iperev
iperev deleted the fix/cli-nonclaims-guide branch September 8, 2026 23:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant