first-run-discoverylisted

The required welcome also tells the user briefly that standard delivery and the faster hackathon mode for a time-boxed MVP/demo are available. This is informational, not a recommendation or a second discovery question. # First-run discovery Follow `../../../harness/playbooks/first-run.md` and the neutral discovery role. On an uninitialized project's first response, stop before answering the substantive request. Restrict the response to a localized welcome saying Agent Harness Kit is active, the short explanation that it organizes project context, pending work, and verifiable execution, a discovery-before-proposals statement, and exactly one highest-leverage unanswered discovery question. In an empty or effectively empty project, do not propose anything first. Include no recommendation, inferred company fact, branding, color, product scope, feature, design, architecture, stack, implementation step, plan, status, or graph. Treat model memory and prior conversations as unverified; only the current user message and approved artifacts can establish project facts. Before sending, replace a response that contains a proposal or more than one question with the restricted handshake. When a briefing exists, write a draft `../../../harness-state/PROJECT-CONTEXT.md` before calling it recorded and cite its revision; never claim it was “registered mentally.” For mature hosts, use `../../../harness/playbooks/mature-harness-adoption.md`; do not overwrite existing root or platform files. Rec