Description
About a third of agent-host/prompts/ asks Claude Code to clone and edit unrelated public repositories (tqdm, lodash, axios, chalk and others), which does not look like a sports newspaper engineering team at work and depends on third-party repos staying put. Every prompt is long, well-formed and ends with the same “no commits, no pushes, stay in the directory” boilerplate that dev-session already enforces through its appended system prompt and tool allowlist.
Acceptance Criteria
- #1 Each developer session starts in a small fictional Touchline codebase (site, odds feed, offers, editorial tooling) seeded into the container, with a git history
- #2 The prompt corpus is rewritten around that codebase per team (newsroom, trading, platform), mixing one-line questions, terse lowercase requests and longer tasks
- #3 Prompts no longer repeat the no-commit boilerplate, and the sandbox rules in dev-session still hold
- #4 Sessions still exercise the demo MCP server and the other gateway-pushed MCP servers
Definition of Done
- #1 just check
Implementation Plan
- Fictional Touchline codebase under agent-host/codebase with seed-repo creating a git history. 2. Rewrite prompts per team (newsroom, trading, platform) around it, mixed lengths, no boilerplate. 3. Keep MCP-exercising prompts. 4. dev-session seeds the repo per session.
Implementation Notes
Live on v0.2.0: first five dev_session lines all ran in the seeded repo (trading-overround-report, newsroom-preview-template-question, platform-runbook-update, platform-quick-route-question), rc 0; the conversation ‘why does /match/anything just 404 right now’ answered from the codebase. MCP coverage per prompt mapped in the lane report (touchline, time, fetch, git, memory, sequential-thinking, context7, deepwiki). Allowlist dropped git clone/ls-remote.
Final Summary
Developer sessions start in a seeded fictional Touchline Times repo (agent-host/codebase, 15 backdated commits by 6 authors, two planted failing tests) with 48 rewritten per-team prompts of mixed length and no boilerplate. Verified by seed-repo determinism checks, a prompt-format validator and live sessions.