Why: Refresh the WIP plan against Docs #103 before user review.
Evidence: origin/main 5909cb3; only the separate DHF plan note changed.
Impact: Includes current main without rewriting the feature branch.
Refs: Documents PR #100
Why: The approved written amendment needs executable, reviewable steps for explicit test accounting and independent native sandbox replay.
Evidence: Current Dev and RDM source inspection, failed Dev make test receipt, local KVM/tool availability, official Go, Ubuntu and QEMU documentation, plan link and diff checks.
Impact: Documents only. No candidate execution, runner configuration, source lock or gate behavior changes.
Refs: Documents design 1790cf8; Dev PR #537; Documents PR #100
Why: Nested Bubblewrap tests fail inside the credential-isolated candidate boundary, and a green main gate alone would hide unrun product isolation checks.
Evidence: Dev 1ea93a5 make test SELF receipt; Backend and RDM test inventory; RDM CI workflow inspection; diff and relative-link checks.
Impact: Adds a pending written design and index entry only. No execution behavior or source lock changes.
Refs: Dev PR #537; Documents PR #100; approved remediation plan 20ada84
Why: The review design, execution plan, and index still described the approved work as awaiting review or unimplemented.
Evidence: SELF Dev task commits e0c8686 through 76ad40c and the isolated governance receipts are referenced without claiming current-head CI. git diff --check and 80 relative links passed.
Impact: Documents now distinguishes completed local remediation from pending platform GATE, renewed stage 7 acceptance, and independent stage 8 review.
Refs: Agent-System-Dev #537; Agent-System-Documents #100; approved plan 20ada84
Why: Turn the approved written design into separately testable work that closes three Important Stage 8 findings before migration PRs can merge.
Evidence: SELF plan/spec coverage, interface, relative-link, placeholder, code-fence and whitespace checks passed; implementation and new-head gates remain NOT_RUN.
Impact: Add a six-task plan and record the design approval without changing Dev candidate code, CI or protected branches.
Refs: Agent-System-Documents#100, Agent-System-Dev#537, Stage 8 review
Why: The read-only candidate container cannot install its own toolchain, so define a separate trusted image build step.
Evidence: SELF design consistency and whitespace checks passed; full CI feasibility remains part of implementation validation.
Impact: Preserve the no-socket, read-only candidate boundary without claiming tools can be installed after the container is locked down.
Refs: Agent-System-Documents#100, Agent-System-Dev#537
Why: Specify the approved remediation direction for three Important findings from the independent dependency-migration review.
Evidence: SELF Markdown link and whitespace checks passed before commit; written design awaits human review and implementation validation.
Impact: Add a bounded design addendum for local/CI candidate isolation, fixed-rules retry and safe generated-workspace finish without changing product code.
Refs: Agent-System-Documents#100, Agent-System-Dev#537, Stage 8 review
Why: Include the completed merge-queue trial record before reviewing the versioned-dependency documentation branch.
Evidence: Current main and migration branch have disjoint changed paths; local merge-tree shows no conflict.
Impact: Preserve the approved migration proposal and implementation plan while retaining the newer trial report.
Refs: Agent-System-Documents#100, Agent-System-Documents#101, Agent-System-Dev#537
Why:
Authoritative Documents main advanced during this multi-repository task.
Evidence:
Read current main 7bd4e17827d4c7c88647bf3c9199c495b60cb107; the approved dependency spec and plan digests and 120 links remain unchanged.
Impact:
Retain current recovery and RDM proposal status updates without changing this task's approved requirements.
Refs:
R15; dependency-workspace U6/U7; Documents origin/main
Why:
Keep current upstream planning contracts and the approved dependency migration together without overwriting either entry.
Evidence:
SELF Dev doc checker validates R1-R15, U1-U8 and relative links against the merged Documents candidate.
Impact:
Merge current main and retain both planning index intents. Business implementations and acceptance histories remain unchanged.
Refs:
Documents a7ff466; Agent-System-Dev dependency-workspace and latest authoritative main.
Why:
Keep the approved migration scope and in-flight branch protection discoverable from the planning index.
Evidence:
SELF Dev evidence checks R1-R15, U1-U8, general standards boundaries and 116 relative links. Formal acceptance remains pending.
Impact:
Update current entry points without changing historical evidence or approval boundaries.
Refs:
Agent-System-Dev feature/dependency-workspace; approved versioned-dependency plan r1 and R15.
Why: Make the approved architecture executable while preserving current and future feature branches.
Evidence: The Dev task card records the successful resumed precheck and synchronization at the current main baseline. Implementation verification remains separate.
Impact: Record approved scope, R15 and the implementation plan; no deployed behavior or release is changed.
Refs: Versioned dependencies r1; feature/dependency-workspace
Why: Preserve independent repositories and a single Dev entry while reducing repeated submodule pins.
Evidence: SELF source inventory and documentation checks are recorded by Dev make evidence in the dependency-workspace task card. Migration checks remain NOT_RUN.
Impact: Add a proposed architecture and implementation sequence covering Go, frontend packages, RDM, build governance, and reusable standards. Active rules and runtime behavior are unchanged.
Refs: Dev feature/dependency-workspace; docs/proposals/2026-10-13-versioned-dependencies-and-workspaces.md r1
weichen