BREAKING feat/nxp-next-provenance #1 / 4
aaronrene · 16 hours ago · Sep 5, 2026 · Diff

NXP-b DONE: independent BV-r2 pass + ISR (SD-17)

sha256:c07f2f34a0db9f43fe866f157d1935322008545ff8940c06c7c921eb219c55ab sha
+7 ~9 −7 symbols
816 changed · 816 in snapshot files
sha256:df78bae378a81d7c8d5864acfc1d635b9f1671a58e1234d24de8885d7ae2a791 snapshot
+7
symbols added
~9
symbols modified
−7
symbols removed
816
files changed
816
files in snapshot
0
dead code introduced
Semantic Changes 23 symbols
~ docs/OVERSEER-HANDOVER.md .md 7 symbols added, 7 symbols removed, 6 symbols modified
NEXT SESSION — NXP-b build verification round 2 (NXP-b-BV-r2) section NEXT SESSION — NXP-b build verification round 2 (NXP-b-BV-r2) L11–91
Paste-ready prompt — NXP-b build verification round 2 (NXP-b-BV-r2) section Paste-ready prompt — NXP-b build verification round 2 (NXP-b-BV-r2) L50–91
code[text] variable variable code[text] L52–87
THE ONE NEXT STEP — Model: thinking-high section THE ONE NEXT STEP — Model: thinking-high L34–50
table section table L40–47
Where NXP-b stands section Where NXP-b stands L17–34
table section table L24–28
+ NEXT SESSION — NXP → main (land-a, Tier 3) section NEXT SESSION — NXP → main (land-a, Tier 3) L11–100
+ Paste-ready prompt — NXP → main (land-a, Tier 3) section Paste-ready prompt — NXP → main (land-a, Tier 3) L63–100
+ code[text] variable variable code[text] L65–96
+ THE ONE NEXT STEP — Model: Operator + Auto section THE ONE NEXT STEP — Model: Operator + Auto L47–63
+ table section table L52–60
+ Where NXP-b landed section Where NXP-b landed L17–47
+ table section table L23–28
~ table
Files Changed
+816
816 in snapshot
+ .gitignore .gitignore
+ .museattributes .museattributes
+ .museignore .museignore
+ .overseer/.muse-bridge-sentinel .muse-bridge-sentinel
+ AGENTS.md .md
+ CHANGELOG.md .md
+ README.md .md
+ SECURITY.md .md
+ cli/args.py .py
+ cli/drift.py .py
+ cli/kn_r2.py .py
+ cli/main.py .py
+ cli/ok
+ cli/paths.py .py
+ desktop/.gitignore .gitignore
+ pyproject.toml .toml

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:c07f2f34a0db9f43fe866f157d1935322008545ff8940c06c7c921eb219c55ab --body "your comment"