[K1-D1][Dogfood] 5-day real-work validation under Arckeep identity

[Dylan5237]

Parent control plane: #2
Parent stabilization gate: #16

Status: PAUSED BEFORE DAY 1 — ACTIVATION STEP 5 READY

The previous ACTIVE — DAY 1 marker is explicitly not counted.

#34 Dogfood Quick Capture + Start Menu launcher has passed Architecture Review + Human Visual Gate and is merged.

Activation steps 1–4 are complete:

• deterministic merged build created from develop/kcc-1.0@8a067fa29e32af68634660cfe24797c930a76584;
• build-info.json confirms sourceBranch=develop/kcc-1.0 and exact source commit 8a067fa29e32af68634660cfe24797c930a76584;
• stable executable exists at D:\_projects\tools\kcc-workbench-wt-package-dev\dist-fast\win-unpacked\Arckeep.exe;
• current-user Start Menu shortcut Arckeep.lnk is installed and COM-readback confirms it points exactly to that stable executable.

A pre-existing R2 candidate had been holding the real default profile/single-instance lock. Per process-safety rules the Agent stopped with HUMAN_ACTION_REQUIRED; the user has now manually closed that old instance.

Final activation step is now READY:

1. launch Arckeep from the Start Menu shortcut;
2. confirm the merged build starts normally under the real profile;
3. confirm Kimi surface, Dogfood note button, icon-only refresh, Dogfood Inbox, and merged build provenance;
4. if PASS, mark Day 1 ACTIVE immediately.

Do not count dogfood time until this final Start Menu launch smoke passes.

Purpose

Use the stabilized KCC 1.0 Electron runtime under the Arckeep identity in real daily work for five actual usage days. The purpose is not to add features; it is to collect product-truth evidence about whether Arckeep is genuinely usable as the user's daily AI workbench.

Evidence capture

Once Day 1 restarts, prefer the in-app Dogfood Inbox from #34 for fast capture of:

• 问题;
• 想法;
• 正向反馈.

Do not turn every observation into an implementation issue immediately. Capture first; create a fix WP only when it is P0/P1, risks state/auth/data integrity, or recurs enough to materially damage daily usability.

Paths to watch closely

1. Startup / reopen usability.
2. Kimi ↔ CloudCLI switching without session loss.
3. CloudCLI endpoint/origin/auth continuity ([K1-S0.2][P1] CloudCLI repeatedly asks for login instead of reusing local auth #18).
4. Viewer passive recording without opening Viewer during work ([K1-P1] Viewer recording must arm on session change without opening Viewer #23).
5. Viewer realtime change delivery ([K1-S0.1][P1] Viewer realtime artifact updates are unreliable #17).
6. Existing userData/session/window/settings continuity after Arckeep identity swap ([K1-S0.5][P2] Replace KCC 1.0 app identity with Arckeep name/logo only #20).
7. Development update loop / deterministic packaging ([K1-S0.3] Deterministic development packaging from develop/kcc-1.0 #25/[K1-S0.4][P1] Reduce KCC startup latency and development package turnaround #19).
8. Dogfood Inbox itself must not disrupt the active Agent surface or Viewer recording ([K1-D0][P1] Dogfood Quick Capture + Start Menu launcher #34).

Completion gate

After five actual usage days, synthesize recurring friction, positive stable paths, workarounds, and product direction. Do not pre-decide that Arckeep 2.0 resumes; the dogfood evidence decides.

Safety

• destructive mutation of real auth/profile data requires explicit human approval;
• Agents may terminate only PIDs they spawned and tracked;
• pre-existing app/profile/single-instance locks require HUMAN_ACTION_REQUIRED rather than force-kill.