integration

Runtime adapter over codemap-py integrate engine (src/codemap_py/integration.py). Targets Claude Code, Codex, or both. Never invokes another runtime's model; uses only its native plugin-manager CLI.

Five exact pinned CLI modes; retired check removed:

Mode	Args	Mutation	Exit
audit	[--runtime {claude,codex,both}] [--json] [--since YYYY-MM-DD]	none	0 pass/warn; 1 fail; 2 bad syntax
plan	[--runtime ...] [--consumers <csv>] [--source {local-candidate,release}] [--out <artifact>]	report artifact only	0; 2 bad syntax
apply	--plan <artifact> --approve <sha256>	verified source checkout only	0; 1 drift/fs; 2 bad approve/syntax
sync	--source {local-candidate,release} --plan <artifact> --approve <sha256> [--runtime ...]	local runtime plugin state	0; 1 partial-fail/journal; 2 bad approve
demo	[--runtime ...]	disposable evidence only	0; 1 fail

--approve requires explicit mutation mode (apply/sync), saved plan artifact, and its user-shown SHA-256. It never authorizes new targets, remote publication, Git history/remote mutation, marketplace or user instruction-file edits, or data deletion.

Closed integration/reinstall set: Claude consumers foundry, oss, develop, research (provider codemap-py); Codex consumer codex-rig (provider codemap-py). Explicit mapping, not discovery/extension registry; cross-check both marketplace and plugin manifests before mutation. --runtime codex: only codex-rig; --runtime claude: four Claude consumers; --runtime both or omitted: all five.

Shared-engine safety invariants:

• plan records schema/protocol version, op ID, exact targets, before-state hashes, desired versions/refs/hashes, exact argv, ordered ops, rollback identities, expected post-state, and plan SHA-256.
• Every mutation revalidates target + before-state immediately before action; drift invalidates approval.
• Source writes use before-images + atomic per-file replace; apply refuses foreign/modified markers, path escapes, symlinks, installed-cache roots, dirty working-tree overlap, and unverified product identity.
• sync refuses plans whose source is absent from selected candidate, installed bytes mismatch selected hash, or release/rollback evidence names mutable/default-branch source. No implicit "latest".
• First-target success + second-target failure stops immediately. Rollback performs only approved-plan actions. Claim completion/rollback only after post-state hash verification.
• "Push" means only (1) updating allowlisted version-controlled consumer source integration from codemap-py.integration.v2, and (2) installing/reinstalling those built plugin versions locally via native runtime CLI. Never git push, remote marketplace mutation, release publication, or direct installed-cache edits.

NOT for: structural queries (use /codemap-py:query-code); standalone index rebuilds (use /codemap-py:scan-codebase).

• $ARGUMENTS: optional:
  • Omitted or audit — zero-write inspection of provider, consumer, managed-block, index, runtime-log, and usage evidence.
  • plan — persist report artifact (targets, argv, hashes, rollback identities, plan SHA-256); no mutation.
  • apply — atomically update current-version managed blocks in allowlisted consumer source from approved plan.
  • sync — install/reinstall approved targets locally via native plugin-manager CLIs.
  • demo — run audit plus representative plain-vs-structural-context workflows; disposable evidence only.

Step 1: Resolve mode

Parse $ARGUMENTS case-insensitively: empty or starts audit → audit; plan → plan; apply → apply; sync → sync; demo → demo. Otherwise ask AskUserQuestion: "Unrecognized command $ARGUMENTS. Which of the five modes did you mean?" Options: (a) audit, (b) plan, (c) apply, (d) sync, (e) demo. Wait for reply.