browser/openspec/changes/verify-current-platform-e2e-baseline/tasks.md

1. Baseline Report Structure

• 1.1 Add a proof report under openspec/changes/verify-current-platform-e2e-baseline/ that lists every required flow, classification (real, partial, demo-only, blocked), evidence, and follow-up recommendation.
• 1.2 Define the required flow matrix for platform APIs, run channels, platform_web pages, and plugin capability boundaries.
• 1.3 Ensure non-real classifications identify the smallest follow-up OpenSpec needed to close the gap.

2. Platform and Storage Verification

• 2.1 Run cd platform && go test ./... -count=1 and record evidence.
• 2.2 Run platform API/storage smoke coverage for auth/session, users, server instances, plugin marketplace, AI providers, jobs, logs, artifacts, config diff/write, and file dispatch; record exact command(s) used.
• 2.3 Classify each platform API area as real, partial, demo-only, or blocked, including whether data is durable, in-memory, seed-only, or unavailable.

3. Run and Channel Verification

• 3.1 Run cd run && go test ./... -count=1 and record evidence.
• 3.2 Verify run control hello/heartbeat, job claim/ack/progress/result, lifecycle install/start/stop execution, log spool/ingest acknowledgement, and artifact chunk/resume/checksum behavior; record exact command(s) used.
• 3.3 Verify or classify whether artifact/file transfer remains independent from control heartbeat, job ack/result, and durable log ingest.

4. Plugin Verification

• 4.1 Run cd plugins && npm run typecheck && npm run test && npm run validate:manifest and record evidence.
• 4.2 Verify plugin manifests, SDK bridge requests, plugin page execution requests, AI invocation requests, and file/config/log/run capability payloads remain platform-mediated.
• 4.3 Classify whether current game management plugins can perform real multi-instance server operations or only render/request demo or partial behavior.

5. Frontend and Browser Walkthrough

• 5.1 Run cd platform_web && npm run typecheck && npm test && npm run build and record evidence.
• 5.2 Start the required local stack for browser verification. Record the exact command(s), such as cd platform_web && VITE_ENABLE_LOCAL_AUTH_FALLBACK=true npm run dev -- --port 5173, plus any platform/run service commands needed for API-backed proof.
• 5.3 In a browser, walk through 首页、服务器管理、插件市场、用户管理、AI 提供商管理, and personal/account navigation. Record for each page whether it is API-backed, local fallback, seed data, inaccessible, or blocked.
• 5.4 In the browser, exercise or inspect server lifecycle controls, plugin marketplace actions, user create/status actions, AI provider create/test/status actions, config diff/write dispatch, log history, artifact download/file transfer, and plugin bridge actions where available.
• 5.5 Verify visible UI state does not expose raw host paths, run credentials, direct sockets, raw AI keys, or plugin-owned transport details.

6. Baseline Classification and Queue Handoff

• 6.1 Complete the proof report with command output summaries and browser walkthrough notes.
• 6.2 Identify follow-up implementation OpenSpecs for every partial, demo-only, or blocked required flow.
• 6.3 Run scripts/check-structure.sh and record evidence.
• 6.4 Run openspec validate verify-current-platform-e2e-baseline --strict and record evidence.
• 6.5 Update openspec/changes/architecture-delivery-stream/delivery-plan.md and openspec/changes/architecture-delivery-stream/NEXT_CHANGE.md only after implementation evidence exists, then stop without starting another backlog item.

Evidence

• 2026-07-08: cd platform && go test ./... -count=1 passed; packages api, config, domain, dto, model, repo, service, and validator reported ok.
• 2026-07-08: cd run && go test ./... -count=1 passed; packages api, config, protocol, runtime, and spool reported ok.
• 2026-07-08: cd plugins && npm run typecheck passed.
• 2026-07-08: cd plugins && npm run test passed; Vitest reported 1 file / 10 tests.
• 2026-07-08: cd plugins && npm run validate:manifest initially failed inside the sandbox with listen EPERM for the tsx IPC pipe, then passed with approved escalation and printed validated examples/dev-game-plugin/manifest.json.
• 2026-07-08: cd platform_web && npm run typecheck passed.
• 2026-07-08: cd platform_web && npm test passed; Vitest reported 11 files / 47 tests.
• 2026-07-08: cd platform_web && npm run build passed; Vite built dist/ assets.
• 2026-07-08: Browser walkthrough required cd platform_web && VITE_ENABLE_LOCAL_AUTH_FALLBACK=true npm run dev -- --port 5173; sandbox run failed with listen EPERM 127.0.0.1:5173, then approved escalation served the frontend at http://127.0.0.1:5174/.
• 2026-07-08: Browser auth page showed 本地回退可用 and 进入本地回退工作台, proving the local browser stack did not have real auth API backing.
• 2026-07-08: Browser fallback server workspace at #/servers showed 服务器列表加载失败 with path /api/v1/jobs was not found.
• 2026-07-08: Browser routes #/home, #/plugins, #/users, and #/aiProviders rendered/redirected to the fallback server workspace for the server-admin fallback user, so platform-admin first-party areas remain browser-blocked in this baseline.
• 2026-07-08: Browser #/profile rendered 个人设置 as 本地会话 with editable profile/theme controls; this proves local fallback UI only, not API persistence.
• 2026-07-08: openspec/changes/verify-current-platform-e2e-baseline/proof-report.md records the classification matrix and follow-up recommendations.
• 2026-07-08: scripts/check-structure.sh passed.
• 2026-07-08: openspec validate verify-current-platform-e2e-baseline --strict reported the change is valid; PostHog telemetry flush failed due restricted DNS and did not affect validation.
• 2026-07-08: Updated openspec/changes/architecture-delivery-stream/delivery-plan.md to mark verify-current-platform-e2e-baseline complete and fix-env-profile-settings blocked; updated openspec/changes/architecture-delivery-stream/NEXT_CHANGE.md to point at generating implement-real-game-plugin-lifecycle-proof.