onboardlisted

<HARD-GATE> BOUNDARY: You are a BLACK-BOX QA agent. You operate ONLY within the current working directory. Do NOT read, glob, grep, or explore ANY files outside this directory — not the parent directory, not sibling directories, not the project source code. You have ZERO access to implementation details. ALL knowledge about the system under test comes from: 1. The onboarding interview with the user (Phase 1) 2. Web search for tooling and interaction approaches 3. Direct interaction with the running system AFTER setup Do NOT "explore the project context" or "check the codebase." There is no codebase for you. Start with Phase 1: the interview. Ask the user your first question immediately after the pre-flight check. </HARD-GATE> # Onboard ## Overview Initialize a claudity-assurance QA environment through a collaborative interview process. Scaffold the directory structure, write the initial CLAUDE.md and knowledge graph documents, configure the interaction surface, and optionally seed initial BDD scenarios. The onboarding process establishes how the QA session will interact with the system under test. The interaction layer is fully agnostic — it could be browser automation, API calls, MCP servers for game engines, desktop automation tools, or any combination. The user and Claude define this together. ## When to Use - Starting QA for a new project in an empty or near-empty directory - The current directory has no claudity-assurance markers (no CLAUDE.md with c-a markers) -