fix(skills): the hardware-loop fence-scope pin follows the deliberate Strumento v0.2 reexport inversion (#1193) - #1198
Merged
Conversation
…nato re-scope (#1193) The fleet-gated regression pinned the hardware-loop skill's fence scope to Strumento, but the live skill's fence resolves to Intonato. Adjudication from history: the skill moved correctly, the pin was the drifted side. - The pin (and the 'ten' claim inventory) date to 504277c (#1002), when the skill's fence read `using Strumento # reexports Intonato ...`. - The 2026-09-10 freshness audit (armonissima#88, vault 10a93ce) deliberately updated the fence to `using Intonato` — the old `using` was the stale v0.2 reexport idiom: the seam inverted in Strumento v0.2, so Intonato (the chassis) now reexports the substrate (Strumento), not vice versa. - Inventory fallout: the old `Intonato` claim was minted by the old fence comment; the extracted claim set is nine now. Intonato coverage lives in the fence-scope pin and the reexport-chain inversion test. Red→green verified on a fleet machine (live checkouts mounted): the focused test failed with `expected [ 'Intonato' ] to deeply equal [ 'Strumento' ]`, then the full skill_drift_lint file passed 68/68. Stays mount-gated (CI-blind by design).
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Adjudication: the PIN was the drifted side. The 2026-09-10 freshness audit (armonissima #88) deliberately re-scoped the hardware-loop fence to
using Intonato— Strumento v0.2 inverted the reexport seam (Intonato, the chassis, now reexports Strumento, the substrate). The test pin dated to #1002's original fence comment; flipping it exposed a second-order fallout (the old fence comment minted anIntonatoclaim in the ten-claim inventory — the live fence names no symbol, so the live set is nine; inventory updated with the adjudication recorded in-test).Director gate: the mount-gated battery runs on this machine — RED proven first (exactly
expected [ 'Intonato' ] to deeply equal [ 'Strumento' ]), then the full file 68/68 including the environmental ext-scan sibling. Fixes #1193.