vms-015: repoint cluster-dlm evidence from deleted src/vmsscs to src/kernel-core - #1100
Merged
Merged
Conversation
…utive-resident src/kernel-core
The SCS/DLM code moved from the retired userspace SCS daemon
(src/vmsscs/, now DELETED) into the executive-resident kernel-core
substrate. Two Compatibility Surface Register rows still cited the old,
gone files, tripping render_compat.py's evidence-drift warnings.
Repoint (verified the target actually implements the claimed behavior,
not merely exists):
- cluster-dlm$async-reply-wire:
src/vmsscs/scsd.c -> src/kernel-core/vms_dlm_scs_fsm.c
The DLM REQUESTER arm: h_grant() receives the async queued-reply /
deferred GRANT off the SCS wire and completes the executive-resident
origin record via grant_recv() -- the "requester-side completion" the
row claims.
- cluster-dlm$scs-transport:
src/vmsscs/scs_dlm.c -> src/kernel-core/vms_cluster_codec_dlm.c
The DLM lock-request message class: typed encode/decode of the
ENQ/GRANT/DEQ/BLKAST/REBUILD/DLKSRCH frame body.
verified_against fragment repointed: the stale "src/vmsscs codec
ctests" -> tests/cluster/host/test_codec_dlm.c (frame round-trip +
op-validator ctest).
Only the file citations changed; status/authenticity/desc untouched.
render_compat.py now emits no "evidence not found" warning for either
row. Regenerated docs/compatibility-surface.md committed alongside.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018q4jvj6GCkdbYjRvpy7Vwu
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.
vms-015 — Compatibility Surface Register evidence-drift fix
The SCS/DLM implementation moved from the retired userspace SCS daemon (
src/vmsscs/, now deleted on origin/main) into the executive-residentsrc/kernel-core/substrate. Twocluster-dlmregister rows still cited the gone files, trippingrender_compat.py's evidence-drift warnings.Evidence repoints (verified the target implements the behavior, anti-LARP)
cluster-dlm$async-reply-wiresrc/vmsscs/scsd.csrc/kernel-core/vms_dlm_scs_fsm.ch_grant()receives the async queued-reply / deferred GRANT off the SCS wire and completes the executive-resident origin record viagrant_recv()— the "requester-side completion" the row claims.cluster-dlm$scs-transportsrc/vmsscs/scs_dlm.csrc/kernel-core/vms_cluster_codec_dlm.cverified_against fix (scs-transport row)
Stale fragment
src/vmsscs codec ctests (scs_dlm frame encode/decode + op-name validators)→tests/cluster/host/test_codec_dlm.c (DLM frame encode/decode + op validators)(the current codec round-trip + op-validator ctest).Confirmation
python3 tools/compat/render_compat.py 2>&1 | grep -i cluster-dlm→ no output (both "evidence not found" warnings gone). Regenerateddocs/compatibility-surface.mdcommitted; its only diff is the two evidence path strings.Only file citations changed — status / authenticity / desc untouched. No
src/product code changed; no tests weakened.Known residual drift (out of scope for vms-015, flagged not fixed)
The
verified_againststrings across several cluster-dlm rows still referencetests/qemu/run_dlm_harness_h0.sh..ec75— those.shharness scripts no longer exist on origin/main (render_compat.pydoes not validateverified_againstpaths, so no warning fires). This affects multiple rows I was scoped not to touch; recommend a follow-up sweep to repoint the harness references (likely to thetests/cluster/sim/+tests/cluster/host/successors).🤖 Generated with Claude Code
https://claude.ai/code/session_018q4jvj6GCkdbYjRvpy7Vwu