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: include the current integration baseline before verification.
Evidence: fetched origin/main=d5428c5f05fc5f625e6232ab3156b17f13e14d6a.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Existing upload history must stay private after project adoption, and final object evidence must remain traceable.
Evidence: Original tool receipts and independent reports saved byte-for-byte; new fixed combination and CI remain pending.
Impact: Select Backend d26f3cf and proposal r1.1 with unchanged public downstream contracts; preserve workspaces and live data.
Refs: feature/project-member-access; Frontend PR82; Documents PR97
Why: Shared project identity resolution is one private module used by app and server.
Evidence: Boundary scan passes 85 edges and its injected illegal-edge negative check; previous full run stopped at this documented boundary.
Impact: Add only app/server to projectscope and projectscope to store, without allowing transport/composition dependencies in the resolver.
Refs: system-project-membership proposal r1; feature/project-member-access
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=143e6367367760deceac91ac3de5ccb3ed6adebc.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Final review and real composition exposed member upload rejection, private project cards and stale duty selection.
Evidence: Component correction receipts and fixed clean source SHAs; independent replays and final composition are in progress.
Impact: Select Backend d2f96e7 and Frontend 2ba275b with current UI, preserving private originals and verified project commands.
Refs: feature/project-member-access
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=86d975b822c2384e96edd75f9c3a2dca63593b3a.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Host-only project creation and domain membership must form one verified identity.
Evidence: Tool-imported SELF receipts and independent Backend and Frontend replay attestations; composed acceptance and final CI remain in progress.
Impact: Advance fixed component pins and record the authorized implementation and privacy boundaries without deployment or runtime changes.
Refs: .task/feature-project-member-access.md; system-project-membership proposal r1
Why: retain the repeatable membership check and current integration checkpoint.
Evidence: SELF receipts in the task card; readiness fails on the reported data state.
Impact: diagnosis metadata only; product implementation remains pending stage review.
Refs: .task/feature-project-member-access.md
Why: a saved host-project membership has no registered RDM project or binding,
so member discovery and private conversation creation cannot resolve it.
Evidence: metadata-only read probes and forge scans are preserved as SELF
receipts in the task card; HTTP and browser replay remain NOT_RUN.
Impact: task documentation and read-only diagnostic helpers only; product
code, runtime databases and deployments are unchanged pending stage review.
Refs: .task/feature-project-member-access.md; policy/delivery.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-project-member-access.md; R0=55cecae703cf8c4f33185e9e4556597c11817b3b.
Impact: task metadata only; the feature workspace starts at 55cecae703.
Refs: .task/feature-project-member-access.md
weichen