vms-7f6+vms-1ee: cluster-dlm register honesty — repoint retired citations + downgrade 4 rows verified→implemented - #1101
Merged
Conversation
…heir executive-resident successors The run_dlm_harness_h0.sh..ec75 QEMU harnesses were deleted in #1052 (the CN=3 executive-resident pivot that retired the userspace SCSD daemon). Three cluster-dlm register rows still cited them in verified_against. render_compat.py only validates `evidence:` paths, not `verified_against:`, so this drift was invisible to the tool. Repointed to the real successors (verified by reading each test): - cross-node-lock (H5/H6): tests/qemu/test_syssvc_dlm_xnode.c scenarios 5 & 7 (block-then-grant + BLKAST wire) on a real /dev/vms executive. - async-reply-wire (H5): test_syssvc_dlm_xnode.c scenarios 5 & 5b (deferred GRANT report + requester-side origin-record receive) on real /dev/vms. - scs-transport: tests/cluster/host/test_codec_dlm.c (codec round trip + op validators) + test_syssvc_dlm_xnode.c (receive-handler GRANT/QUEUE/DEQ/BLKAST). Left unchanged and FLAGGED for conductor adjudication (NOT repointed, status untouched): cluster-dlm$remaster-lvb-deadlock. Its cited harnesses proved LVB write/read crossing (H8/H9), dynamic remastering (H10a/H10b), directory-ownership refusal (e84) and distributed deadlock detection (H11) on a real MULTI-NODE /dev/vms rail. No successor test exercises those cross-node behaviors on a real /dev/vms today; only partial host-backend/simulator coverage exists (test_lock_proxy.c: LVB-read + ENUM_WAITS visibility; sim scenarios: directory routing). A row marked status:verified / authenticity:real whose multi-node proof is gone may be overclaiming — flagged for downgrade / Baron authenticity review rather than silently repointed. render_compat.py: succeeds, 0 warnings (unchanged from baseline); build json is gitignored and the rendered surface md does not carry per-row verified_against, so both are byte-identical after regeneration. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018q4jvj6GCkdbYjRvpy7Vwu
…ed (multi-node proof retired in #1052) An adversarial audit of the frontier verified/real rows found that repointing verified_against alone (the prior commit) was insufficient: all four cluster-dlm rows are marked `verified` on the strength of the run_dlm_harness_*.sh multi-node real-/dev/vms proofs, which were DELETED in #1052 (the CN=3 executive-resident pivot that retired the userspace SCSD daemon). The surviving coverage — test_syssvc_dlm_xnode.c (single-node dispatch with an injected cross-node CSID), test_codec_dlm.c (frame codec), the host units, and the N-node simulator scenarios — is real but does NOT prove the multi-node/over-the-wire behavior the `verified` status claims. Keeping `verified` is an overclaim on the public compatibility page. Honest correction (INV-6 real-data-or-honest-omission): - status verified->implemented for cross-node-lock, async-reply-wire, remaster-lvb-deadlock, scs-transport (code is real + executive-resident; the multi-node PROOF is gone, not the code). - remaster-lvb-deadlock verified_against repointed off the deleted harnesses to its real surviving partial coverage (host units + sim scenarios + codec). - notes: corrected the "Proven on a live multi-node /dev/vms rail" / "across every DLM QEMU harness (H0..H11)" claims to reflect that those harnesses were retired in #1052; the accurate mechanism descriptions are preserved, and every run_dlm_harness reference is now explicitly framed as retired history. Re-establishing the multi-node runtime proof is tracked + gated for Baron in vms-1ee. verified count 26->22. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018q4jvj6GCkdbYjRvpy7Vwu
baron-3dl
changed the title
baron-3dl
added a commit
that referenced
this pull request
Sep 10, 2026
…cated SET HOST (hard-gated x86_64+Alpha+VAX) Version bump (identity + os-release in step, INV-1 SSOT gate). V0.6-13 ships: - DECnet Phase IV file COPY (FAL/DAP): object-17 FAL server + DAP codec + COPY client, authenticated against the real SYSUAF/Purdy with RMS-over-ACP transfer, byte-verified both directions (#1096, vms-8c2). - The authenticated inbound SET HOST -> LOGINOUT proof is now a HARD GATE on all three rails: DECNETD.EXE staged onto the VAX sysvol + Alpha boot image, so DECNETD-CTERM-ACCEPT + DECNETD-ISOLATION assert+PASS on x86_64 + Alpha + VAX — the login frontier is substrate-agnostic (#1099, vms-c1f). - DECnet Phase IV configuration + usage guide (#1097, vms-30e). - Compatibility-register honesty: cluster-dlm evidence repointed off deleted src/vmsscs paths to the executive-resident src/kernel-core, and the 4 cluster-dlm rows whose multi-node /dev/vms proof was retired in #1052 downgraded verified->implemented (#1100/#1101; multi-node proof re-establishment gated in vms-1ee). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018q4jvj6GCkdbYjRvpy7Vwu
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
1 participant
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.
The
run_dlm_harness_*.shmulti-node real-/dev/vms proofs behind the fourcluster-dlmverified/real rows were deleted in #1052 (CN=3 executive-resident pivot). This PR makes the register honest:verified_againstcitations to the real surviving tests (test_syssvc_dlm_xnode.c,test_codec_dlm.c, host units, sim scenarios).cross-node-lock,async-reply-wire,remaster-lvb-deadlock,scs-transportfromverified→implemented: the code is real + executive-resident, but the surviving coverage (single-node dispatch with injected CSID / frame codec / host units / sim) does not prove the multi-node over-the-wire behavior theverifiedstatus claimed. Keepingverifiedoverclaims on the public compat page.Re-establishing the multi-node runtime proof is tracked + gated for Baron in vms-1ee. verified count 26→22. Docs-only (register YAML + regenerated compatibility-surface.md); INV-6 honest-omission.
🤖 Generated with Claude Code
https://claude.ai/code/session_018q4jvj6GCkdbYjRvpy7Vwu