{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "name": "app-audit routing accuracy corpus",
  "version": "2.1.0",
  "purpose": "Routing-eval corpus for app-audit (adia-ui-factory plugin). Each phrase declares whether app-audit SHOULD be the routing target. Scored by the estate's TF-IDF routing-eval runner against the skill's description (heuristic token overlap).",
  "scoring_notes": "Heuristic signal, not ground truth. Treat misroutes as a prompt to tighten the skill description, never as a reason to keyword-stuff it. Real harness routing is LLM-driven.",
  "license": "internal",
  "scope": "app-audit routing \u2014 does this phrase activate app-audit (diagnose/recon/root-cause an EXISTING @adia-ai consumer repo), and does it correctly stay OUT of app-planning (classify a greenfield to plan a build), app-migration (the mechanical sweep AFTER a confirmed diagnosis), surface-qa (browser QA of a built surface), and screen-composition (author a new screen)?",
  "phrases": [
    {
      "id": "audit-health-01",
      "phrase": "audit this AdiaUI app",
      "expected": "app-audit",
      "expected_shape": "audit-health",
      "rationale": "Canonical audit request on an existing consumer repo."
    },
    {
      "id": "audit-health-02",
      "phrase": "review this @adia-ai codebase before we touch it",
      "expected": "app-audit",
      "expected_shape": "brownfield-recon",
      "rationale": "Recon-before-edit on an inherited repo."
    },
    {
      "id": "audit-health-03",
      "phrase": "I inherited a repo that uses @adia-ai \u2014 what state is it in",
      "expected": "app-audit",
      "expected_shape": "brownfield-recon",
      "rationale": "Inherited-repo health check."
    },
    {
      "id": "audit-current-01",
      "phrase": "is this app on the latest @adia-ai version",
      "expected": "app-audit",
      "expected_shape": "is-it-current",
      "rationale": "Version-currency question \u2014 the recon 3-tuple."
    },
    {
      "id": "audit-current-02",
      "phrase": "is our AdiaUI setup up to date or drifted",
      "expected": "app-audit",
      "expected_shape": "is-it-current",
      "rationale": "Drift-detection framing."
    },
    {
      "id": "audit-migrate-01",
      "phrase": "what should we migrate in this AdiaUI app",
      "expected": "app-audit",
      "expected_shape": "what-to-migrate",
      "rationale": "Diagnosis-first: the audit produces the ranked what, app-migration executes it."
    },
    {
      "id": "audit-wrong-01",
      "phrase": "the dashboard renders unstyled and broken, what's wrong",
      "expected": "app-audit",
      "expected_shape": "wrong-output-root-cause",
      "rationale": "Wrong-output symptom \u2192 the correction loop."
    },
    {
      "id": "audit-wrong-02",
      "phrase": "this screen doesn't match the reference, why",
      "expected": "app-audit",
      "expected_shape": "wrong-output-root-cause",
      "rationale": "Mismatch-vs-reference \u2192 root-cause triage."
    },
    {
      "id": "audit-wrong-03",
      "phrase": "the admin shell topbar looks mispositioned",
      "expected": "app-audit",
      "expected_shape": "wrong-output-root-cause",
      "rationale": "The Light-DOM zeroth-question archetype."
    },
    {
      "id": "audit-wrong-04",
      "phrase": "components render empty even though the data is set",
      "expected": "app-audit",
      "expected_shape": "wrong-output-root-cause",
      "rationale": "Silent no-op symptom \u2014 attribute/scheme drift."
    },
    {
      "id": "audit-gap-01",
      "phrase": "why does npm run dev fail to resolve @adia-ai imports",
      "expected": "app-audit",
      "expected_shape": "audit-health",
      "rationale": "Class-0 manifest-gap symptom."
    },
    {
      "id": "audit-gap-02",
      "phrase": "check this repo for hand-rolled things the library now ships",
      "expected": "app-audit",
      "expected_shape": "audit-health",
      "rationale": "Class-3 capability drift."
    },
    {
      "id": "audit-report-01",
      "phrase": "give me a health report on our AdiaUI consumer app",
      "expected": "app-audit",
      "expected_shape": "audit-health",
      "rationale": "The diagnostic-report deliverable."
    },
    {
      "id": "audit-recon-01",
      "phrase": "before I edit this brownfield surface, what's the repo's adoption state",
      "expected": "app-audit",
      "expected_shape": "brownfield-recon",
      "rationale": "Recon-earns-remediation, the core posture."
    },
    {
      "id": "adv-orient-01",
      "phrase": "we're starting a new internal claims tool on adia-ui, plan it",
      "expected": null,
      "expected_shape": "app-planning",
      "rationale": "GREENFIELD classification/planning \u2014 app-planning, not a brownfield audit."
    },
    {
      "id": "adv-migrate-01",
      "phrase": "run the migration sweep to bump @adia-ai from 0.6 to 0.8",
      "expected": null,
      "expected_shape": "app-migration",
      "rationale": "The mechanical sweep AFTER a confirmed plan \u2014 app-migration executes; audit only diagnoses."
    },
    {
      "id": "adv-verify-01",
      "phrase": "QA this screen in the browser and check a11y",
      "expected": null,
      "expected_shape": "surface-qa",
      "rationale": "Browser QA of a built surface \u2014 surface-qa, not repo diagnosis."
    },
    {
      "id": "adv-compose-01",
      "phrase": "build the settings screen from this plan",
      "expected": null,
      "expected_shape": "screen-composition",
      "rationale": "Authoring a new surface \u2014 the audit hands off to a builder, never authors."
    },
    {
      "id": "adv-release-01",
      "phrase": "cut a release and write the migration guide",
      "expected": null,
      "expected_shape": "adia-forge:package-release",
      "rationale": "Framework release engineering \u2014 a different plugin entirely."
    },
    {
      "id": "adv-generic-01",
      "phrase": "audit our npm dependencies for security vulnerabilities",
      "expected": null,
      "expected_shape": "none",
      "rationale": "Generic dependency audit unrelated to @adia-ai consumer health."
    }
  ],
  "minimums_per_spec": {
    "trigger_phrases": 14,
    "adversarial_phrases": 6,
    "task_shapes_covered": "audit-health, wrong-output-root-cause, is-it-current, what-to-migrate, brownfield-recon",
    "adversarial_fraction": "30%"
  },
  "evaluator_notes": "app-audit's tightest confusables are app-planning (greenfield vs brownfield) and app-migration (diagnose vs execute). The description leads with EXISTING/brownfield and fences both explicitly."
}
