feat(harness): add Agent Map concept demo

[ynadge]

Summary

Adds a deterministic, browser-only Agent Map concept fixture for product and design review. It demonstrates a project-level planning conversation, iterative map revision and confirmation, simulated builder-session launch, injected child-session context, and per-agent step decomposition.

This is intentionally a concept surface, not a production graph-authoring implementation or prompt contract.

Changes

• Add the three-pane Agent Map walkthrough with a project rail, planning chat, and project map.
• Model project agents, a persisted resource, a connector, contract-bearing handoffs, and an owned subagent without putting ordinary capabilities on the project map.
• Add conversational proposal, refinement, confirmation, build-plan, launch, and reset phases.
• Add simulated Research and Publisher builder sessions with scoped startup-context layers and five implementation steps each.
• Preserve project-planner state when navigating between the Agent Map and child builder snapshots.
• Gate the fixture behind both VITE_MOCK=1 and ?mockFixtures=agent-map.
• Add reducer coverage and a complete Playwright walkthrough.

Motivation

The concept explores treating the Agent Map as a collaborative project plan created before implementation, rather than only as a post-hoc dependency graph inferred from existing agents. The confirmed map can then become shared context for scoped implementation sessions while keeping project topology separate from per-agent execution detail.

Testing

• Prettier check for all six changed files
• pnpm --filter @sapiom/harness exec vitest run web/src/lib/agent-map-demo.test.ts — 6/6 tests
• pnpm --filter @sapiom/harness typecheck
• VITE_MOCK=1 pnpm --filter @sapiom/harness build:web
• pnpm --filter @sapiom/harness build:web
• Verified the ordinary build emits no Agent Map demo chunk
• pnpm --filter @sapiom/harness exec playwright test --config web/e2e/playwright.config.ts agent-map-demo.spec.ts — 1/1 Chromium test

Interactive demo

Run from the repository root:

VITE_MOCK=1 pnpm --filter @sapiom/harness dev:web --host 127.0.0.1 --port 5299

Then open:

http://127.0.0.1:5299/?mockFixtures=agent-map

Use the prepared walkthrough through Approve and launch builders, then select either builder row to inspect its injected context and agent-specific steps.

Safety and scope

• No real agents, repositories, sessions, connectors, deployments, or network requests are created.
• The scripted state is browser-only and resets on reload.
• The builder composers are intentionally disabled.
• No production SystemGraph contract is widened or reused for graph authoring.
• Ordinary non-mock builds exclude the concept chunk.

Checklist

• Diff is limited to one logical concept fixture
• Existing Harness design tokens and component anatomy are reused
• No hardcoded secrets or production side effects
• Self-reviewed against current main