Why: The approved r0.3 plan must run against the current project member and IAM mainline.
Evidence: First task-sync conflict receipt was imported; Backend full Go tests and Frontend test/build passed after resolving component interactions; git diff --cached --check passed.
Impact: Combine current main with the existing U3 draft, preserving both planning entries and the Backend private project event proof transaction.
Refs: Dev PR #512; Backend PR #193; Frontend PR #79; Documents PR #95
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-d1-closeout-evidence.md(PR#517) — merges verified via git log --merges against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: The reviewable plan needs a fixed Dev combination and complete tool-written verification receipt.
Evidence: make test && make build exit 0 on Dev 73bb827; SELF receipt 02567630b483ace3feaa12e227d50de63205d76fe76e6ac266085dbda50b7535 imported by make evidence.
Impact: Task evidence only; r0.3 semantic implementation and paid quality remain NOT_RUN.
Refs: Dev PR #512; Documents PR #95
Why: The r0.2 real-model sample failed semantic quality, and the user approved the r0.3 written design for detailed planning.
Evidence: Prior r0.2 A01 report and imported SELF receipts remain in the task card; plan self-review and git diff --cached --check passed.
Impact: Pin Documents f608ae5 and update planning state; implementation and paid model trials remain gated.
Refs: Documents PR #95; Dev PR #512
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=69c5c84d8a2f1a7966ebfb809cbb26d54e8e8abb.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The failed A01 needs a documented next design while the six PRs remain draft and unmerged.
Evidence: Independent semantic FAIL and the committed r0.3 spec with resolved links and explicit no-paid/no-implementation boundary.
Impact: Project entry and task card point to a pending design review; no new semantic behavior is enabled.
Refs: U3 r0.2 A01 assessment, r0.3 design
Why: The first rerun stopped at the dirty-worktree guard while the serial rerun completed both test and build.
Evidence: make evidence imported exit-0 receipt 3ea47713 at Dev f8c7650; original exit-2 receipt remains.
Impact: The failed model quality decision is unchanged and current-head GATE remains pending.
Refs: U3 r0.2 A01 assessment
Why: An in-flight Documents edit correctly blocked build after the first post-sample test phase.
Evidence: Full exit-2 SELF receipt imported by make evidence; Documents report committed at 4971d0d with archive hashes.
Impact: The candidate now has a clean composition for a serial full rerun; model-quality FAIL is unchanged.
Refs: U3 r0.2 A01 assessment
Why: Keep complete archive verification after the active card is moved.
Evidence: Original SELF synchronization and scoped diff receipts confirm no product or unrelated card changes.
Impact: Task records only.
Refs: Dev #526; RDM #354
Why: The approved base and downstream project membership delivery has reached its merge endpoint.
Evidence: Dev #526 and RDM #354 actual merge records, exact-head gates and independent reviews are preserved with original source labels.
Impact: Archive this task and record the separately authorized deployment follow-up; no product change, worktree cleanup or 8788 write.
Refs: Dev #526; RDM #354
Why: task-sync flagged the earlier rows as recorded with uncommitted script
changes; the gate requires key checks re-run at a committed head.
Evidence: SELF row via make evidence - 25/25 PASS on a fresh rdm@84ca64f
disposable instance.
Impact: task card only.
Refs: task feature/rdm-increment-settings-duties.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=ee9b437b22b49f96e1bc65f79417b22e8e82a37c.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: with the four-repo v0.4.0 release live, the account.list query/name
passthrough (RDM #356) enables the deferred full assertion of scenario 2; the
harness also needed v0.4.0 adaptations discovered on the combo instance.
Evidence: tool-written rows on the card - full ten-scenario run on a disposable
rdm@84ca64f combo instance (25/25 PASS incl. 2b name-substring, 2c
case-insensitive owner filter, 2d limit truncation), and dev service status
(rdm@84ca64f running against the live dev database, auth gate 401).
Harness fixes: rdm.project.member.setRole renamed to set-role (RDM #350);
command envelope parsed via payload; re-login after the password gate (base
#195 revokes sessions on password change); RDM world provisioning via
rdm.project.create + bind with the domain admin self-removing so owner2 is the
sole owner (creator is seeded as owner); scenario 8b asserts allow:true in the
current response shape; scenario 10b now meaningful (base #195 admits member
conversations through RDM project membership).
Impact: integration script and task card only; no product code.
Refs: task feature/rdm-increment-settings-duties; RDM #356; base v0.4.0 tags.
Why: The authorized r0.2 trial had an unsupported stage inference, while replay exposed two separate diagnostic-control defects.
Evidence: Exact paid-run files and tool-imported receipts, independent REPLAY, and Backend RED-to-GREEN/full-suite checks.
Impact: U3 quality remains FAIL; the new Backend code has no paid-model acceptance and all PRs stay draft.
Refs: U3 quality implementation plan r0.2, Task 6
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=ee9b437b22b49f96e1bc65f79417b22e8e82a37c.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Continue the approved downstream delivery after owner-published tags.
Evidence: RDM formal tag test is captured by its evidence wrapper; PR #354 is under final review and CI.
Impact: Task continuity only; preserve unrelated active cards and all worktrees.
Refs: Dev #526; RDM #354
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=20e086e48b9cec7f300feba5342db7a0661a4d4e.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Backend #195 and Frontend #82 (parallel task feature/project-member-access)
merged after the original targets (Backend 15566f9 / Frontend c294835), and Dev
main 20e086e pins exactly those new heads (5d5fc989/eb2d6d32). Tagging the stale
SHAs would make RDM pins->v0.4.0 a downgrade versus Dev main, so the release must
land on current main HEADs; the checkout origin/main command already does this.
Evidence: SELF rows on the card - four-repo ls-remote (main HEADs recorded, all
v0.4.0 tag refs empty), git ls-tree origin/main pins, and 15566f9../42cda9c0..
commit ranges showing the parallel merges.
Impact: Dev task card release-plan section only; no code or pins change.
Refs: task feature/rdm-increment-settings-duties; related Backend #195,
Frontend #82, Dev #527.
Why: Base merge and downstream completion have distinct authority and validation boundaries.
Evidence: Exact CI head, runner identity, actual merge tree and component commits verified; original platform and tool records preserved.
Impact: Save the handoff for owner-run tags and later RDM pin consumption, without deployment or cleanup.
Refs: Dev526 Backend195 Frontend82 Documents97
Why: The final umbrella head needs its own gate after main components merge.
Evidence: Final task-sync receipt saved; candidate and merged component trees match.
Impact: Task-only checkpoint, keeping the same implementation and runtime boundary.
Refs: Dev PR526; project-member-access
Why: The final base combination must reference actual reviewed main commits.
Evidence: Component PRs are merged, and each merged tree matches the independently tested candidate; whole review receipts remain unmodified.
Impact: Advance gitlinks and preserve acceptance evidence; new exact-head CI follows with no runtime changes.
Refs: Backend195 Frontend82 Documents97; feature/project-member-access
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d2c23f3a55a77711ded4328aa6215d9469c2b420.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Final merge gates require the latest main and exact component ancestry.
Evidence: Tool-written task-sync passed; Frontend tree equality preserves functional replay evidence while current HEAD CI will run again.
Impact: Task record only; no product source change.
Refs: feature/project-member-access
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=946cc13c9a10a2023a766b211e1148e625b62943.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The composed candidate and its validation limits must be available for independent review and current-head CI.
Evidence: Original receipts, fixed manifests, independent identities and real before/after task outcomes are preserved without source relabeling.
Impact: Archive acceptance and gate references in the canonical task; no product code, deployment or live data changes.
Refs: feature/project-member-access; Backend195 Frontend82 Documents97
Why: The distinct one-shot evaluation gate changed the Backend and Dev SHAs.
Evidence: make evidence imported exit-0 make test && make build at 894312f; Backend platform run 2940 passed at d89c72e.
Impact: The candidate remains draft and the paid A01 quality gate remains NOT_RUN.
Refs: U3 quality implementation plan r0.2, Task 6 preparation
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d5428c5f05fc5f625e6232ab3156b17f13e14d6a.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
weichen