@soleur/opencode 3.354.12 → 3.354.14
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -83,6 +83,8 @@ Two lessons from #9448 belong in every fix-agent and review-seat brief (full acc
|
|
|
83
83
|
- **A diff under `docs/legal/` or `knowledge-base/legal/` has no seat arm in `fix-round-seats.sh`, and a legal-wording fix needs the CLO agent, not a vote.** Add `soleur:legal:legal-compliance-auditor` to the panel and to every fix round by hand (the script prints `unknown-seat:` for it), brief the history seat to check published-baseline claims against `origin/main` rather than the panel SHA (a fix round that re-dates an entry reads as an overwrite against the panel SHA), and send every wording doubt to the CLO agent as one batched spawn with the seat reports attached. **Why:** PR #10326 -- see `knowledge-base/project/learnings/2026-10-15-my-correction-pr-wrote-only-and-no-where-the-code-read-showed-more.md`.
|
|
84
84
|
- **Seats share the session scratchpad, so a fixed-name pointer file (`sbx`, `mut.py`) is a collision.** On #10514 one seat overwrote another's sandbox pointer and ran its probes, including a hash-pinned `pip install`, inside the other seat's sandbox. Brief every seat to keep its sandbox path in its own shell variable or a seat-unique file name, and to re-run any result it measured after a pointer changed. See `knowledge-base/project/learnings/2026-10-19-a-newest-wins-reference-picked-my-own-unpushed-work-and-a-filtered-test-run-hid-an-import-error.md`.
|
|
85
85
|
|
|
86
|
+
- **A fix agent's "suite green" covers only the files it was given; brief it on the repo-global ratchets by name, and run the combined-tree gate BEFORE the fix-round panel.** Editing a floor means running `scripts/guard-vacuity-floor.test.sh` (its floor detector parses only `-lt|-le|-ge`, so a `-ne` rewrite drops the file from the promoted set); adding a test that reads outside `apps/web-platform` means registering it in `test/repo-wide-suites.ts` (`repo-wide-containment.test.ts`); refactoring a symbol another test pins as source text means `git grep` of the old literal across `test/`. The lead then runs the affected gate or those suites by name on the COMBINED tree before spawning seats, so the panel reviews a tree that already passes; an affected gate that prints `ran=- of=-` / `budget-deferred` (queued behind sibling runs) is no verdict. **Why:** #10892 — three disjoint-scope fix agents each reported green and together broke all three gates; two panel seats found them by running suites nobody had touched. See `knowledge-base/project/learnings/2026-10-23-fix-round-agents-reported-green-on-their-own-files-and-broke-three-repo-global-gates.md`.
|
|
87
|
+
|
|
86
88
|
## Dedup-before-fixing ledger
|
|
87
89
|
|
|
88
90
|
§5 Step 1's "Remove duplicate or overlapping findings" becomes a required emitted artifact, produced **before any fix dispatch**:
|