Core of the CLI overhaul: adds the ProgramCliSurface type, snapshots
context-mill's cli-manifest.json into a build-time TS module (schema-validated
via ajv in prebuild — a fetched-but-invalid manifest fails the build), adds the
native + skill command factories, the `wizard audit` family with an interactive
picker (recommended leaf pre-highlighted), and the `wizard skill` catalog
(internal role hidden by default). Old single-purpose command entry files are
replaced by manifest-derived commands.

Manifest contract uses context-mill's role/command/skill/internal +
recommended vocabulary (renamed from the earlier surface/public/catalog +
default).

Generated-By: PostHog Code
Task-Id: 4debb1ba-a98a-494f-ba44-29df9fd1d87b

…cute

- flatSkillCommand: graceful fallback when a manifest entry is missing,
  instead of throwing at import (which took down the whole CLI); both flat
  commands now resolve by stable skillId
- command.ts: declare positionals so `skill [name]` parses under
  strictOptions; correct the `recommended` doc comment
- skill: `wizard skill` lists, `wizard skill <name>` runs, `wizard skill
  search <query>` searches; reject unknown skill names
- agentSkillConfig: add a run recipe so `wizard skill <name>` and the narrow
  audit leaves actually run (were silently skipped via skipAgent)
- family-picker: document the argv-bypass on the picker path
- tests: regression guard for the agentSkillConfig run recipe

Generated-By: PostHog Code
Task-Id: b42696d8-ac3c-4cd2-ba12-747a846b8c23

…ill id

AuditRunScreen picked the slide deck by checking
`session.skillId === 'events-audit'`, but context-mill renamed that skill
to `audit-events` (the bootstrap manifest and the programs-cli dispatch
test both use `audit-events`). The stale check silently fell through to
the comprehensive AUDIT_AREA_SLIDES, so `wizard audit events` showed the
wrong deck. Match the current id.

Generated-By: PostHog Code
Task-Id: 95407a79-1f13-4f1d-a37b-43fe4a62b857

Replaces the build-time CLI manifest snapshot with a runtime resolver
that reads cliEntries from skill-menu.json each invocation. Adding a
skill-backed subcommand is now a context-mill release; no wizard release
needed.

How it fits together:

  - dispatch-family.ts owns the runtime resolution. dispatchFamily(family,
    argv) tries the native handler registry first (today: just
    audit/web-analytics), then fetches skill-menu.json and matches
    parentCommand + command -> skillId. The comprehensive `audit all`
    keeps its specialized auditConfig; everything else runs through the
    generic agent-skill program with the resolved skillId injected.

  - family-command-factory.ts wraps dispatchFamily as a yargs Command
    (name: `<family> [skill]`). interactiveDefault opens the picker with
    native + live entries combined; the recommended leaf is
    pre-highlighted.

  - audit.ts collapses to one factory call. migrate.ts / revenue.ts swap
    flatSkillCommand for nativeCommandFactory now that the config has
    the right command name and skillId. skill.ts fetches the catalog
    at handler time instead of reading a baked snapshot.

Deletions:

  - audit-3000 retired (skill, screens, registry entry, agent-interface
    model branch, playground demo, screen-registry wiring)
  - skill-command-factory.ts + flat-skill-command.ts: the runtime resolver
    replaces both, including the empty-manifest fallback flat-skill-command
    existed to work around
  - cli-manifest.bootstrap.json, cli-manifest.schema.bootstrap.json,
    scripts/generate-cli-manifest.cjs, src/lib/programs/cli-manifest.generated.ts
  - ajv dev-dep; the generate-cli-manifest.cjs step in prebuild; three
    .gitignore lines covering the deleted bootstrap apparatus

Test surface: programs-cli mocks fetchSkillMenu and asserts dispatchFamily
routing (skill-backed, native, comprehensive). family-picker keeps its
auditCommand shape assertion but flipped to "no static children by design".
program-registry catches the revenue-analytics command-name rename.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>