docs(deploy): retarget the NEMESIS.md pointer to TERMINUS.md (CLAWD-3862) - #65
Merged
Conversation
…862) CLAWD-3769 enumerated this file and asked whether the reference is a path the script READS -- because this is the one executable in its list, where a rename would change runtime behaviour rather than documentation accuracy. The material answer is that this is a text edit with no behaviour change, and that holds. THE MECHANISM I FIRST GAVE FOR IT WAS FALSE, and an independent reviewer measured it: I wrote "no code path reads, tests or resolves it", and two of those three verbs are wrong. Line 31 sits inside the `-h|--help` header block, which is emitted by `sed -n '2,69p' "$0"` at :86 -- so it IS read from the script and printed to the operator, and it IS pinned by a test (tests/scripts/test_opt_provenance_report.py, which asserts the sed range ends at the header boundary). What is true is narrower: it is never RESOLVED as a path, and this edit is line-count-neutral, so the pinned range and both guard tests are unaffected. Verification: git grep -In 'NEMESIS' -- . -> rc 1, zero hits (was 1) bash -n scripts/deploy-to-runtime.sh -> OK wc -l, HEAD vs origin/main -> 234 vs 234 (neutral) `set -euo pipefail` still at NR=70 -> range 2,69p still correct --help | grep TERMINUS -> prints the retargeted line pytest tests/scripts/test_opt_provenance_report.py -k help -> 2 passed Rebased onto origin/main (ef452df) -- the branch was cut from a local `main` one commit stale, missing merged PR #64. The sweep result is unchanged by that (`git grep` on origin/main returns the same single hit) but the branch should not carry the staleness.
mbs-vhs
force-pushed
the
4dbc92ad/terminus-pointers
branch
from
August 14, 2026 16:50
cdb79de to
260d6cf
Compare
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.
Part 3 of 3 for CLAWD-3862. CLAWD-3769 enumerated this file and was closed on agent-overwatch PR NousResearch#82 without touching it.
3769 flagged
scripts/deploy-to-runtime.shas the one to look at first, because it is the only executable in its list, and asked whether the reference is a path the script reads — in which case the rename changes runtime behaviour rather than documentation accuracy.Resolved: it is prose. Line 31 sits inside the
#-prefixed header comment block explaining that~/.hermesstays load-bearing afterchat.vhs.boxwas decommissioned. No code path reads, tests or resolves it. Text edit only.Verification
Tier
runtime(/opt/hermes-agent), so per TERMINUS.md §1 branch-in-place is the declared workflow. Nothing uncommitted left behind; the runtime deploys from a ref, and this changes no code path it executes.