chore(agents): nevr-runtime-engineer primer states six facts the tree no longer matches
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- devtools, documentation
Research direction
Start with .claude/agents/nevr-runtime-engineer.md at lines 55, 117, 142, 184, 205, 296 and 420 and compare each claim with its cited source: AGENTS.md's commit conventions, src/runtime/CMakeLists.txt, and src/runtime/lifecycle/service_map.cpp. Re-run the grep commands quoted in the issue to confirm the current values. Done means each of the six lines is corrected with the command that verifies it, and the date the checks were run is recorded.
Written by the indexing model from the issue text.
Description
.claude/agents/nevr-runtime-engineer.md (last changed in 799570ba) carries a primer that agents trust as verified. Six of its claims are stale on main at 627ae420; two verifiers reported them independently as PRIMER DRIFT today, and each is checked below.
Evidence at 627ae420
- Line 55: commits are "author Andrew Bates, unsigned". AGENTS.md "Commit and verification conventions": "Author
Spritz Metis Sprock <[email protected]>... with a single houseCo-Authored-By: <agent name> <[email protected]>trailer for the agent that wrote it, plusCo-Authored-By: Andrew Bates <[email protected]>". - Line 117: "the highest tag in
src,toolsandjustfileon origin/main is N146".git grep -ohE '\bN1[0-9][0-9]\b' origin/main -- src tools justfile | sort -V | uniqends at N151 (N147, N148, N149, N151 exist). The primer's own command also returns N802, which is a ruffnoqa: N802code (tools/tests/test_quest_release_timer.py), not a rule. - Lines 142, 184, 205: ws-bridge, the static modules and the built-in log filter are "in
BugSplat64.dll". They are innevr-runtime.dll:src/runtime/CMakeLists.txtputscompat/ws_bridge.cppandlog/builtin_filter.cppinPATCHES_SOURCES, buildsnevr_runtimefrom it withOUTPUT_NAME "nevr-runtime", and linksnevr_platform_compatandnevr_token_authinto it;BugSplat64.dllis the thin host (nevr_host, ADR 0008). - Line 296: "N133: 31 entries".
git grep -c -E '^\s*\{"[a-z_]+",' origin/main -- src/runtime/lifecycle/service_map.cppgives 36, as AGENTS.md's N133 row says. - Line 420: "The disassembly was measurably UNAVAILABLE on 2026-07-28 — budget for that". ReVault answered disassembly, xrefs and function queries on libr15.so today (for example 0x220bff8
stp x28, x27, [sp, #-0x60]!).
Not shown
Whether other primer lines are stale: only these six were checked.
Falsifier
Any of the six lines matching the tree at 627ae420.
Work
- Correct the six lines against the cited sources, each with the command that shows it, so the next drift is found by re-running them.
- Re-run the primer's own verification commands and record the date they were run, or remove a claim no command checks.
- Dominant language
- C++
- Stars
- 2
- Forks
- 5
- Avg merge
- 4h 20m
- Merged PRs (30d)
- 939
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EchoTools/nevr-runtime
-
backlog bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
EchoTools/nevr-runtime#2335 ·
Maintainers usually reply within 1 day
-
backlog bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#2332 ·
Maintainers usually reply within 1 day
-
test(tools): the stage_pack description test fails when its two zips straddle a 2-second boundaryOpenbacklog
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#2309 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
EchoTools/nevr-runtime#2263 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
EchoTools/nevr-runtime#2260 ·
Maintainers usually reply within 1 day
All issues in EchoTools/nevr-runtime
Similar issues
-
Bug Testing
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SCIInstitute/SCIRun#2931 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 5 days
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
godotengine/godot#125272 ·
Maintainers usually reply within 1 day
-
bug impact: performance priority: med review: 2026-11 severity: med
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mgradwohl/ModernLife#67 ·