2026-07-03-unlock-red-dot-owner-07

⟦tag:v2|session|2026-07-03-unlock-red-dot-owner-07⟧ kind: session id: 2026-07-03-unlock-red-dot-owner-07 role tag: ⟦tag:v2|role|pm⟧ task tag: ⟦tag:v2|task|2026-07-03-unlock-red-dot-owner⟧ threadId: 019ef43b-9618-7282-9c65-7f8dcdc6f6c7 loop state: summarized dispatch state: standby

completed:

• worker callback absorbed.
• stalled evidence from 2026-07-03-unlock-red-dot-owner-06 absorbed.
• replacement repair lane [短工]#unlock接线闭环修阻@v1.0 的 canonical formal callback 已从 worker 019f320b-b182-7f01-96a6-a97295f15943 吸收到当前 功能解锁与红点 owner 控制面。
• ../../../src/utils/onboardingSteps.ts 已新增 ONBOARDING_TAB_UNLOCK_FLOW_KEY，[../../../src/App.tsx](../../../src/App.tsx) 已把 hasExperiencedTabUnlockFlow 接入 App.tsx -> OnboardingCoach -> onboardingSteps 链路，并完成最小 build 验证。
• 重复 repair 线程 019f320f-6e68-7002-b9e9-2478f27e233c 与 019f3210-f4e0-7813-8fab-7c116780db4b 继续只按 transport duplicate / historical noise 处理，不进入 live gate。

incomplete:

• [短工]#功能解锁-红点定向回归验收@v1.0 继续未派发；不得从本回包、stalled evidence 或 worktree drift 直接外推为已启动。
• 本轮只修 unlock / unveil 接线闭环，没有进入 src/redDot/** 或补完整 runtime 回归证据。

blockers:

• none

next action:

• none; callback absorbed. Keep ⟦tag:v2|task|2026-07-03-unlock-red-dot-owner⟧ active with the current lane closed; any follow-up must reopen from the live owner task and shortlist, and must not infer 功能解锁-红点定向回归验收 sibling-lane start from this callback alone.

worker prompt:

[短工]#unlock接线闭环修阻@v1.0

这是对当前 unlock child lane 的替换修阻，不是 sibling lane，不要并开其它短工。

truth source checked:
- docs/handoff/index.md
- docs/handoff/current-dispatch-shortlist.md
- docs/handoff/tasks/2026-07-03-unlock-red-dot-owner.md
- docs/handoff/sessions/2026-07-03-unlock-red-dot-owner-06.md
- src/utils/onboardingSteps.ts
- src/App.tsx

当前已知真值：
- 旧 lane `[短工]#揭幕触发与红点接线收束@v1.0` 的 worker `019f3106-3a78-7da0-8a0e-646babe9e13c` 只有 commentary，没有 formal callback pack。
- `src/utils/onboardingSteps.ts` 已切到 `hasExperiencedTabUnlockFlow`，但原先 `src/App.tsx` 仍在给 `OnboardingCoach` 传旧字段 `unlockedTabsCount`。
- 所以当前问题不是单纯 waiting for callback，而是接线未闭环。

你只做这 1 条 repair lane。

file boundaries:
- src/App.tsx
- src/utils/onboardingSteps.ts
- src/utils/tabUnlockConfig.ts
- 必要时只读 src/utils/unveilTriggers.ts
- 必要时最小触碰 src/components/OnboardingCoach.tsx
- 必要时最小触碰 src/components/welcome/WelcomeGate.tsx

acceptance:
- 把 `hasExperiencedTabUnlockFlow` 在 `App.tsx -> OnboardingCoach -> onboardingSteps` 这条链上接到真实 unlock / unveil 口径，形成闭环。
- 若有代码改动，完成最小 build 验证。
- 如果按当前边界无法安全闭环，就回 formal blocker，明确说明边界为何不足。

not doing:
- 不改 docs/handoff/**
- 不进入 src/redDot/**
- 不开 `[短工]#功能解锁-红点定向回归验收@v1.0`
- 不扩到 item / Year1 / tools
- 不输出整段 git diff

formal callback pack:
- completed
- incomplete
- blockers
- next action
- evidence

evidence:

• docs/handoff/index.md
• docs/handoff/current-dispatch-shortlist.md
• docs/handoff/tasks/2026-07-03-unlock-red-dot-owner.md
• docs/handoff/sessions/2026-07-03-unlock-red-dot-owner-06.md
• ../../../src/utils/onboardingSteps.ts
• ../../../src/App.tsx
• worker 019f320b-b182-7f01-96a6-a97295f15943