@memnexus-ai/mx-agent-cli 0.1.294-next.0 → 0.1.295-next.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/__tests__/agents-md-canonicalization.test.js +31 -1
- package/dist/__tests__/agents-md-canonicalization.test.js.map +1 -1
- package/dist/__tests__/behavioral-extraction.test.js +50 -0
- package/dist/__tests__/behavioral-extraction.test.js.map +1 -1
- package/dist/__tests__/bootstrap-behavioral-contract.test.js +6 -3
- package/dist/__tests__/bootstrap-behavioral-contract.test.js.map +1 -1
- package/dist/__tests__/bundle-config.test.js +28 -2
- package/dist/__tests__/bundle-config.test.js.map +1 -1
- package/dist/__tests__/catalog-interaction.test.d.ts +25 -0
- package/dist/__tests__/catalog-interaction.test.d.ts.map +1 -0
- package/dist/__tests__/catalog-interaction.test.js +269 -0
- package/dist/__tests__/catalog-interaction.test.js.map +1 -0
- package/dist/__tests__/catalog-named-memories.test.d.ts +2 -0
- package/dist/__tests__/catalog-named-memories.test.d.ts.map +1 -0
- package/dist/__tests__/catalog-named-memories.test.js +204 -0
- package/dist/__tests__/catalog-named-memories.test.js.map +1 -0
- package/dist/__tests__/catalog-origin-main.test.d.ts +15 -0
- package/dist/__tests__/catalog-origin-main.test.d.ts.map +1 -0
- package/dist/__tests__/catalog-origin-main.test.js +296 -0
- package/dist/__tests__/catalog-origin-main.test.js.map +1 -0
- package/dist/__tests__/catalog.test.d.ts +2 -0
- package/dist/__tests__/catalog.test.d.ts.map +1 -0
- package/dist/__tests__/catalog.test.js +131 -0
- package/dist/__tests__/catalog.test.js.map +1 -0
- package/dist/__tests__/cli-build-integration.test.d.ts +2 -0
- package/dist/__tests__/cli-build-integration.test.d.ts.map +1 -0
- package/dist/__tests__/cli-build-integration.test.js +64 -0
- package/dist/__tests__/cli-build-integration.test.js.map +1 -0
- package/dist/__tests__/cli-build.test.d.ts +2 -0
- package/dist/__tests__/cli-build.test.d.ts.map +1 -0
- package/dist/__tests__/cli-build.test.js +640 -0
- package/dist/__tests__/cli-build.test.js.map +1 -0
- package/dist/__tests__/codex-deploy-config.test.js +60 -0
- package/dist/__tests__/codex-deploy-config.test.js.map +1 -1
- package/dist/__tests__/completion-rows-discriminate.test.d.ts +20 -0
- package/dist/__tests__/completion-rows-discriminate.test.d.ts.map +1 -0
- package/dist/__tests__/completion-rows-discriminate.test.js +481 -0
- package/dist/__tests__/completion-rows-discriminate.test.js.map +1 -0
- package/dist/__tests__/config-fidelity-archived-symlinks.test.d.ts +2 -0
- package/dist/__tests__/config-fidelity-archived-symlinks.test.d.ts.map +1 -0
- package/dist/__tests__/config-fidelity-archived-symlinks.test.js +127 -0
- package/dist/__tests__/config-fidelity-archived-symlinks.test.js.map +1 -0
- package/dist/__tests__/config-fidelity-display.test.d.ts +2 -0
- package/dist/__tests__/config-fidelity-display.test.d.ts.map +1 -0
- package/dist/__tests__/config-fidelity-display.test.js +77 -0
- package/dist/__tests__/config-fidelity-display.test.js.map +1 -0
- package/dist/__tests__/config-fidelity.test.js +166 -33
- package/dist/__tests__/config-fidelity.test.js.map +1 -1
- package/dist/__tests__/config-generation-gate.test.js +78 -0
- package/dist/__tests__/config-generation-gate.test.js.map +1 -1
- package/dist/__tests__/config-sync.test.js +35 -0
- package/dist/__tests__/config-sync.test.js.map +1 -1
- package/dist/__tests__/coordination-401-production-wiring.test.js +12 -7
- package/dist/__tests__/coordination-401-production-wiring.test.js.map +1 -1
- package/dist/__tests__/coordination-401-recovery.test.js +39 -32
- package/dist/__tests__/coordination-401-recovery.test.js.map +1 -1
- package/dist/__tests__/coordination-brief-pin.test.js +21 -8
- package/dist/__tests__/coordination-brief-pin.test.js.map +1 -1
- package/dist/__tests__/coordination-client.test.js +227 -3
- package/dist/__tests__/coordination-client.test.js.map +1 -1
- package/dist/__tests__/coordination-credential-endpoint.test.d.ts +24 -0
- package/dist/__tests__/coordination-credential-endpoint.test.d.ts.map +1 -0
- package/dist/__tests__/coordination-credential-endpoint.test.js +1230 -0
- package/dist/__tests__/coordination-credential-endpoint.test.js.map +1 -0
- package/dist/__tests__/coordination-memory.test.js +20 -4
- package/dist/__tests__/coordination-memory.test.js.map +1 -1
- package/dist/__tests__/coordination-provision.test.js +22 -14
- package/dist/__tests__/coordination-provision.test.js.map +1 -1
- package/dist/__tests__/coordination-status-registration.test.d.ts +16 -0
- package/dist/__tests__/coordination-status-registration.test.d.ts.map +1 -0
- package/dist/__tests__/coordination-status-registration.test.js +480 -0
- package/dist/__tests__/coordination-status-registration.test.js.map +1 -0
- package/dist/__tests__/coordination-token-multitenant.test.js +11 -11
- package/dist/__tests__/coordination-token-multitenant.test.js.map +1 -1
- package/dist/__tests__/coordination-token.test.js +35 -28
- package/dist/__tests__/coordination-token.test.js.map +1 -1
- package/dist/__tests__/creation-pr-class-check.test.d.ts +17 -0
- package/dist/__tests__/creation-pr-class-check.test.d.ts.map +1 -0
- package/dist/__tests__/creation-pr-class-check.test.js +346 -0
- package/dist/__tests__/creation-pr-class-check.test.js.map +1 -0
- package/dist/__tests__/digest-team-omission.test.d.ts +15 -0
- package/dist/__tests__/digest-team-omission.test.d.ts.map +1 -0
- package/dist/__tests__/digest-team-omission.test.js +247 -0
- package/dist/__tests__/digest-team-omission.test.js.map +1 -0
- package/dist/__tests__/doctor-worktree-path.test.d.ts +17 -0
- package/dist/__tests__/doctor-worktree-path.test.d.ts.map +1 -0
- package/dist/__tests__/doctor-worktree-path.test.js +158 -0
- package/dist/__tests__/doctor-worktree-path.test.js.map +1 -0
- package/dist/__tests__/fleet-data.test.js +40 -7
- package/dist/__tests__/fleet-data.test.js.map +1 -1
- package/dist/__tests__/fleet-tmux.test.js +2 -2
- package/dist/__tests__/fleet-tmux.test.js.map +1 -1
- package/dist/__tests__/generate-claude.test.js +137 -3
- package/dist/__tests__/generate-claude.test.js.map +1 -1
- package/dist/__tests__/git-env.test.d.ts +14 -0
- package/dist/__tests__/git-env.test.d.ts.map +1 -0
- package/dist/__tests__/git-env.test.js +131 -0
- package/dist/__tests__/git-env.test.js.map +1 -0
- package/dist/__tests__/git-identity-isolation.test.d.ts +33 -0
- package/dist/__tests__/git-identity-isolation.test.d.ts.map +1 -0
- package/dist/__tests__/git-identity-isolation.test.js +626 -0
- package/dist/__tests__/git-identity-isolation.test.js.map +1 -0
- package/dist/__tests__/hook-heal.test.js +17 -0
- package/dist/__tests__/hook-heal.test.js.map +1 -1
- package/dist/__tests__/init-coordination-url.test.d.ts +11 -0
- package/dist/__tests__/init-coordination-url.test.d.ts.map +1 -0
- package/dist/__tests__/init-coordination-url.test.js +114 -0
- package/dist/__tests__/init-coordination-url.test.js.map +1 -0
- package/dist/__tests__/memory-autocreate.test.js +574 -8
- package/dist/__tests__/memory-autocreate.test.js.map +1 -1
- package/dist/__tests__/memory-log-result.test.d.ts +13 -0
- package/dist/__tests__/memory-log-result.test.d.ts.map +1 -0
- package/dist/__tests__/memory-log-result.test.js +113 -0
- package/dist/__tests__/memory-log-result.test.js.map +1 -0
- package/dist/__tests__/memory-named-exists.test.d.ts +16 -0
- package/dist/__tests__/memory-named-exists.test.d.ts.map +1 -0
- package/dist/__tests__/memory-named-exists.test.js +288 -0
- package/dist/__tests__/memory-named-exists.test.js.map +1 -0
- package/dist/__tests__/mx-agent-cli-pin-validation.test.js +23 -47
- package/dist/__tests__/mx-agent-cli-pin-validation.test.js.map +1 -1
- package/dist/__tests__/mx-agent-cli-version-pin.test.js +34 -88
- package/dist/__tests__/mx-agent-cli-version-pin.test.js.map +1 -1
- package/dist/__tests__/new-project-first-team.test.d.ts +15 -0
- package/dist/__tests__/new-project-first-team.test.d.ts.map +1 -0
- package/dist/__tests__/new-project-first-team.test.js +263 -0
- package/dist/__tests__/new-project-first-team.test.js.map +1 -0
- package/dist/__tests__/otel-env.test.d.ts +2 -0
- package/dist/__tests__/otel-env.test.d.ts.map +1 -0
- package/dist/__tests__/otel-env.test.js +127 -0
- package/dist/__tests__/otel-env.test.js.map +1 -0
- package/dist/__tests__/project-config.test.js +283 -1
- package/dist/__tests__/project-config.test.js.map +1 -1
- package/dist/__tests__/provision-behavioral-contract.test.js +96 -4
- package/dist/__tests__/provision-behavioral-contract.test.js.map +1 -1
- package/dist/__tests__/provision-catalog-precondition.test.d.ts +26 -0
- package/dist/__tests__/provision-catalog-precondition.test.d.ts.map +1 -0
- package/dist/__tests__/provision-catalog-precondition.test.js +620 -0
- package/dist/__tests__/provision-catalog-precondition.test.js.map +1 -0
- package/dist/__tests__/provision-completion-rows.test.d.ts +17 -0
- package/dist/__tests__/provision-completion-rows.test.d.ts.map +1 -0
- package/dist/__tests__/provision-completion-rows.test.js +3095 -0
- package/dist/__tests__/provision-completion-rows.test.js.map +1 -0
- package/dist/__tests__/provision-identity-gate.test.d.ts +20 -0
- package/dist/__tests__/provision-identity-gate.test.d.ts.map +1 -0
- package/dist/__tests__/provision-identity-gate.test.js +600 -0
- package/dist/__tests__/provision-identity-gate.test.js.map +1 -0
- package/dist/__tests__/provision-resume.test.d.ts +26 -0
- package/dist/__tests__/provision-resume.test.d.ts.map +1 -0
- package/dist/__tests__/provision-resume.test.js +1164 -0
- package/dist/__tests__/provision-resume.test.js.map +1 -0
- package/dist/__tests__/provision-roleguide-anchors.test.d.ts +27 -0
- package/dist/__tests__/provision-roleguide-anchors.test.d.ts.map +1 -0
- package/dist/__tests__/provision-roleguide-anchors.test.js +747 -0
- package/dist/__tests__/provision-roleguide-anchors.test.js.map +1 -0
- package/dist/__tests__/provision-skeleton-fill.test.d.ts +16 -0
- package/dist/__tests__/provision-skeleton-fill.test.d.ts.map +1 -0
- package/dist/__tests__/provision-skeleton-fill.test.js +488 -0
- package/dist/__tests__/provision-skeleton-fill.test.js.map +1 -0
- package/dist/__tests__/provision-teambuilder-flow.test.js +93 -7
- package/dist/__tests__/provision-teambuilder-flow.test.js.map +1 -1
- package/dist/__tests__/repo-guard-wiring.test.d.ts +21 -0
- package/dist/__tests__/repo-guard-wiring.test.d.ts.map +1 -0
- package/dist/__tests__/repo-guard-wiring.test.js +638 -0
- package/dist/__tests__/repo-guard-wiring.test.js.map +1 -0
- package/dist/__tests__/runtime-codex-gateway-pilot.test.d.ts +2 -0
- package/dist/__tests__/runtime-codex-gateway-pilot.test.d.ts.map +1 -0
- package/dist/__tests__/runtime-codex-gateway-pilot.test.js +309 -0
- package/dist/__tests__/runtime-codex-gateway-pilot.test.js.map +1 -0
- package/dist/__tests__/runtime-codex-gateway-provider.test.d.ts +2 -0
- package/dist/__tests__/runtime-codex-gateway-provider.test.d.ts.map +1 -0
- package/dist/__tests__/runtime-codex-gateway-provider.test.js +163 -0
- package/dist/__tests__/runtime-codex-gateway-provider.test.js.map +1 -0
- package/dist/__tests__/runtime-identity.test.d.ts +2 -0
- package/dist/__tests__/runtime-identity.test.d.ts.map +1 -0
- package/dist/__tests__/runtime-identity.test.js +117 -0
- package/dist/__tests__/runtime-identity.test.js.map +1 -0
- package/dist/__tests__/session-pause-provisioning.test.js +6 -1
- package/dist/__tests__/session-pause-provisioning.test.js.map +1 -1
- package/dist/__tests__/session-record-disclosure.test.d.ts +24 -0
- package/dist/__tests__/session-record-disclosure.test.d.ts.map +1 -0
- package/dist/__tests__/session-record-disclosure.test.js +494 -0
- package/dist/__tests__/session-record-disclosure.test.js.map +1 -0
- package/dist/__tests__/session.test.js +35 -0
- package/dist/__tests__/session.test.js.map +1 -1
- package/dist/__tests__/slug-validation.test.js +27 -21
- package/dist/__tests__/slug-validation.test.js.map +1 -1
- package/dist/__tests__/standards-injection.test.js +23 -1
- package/dist/__tests__/standards-injection.test.js.map +1 -1
- package/dist/__tests__/start-interactive-role.test.d.ts +22 -0
- package/dist/__tests__/start-interactive-role.test.d.ts.map +1 -0
- package/dist/__tests__/start-interactive-role.test.js +204 -0
- package/dist/__tests__/start-interactive-role.test.js.map +1 -0
- package/dist/__tests__/start-team-identity.test.d.ts +25 -0
- package/dist/__tests__/start-team-identity.test.d.ts.map +1 -0
- package/dist/__tests__/start-team-identity.test.js +307 -0
- package/dist/__tests__/start-team-identity.test.js.map +1 -0
- package/dist/__tests__/team-memory-commands.test.js +142 -19
- package/dist/__tests__/team-memory-commands.test.js.map +1 -1
- package/dist/__tests__/template-sync.test.d.ts +19 -0
- package/dist/__tests__/template-sync.test.d.ts.map +1 -0
- package/dist/__tests__/template-sync.test.js +270 -0
- package/dist/__tests__/template-sync.test.js.map +1 -0
- package/dist/__tests__/test-project.test.d.ts +18 -0
- package/dist/__tests__/test-project.test.d.ts.map +1 -0
- package/dist/__tests__/test-project.test.js +465 -0
- package/dist/__tests__/test-project.test.js.map +1 -0
- package/dist/__tests__/usage-per-call-grouping.test.d.ts +25 -0
- package/dist/__tests__/usage-per-call-grouping.test.d.ts.map +1 -0
- package/dist/__tests__/usage-per-call-grouping.test.js +952 -0
- package/dist/__tests__/usage-per-call-grouping.test.js.map +1 -0
- package/dist/__tests__/verify-hooks-check-all.test.d.ts +32 -0
- package/dist/__tests__/verify-hooks-check-all.test.d.ts.map +1 -0
- package/dist/__tests__/verify-hooks-check-all.test.js +553 -0
- package/dist/__tests__/verify-hooks-check-all.test.js.map +1 -0
- package/dist/__tests__/worktree-sync-fixture.test.d.ts +17 -0
- package/dist/__tests__/worktree-sync-fixture.test.d.ts.map +1 -0
- package/dist/__tests__/worktree-sync-fixture.test.js +519 -0
- package/dist/__tests__/worktree-sync-fixture.test.js.map +1 -0
- package/dist/__tests__/worktree-sync-hardening.test.d.ts +13 -0
- package/dist/__tests__/worktree-sync-hardening.test.d.ts.map +1 -0
- package/dist/__tests__/worktree-sync-hardening.test.js +919 -0
- package/dist/__tests__/worktree-sync-hardening.test.js.map +1 -0
- package/dist/__tests__/worktree-sync-shell-free.test.d.ts +25 -0
- package/dist/__tests__/worktree-sync-shell-free.test.d.ts.map +1 -0
- package/dist/__tests__/worktree-sync-shell-free.test.js +185 -0
- package/dist/__tests__/worktree-sync-shell-free.test.js.map +1 -0
- package/dist/__tests__/worktree.test.js +75 -1
- package/dist/__tests__/worktree.test.js.map +1 -1
- package/dist/agent-config/.mx-config-generation.json +2 -2
- package/dist/agent-config/AGENTS.md.template +2 -2
- package/dist/agent-config/agents/bar-raiser.md +34 -1
- package/dist/agent-config/agents/red-team.md +34 -1
- package/dist/agent-config/agents/security-reviewer.md +22 -1
- package/dist/agent-config/claude-md/CLAUDE.core.md +6 -1
- package/dist/agent-config/claude-md/CLAUDE.overlay.memnexus.md +1 -3
- package/dist/agent-config/coordination-rosters.generated.json +10 -0
- package/dist/agent-config/hooks/HOOK-TIMEOUTS.md +27 -1
- package/dist/agent-config/hooks/OR-TRUE-AUDIT.md +8 -8
- package/dist/agent-config/hooks/auto-capture-precompact.sh +279 -0
- package/dist/agent-config/hooks/auto-capture-session-end.sh +277 -0
- package/dist/agent-config/hooks/coordination-brief.sh +290 -245
- package/dist/agent-config/hooks/deploy-verification-reminder.sh +359 -22
- package/dist/agent-config/hooks/git-mutation-guard.sh +85 -13
- package/dist/agent-config/hooks/session-idle-gate.sh +177 -12
- package/dist/agent-config/hooks/subagent-write-guard.sh +670 -0
- package/dist/agent-config/hooks/worktree-guard.sh +36 -7
- package/dist/agent-config/settings.json +15 -2
- package/dist/agent-config/shared/creation-pr-review-checklist.md +317 -0
- package/dist/commands/bootstrap.d.ts.map +1 -1
- package/dist/commands/bootstrap.js +22 -10
- package/dist/commands/bootstrap.js.map +1 -1
- package/dist/commands/config.d.ts.map +1 -1
- package/dist/commands/config.js +28 -1
- package/dist/commands/config.js.map +1 -1
- package/dist/commands/coordination.d.ts +150 -8
- package/dist/commands/coordination.d.ts.map +1 -1
- package/dist/commands/coordination.js +519 -25
- package/dist/commands/coordination.js.map +1 -1
- package/dist/commands/create.d.ts +913 -1
- package/dist/commands/create.d.ts.map +1 -1
- package/dist/commands/create.js +4879 -345
- package/dist/commands/create.js.map +1 -1
- package/dist/commands/digest.d.ts.map +1 -1
- package/dist/commands/digest.js +91 -7
- package/dist/commands/digest.js.map +1 -1
- package/dist/commands/fleet-tmux.js +1 -1
- package/dist/commands/fleet-tmux.js.map +1 -1
- package/dist/commands/init.d.ts +8 -0
- package/dist/commands/init.d.ts.map +1 -1
- package/dist/commands/init.js +26 -1
- package/dist/commands/init.js.map +1 -1
- package/dist/commands/list.d.ts +32 -1
- package/dist/commands/list.d.ts.map +1 -1
- package/dist/commands/list.js +98 -5
- package/dist/commands/list.js.map +1 -1
- package/dist/commands/new.d.ts +2 -0
- package/dist/commands/new.d.ts.map +1 -1
- package/dist/commands/new.js +114 -21
- package/dist/commands/new.js.map +1 -1
- package/dist/commands/session.js +1 -1
- package/dist/commands/session.js.map +1 -1
- package/dist/commands/start.d.ts +38 -0
- package/dist/commands/start.d.ts.map +1 -1
- package/dist/commands/start.js +171 -8
- package/dist/commands/start.js.map +1 -1
- package/dist/commands/sync.d.ts +57 -0
- package/dist/commands/sync.d.ts.map +1 -1
- package/dist/commands/sync.js +117 -3
- package/dist/commands/sync.js.map +1 -1
- package/dist/commands/usage.d.ts +64 -0
- package/dist/commands/usage.d.ts.map +1 -1
- package/dist/commands/usage.js +96 -3
- package/dist/commands/usage.js.map +1 -1
- package/dist/commands/verify-hooks.d.ts +37 -1
- package/dist/commands/verify-hooks.d.ts.map +1 -1
- package/dist/commands/verify-hooks.js +114 -2
- package/dist/commands/verify-hooks.js.map +1 -1
- package/dist/commands/window.d.ts +10 -0
- package/dist/commands/window.d.ts.map +1 -0
- package/dist/commands/window.js +265 -0
- package/dist/commands/window.js.map +1 -0
- package/dist/commands/worktree-sync.d.ts +54 -0
- package/dist/commands/worktree-sync.d.ts.map +1 -0
- package/dist/commands/worktree-sync.js +135 -0
- package/dist/commands/worktree-sync.js.map +1 -0
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +122 -11
- package/dist/index.js.map +1 -1
- package/dist/lib/agent-session.d.ts.map +1 -1
- package/dist/lib/agent-session.js +6 -1
- package/dist/lib/agent-session.js.map +1 -1
- package/dist/lib/catalog.d.ts +321 -2
- package/dist/lib/catalog.d.ts.map +1 -1
- package/dist/lib/catalog.js +490 -11
- package/dist/lib/catalog.js.map +1 -1
- package/dist/lib/claude.d.ts +53 -23
- package/dist/lib/claude.d.ts.map +1 -1
- package/dist/lib/claude.js +306 -17
- package/dist/lib/claude.js.map +1 -1
- package/dist/lib/cli-build.d.ts +172 -0
- package/dist/lib/cli-build.d.ts.map +1 -0
- package/dist/lib/cli-build.js +654 -0
- package/dist/lib/cli-build.js.map +1 -0
- package/dist/lib/code-context-file.d.ts +109 -0
- package/dist/lib/code-context-file.d.ts.map +1 -0
- package/dist/lib/code-context-file.js +219 -0
- package/dist/lib/code-context-file.js.map +1 -0
- package/dist/lib/code-context-file.test.d.ts +19 -0
- package/dist/lib/code-context-file.test.d.ts.map +1 -0
- package/dist/lib/code-context-file.test.js +202 -0
- package/dist/lib/code-context-file.test.js.map +1 -0
- package/dist/lib/config-fidelity.d.ts +40 -20
- package/dist/lib/config-fidelity.d.ts.map +1 -1
- package/dist/lib/config-fidelity.js +144 -56
- package/dist/lib/config-fidelity.js.map +1 -1
- package/dist/lib/coordination-client.d.ts +73 -0
- package/dist/lib/coordination-client.d.ts.map +1 -1
- package/dist/lib/coordination-client.js +180 -8
- package/dist/lib/coordination-client.js.map +1 -1
- package/dist/lib/coordination-token.d.ts +304 -6
- package/dist/lib/coordination-token.d.ts.map +1 -1
- package/dist/lib/coordination-token.js +851 -52
- package/dist/lib/coordination-token.js.map +1 -1
- package/dist/lib/fleet-data.d.ts +34 -0
- package/dist/lib/fleet-data.d.ts.map +1 -1
- package/dist/lib/fleet-data.js +37 -9
- package/dist/lib/fleet-data.js.map +1 -1
- package/dist/lib/fleet-render.js +1 -1
- package/dist/lib/fleet-render.js.map +1 -1
- package/dist/lib/git-identity.d.ts +302 -0
- package/dist/lib/git-identity.d.ts.map +1 -0
- package/dist/lib/git-identity.js +546 -0
- package/dist/lib/git-identity.js.map +1 -0
- package/dist/lib/hook-staleness.d.ts +95 -0
- package/dist/lib/hook-staleness.d.ts.map +1 -0
- package/dist/lib/hook-staleness.js +304 -0
- package/dist/lib/hook-staleness.js.map +1 -0
- package/dist/lib/jsonl.d.ts +270 -2
- package/dist/lib/jsonl.d.ts.map +1 -1
- package/dist/lib/jsonl.js +472 -76
- package/dist/lib/jsonl.js.map +1 -1
- package/dist/lib/memory.d.ts +350 -23
- package/dist/lib/memory.d.ts.map +1 -1
- package/dist/lib/memory.js +751 -38
- package/dist/lib/memory.js.map +1 -1
- package/dist/lib/otel-env.d.ts +90 -0
- package/dist/lib/otel-env.d.ts.map +1 -0
- package/dist/lib/otel-env.js +98 -0
- package/dist/lib/otel-env.js.map +1 -0
- package/dist/lib/project-config.d.ts +167 -0
- package/dist/lib/project-config.d.ts.map +1 -1
- package/dist/lib/project-config.js +321 -5
- package/dist/lib/project-config.js.map +1 -1
- package/dist/lib/projects-registry.d.ts +82 -0
- package/dist/lib/projects-registry.d.ts.map +1 -0
- package/dist/lib/projects-registry.js +145 -0
- package/dist/lib/projects-registry.js.map +1 -0
- package/dist/lib/projects-registry.test.d.ts +2 -0
- package/dist/lib/projects-registry.test.d.ts.map +1 -0
- package/dist/lib/projects-registry.test.js +176 -0
- package/dist/lib/projects-registry.test.js.map +1 -0
- package/dist/lib/repo-guard-scope.d.ts +126 -0
- package/dist/lib/repo-guard-scope.d.ts.map +1 -0
- package/dist/lib/repo-guard-scope.js +249 -0
- package/dist/lib/repo-guard-scope.js.map +1 -0
- package/dist/lib/roster.d.ts +87 -0
- package/dist/lib/roster.d.ts.map +1 -0
- package/dist/lib/roster.js +332 -0
- package/dist/lib/roster.js.map +1 -0
- package/dist/lib/roster.test.d.ts +15 -0
- package/dist/lib/roster.test.d.ts.map +1 -0
- package/dist/lib/roster.test.js +299 -0
- package/dist/lib/roster.test.js.map +1 -0
- package/dist/lib/runtime/codex-adapter.d.ts.map +1 -1
- package/dist/lib/runtime/codex-adapter.js +5 -0
- package/dist/lib/runtime/codex-adapter.js.map +1 -1
- package/dist/lib/runtime/codex-config.d.ts +129 -0
- package/dist/lib/runtime/codex-config.d.ts.map +1 -1
- package/dist/lib/runtime/codex-config.js +225 -0
- package/dist/lib/runtime/codex-config.js.map +1 -1
- package/dist/lib/runtime/identity.d.ts +72 -0
- package/dist/lib/runtime/identity.d.ts.map +1 -0
- package/dist/lib/runtime/identity.js +128 -0
- package/dist/lib/runtime/identity.js.map +1 -0
- package/dist/lib/standards.d.ts +10 -1
- package/dist/lib/standards.d.ts.map +1 -1
- package/dist/lib/standards.js +8 -1
- package/dist/lib/standards.js.map +1 -1
- package/dist/lib/team-identity.d.ts +134 -0
- package/dist/lib/team-identity.d.ts.map +1 -0
- package/dist/lib/team-identity.js +193 -0
- package/dist/lib/team-identity.js.map +1 -0
- package/dist/lib/templates.d.ts +29 -2
- package/dist/lib/templates.d.ts.map +1 -1
- package/dist/lib/templates.js +1042 -82
- package/dist/lib/templates.js.map +1 -1
- package/dist/lib/test-project.d.ts +95 -0
- package/dist/lib/test-project.d.ts.map +1 -0
- package/dist/lib/test-project.js +103 -0
- package/dist/lib/test-project.js.map +1 -0
- package/dist/lib/vault.d.ts +60 -0
- package/dist/lib/vault.d.ts.map +1 -0
- package/dist/lib/vault.js +102 -0
- package/dist/lib/vault.js.map +1 -0
- package/dist/lib/vault.test.d.ts +17 -0
- package/dist/lib/vault.test.d.ts.map +1 -0
- package/dist/lib/vault.test.js +169 -0
- package/dist/lib/vault.test.js.map +1 -0
- package/dist/lib/window-view.d.ts +63 -0
- package/dist/lib/window-view.d.ts.map +1 -0
- package/dist/lib/window-view.js +217 -0
- package/dist/lib/window-view.js.map +1 -0
- package/dist/lib/window-view.test.d.ts +2 -0
- package/dist/lib/window-view.test.d.ts.map +1 -0
- package/dist/lib/window-view.test.js +168 -0
- package/dist/lib/window-view.test.js.map +1 -0
- package/dist/lib/worktree-sync.d.ts +439 -0
- package/dist/lib/worktree-sync.d.ts.map +1 -0
- package/dist/lib/worktree-sync.js +1167 -0
- package/dist/lib/worktree-sync.js.map +1 -0
- package/dist/lib/worktree.d.ts +58 -1
- package/dist/lib/worktree.d.ts.map +1 -1
- package/dist/lib/worktree.js +91 -4
- package/dist/lib/worktree.js.map +1 -1
- package/dist/standards/decision-request.md +8 -0
- package/dist/standards/po-communication-standard.md +126 -0
- package/dist/standards/report-format.md +8 -0
- package/dist/standards/writing-standard.md +146 -4
- package/package.json +1 -1
- package/scripts/generate-claude.mjs +119 -46
|
@@ -93,7 +93,7 @@ SHA, the three-step job-log procedure for proving which base a CI run checked ou
|
|
|
93
93
|
empty grep result is the *default* rather than a pass, and the withdrawn
|
|
94
94
|
`merge_commit_sha` check (#4942).
|
|
95
95
|
|
|
96
|
-
|
|
96
|
+
The two rules below, through the stale merge ref bullet, are load-bearing enough to state here as well as there:
|
|
97
97
|
|
|
98
98
|
- **Stale API view (#5086).** After any force-push, amend, or rebase: `git fetch origin
|
|
99
99
|
<branch>` and diff the ref locally. Never review from `gh pr view` / `gh pr diff` alone —
|
|
@@ -113,6 +113,27 @@ These two rules are load-bearing enough to state here as well as there:
|
|
|
113
113
|
`merge_commit_sha` polling check was disproved on #4942 — do not use it; details in the
|
|
114
114
|
shared file.
|
|
115
115
|
|
|
116
|
+
- **Scope. Test for the wrapper before you decide the Codex review is owed.** This file
|
|
117
|
+
ships to more than one repository, so establish which one you are in first:
|
|
118
|
+
|
|
119
|
+
```bash
|
|
120
|
+
git remote get-url origin # which repository is under review
|
|
121
|
+
ls dev-tools/scripts/codex-review.sh # the wrapper: present or absent
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
**If the wrapper is absent, the Codex differential review is not part of your verdict.
|
|
125
|
+
Do not run it, and do not record it as owed or as skipped.** Absent means absent from
|
|
126
|
+
the repository under review, not missing from your worktree, so confirm against
|
|
127
|
+
`origin/main` rather than an uncommitted state.
|
|
128
|
+
|
|
129
|
+
`mx-agent-framework` is the worked instance. `dev-tools/scripts/codex-review.sh` does
|
|
130
|
+
not exist there and never has: `git log --all --diff-filter=D -- '*codex-review.sh'`
|
|
131
|
+
returns nothing, and `git ls-tree -r origin/main --name-only -- dev-tools/` returns only
|
|
132
|
+
two files under `dev-tools/wsl/`. The product owner scoped the requirement out of that
|
|
133
|
+
repository on 2026-09-01, and the `/codex` skill was removed from its agent-config the
|
|
134
|
+
same day. Issue #222 records that it was could-not-run on every pull request that
|
|
135
|
+
repository shipped. The bullets below, through the `--exclude` bullet, apply when you
|
|
136
|
+
review in a repository that ships the wrapper.
|
|
116
137
|
- The Codex differential review is a locally-run script, not a CI job, so "a comment
|
|
117
138
|
exists" is not evidence it ran clean. Check the **exit status**, and record the SHA
|
|
118
139
|
yourself:
|
|
@@ -92,11 +92,16 @@ Sync URL is pre-configured in the StopHook.
|
|
|
92
92
|
A PR is not done when it merges. It is done when it deploys and the deploy is verified.
|
|
93
93
|
|
|
94
94
|
1. Sync branch with main. Run `/mx-post-merge-sync`. If unavailable: `git fetch origin main && git rebase origin/main`. Verify: `git rev-list --count HEAD..origin/main` returns 0.
|
|
95
|
-
2. Verify deployment succeeded. Get the merge SHA (`gh pr view <N> --json mergeCommit`), poll the pipeline (`gh run list --commit <sha>`), confirm the artifact is live (npm publish for CLI; deploy workflow `success` for services).
|
|
95
|
+
2. Verify deployment succeeded. Get the merge SHA (`gh pr view <N> --json mergeCommit`), poll the pipeline (`gh run list --commit <sha>`), confirm the artifact is live (npm publish for CLI; deploy workflow `success` for services). If a merge's own CI run was cancelled by a later push to the same ref, the gate is satisfied by a green run at any descendant commit, verified with `git merge-base --is-ancestor <cancelled-sha> <later-sha>`. A cancelled run with no green descendant run is not verified. Both workflows set `concurrency` with `cancel-in-progress: true` keyed on the ref (`.github/workflows/mx-agent-cli.yml:113-115`, `.github/workflows/coordination-service.yml:83-85`), so a cancelled run is an ordinary result of two merges close together, not a failure.
|
|
96
96
|
3. Save a checkpoint memory. Include PR number, what shipped, deploy status, next step.
|
|
97
97
|
|
|
98
98
|
If the pipeline is still running, wait. If it failed, fix it. Do not start the next iteration with an unverified deploy.
|
|
99
99
|
|
|
100
|
+
<!-- core:read-back -->
|
|
101
|
+
## Tools that fail silently — read back what you wrote
|
|
102
|
+
|
|
103
|
+
`gh` is pinned to 2.97.0 in `.devcontainer/Dockerfile`; older `gh` (Debian's 2.46.0, still present in any devcontainer not rebuilt since) fails on several commands and one of them fails **silently** — affected-command table and substitutes in `mx-agent-system/docs/gh-cli-version-pin.md`. An exit-0 or "created"/"sent" confirmation says the call succeeded, not that the stored content is what you wrote: after any write of a PR body, a comment, or memory content, read it back and compare. Check the read-back is non-empty before you trust its diff: `gh pr view --json body` run from a directory that is not a git repository fails and writes zero bytes, and a diff against an empty file reads as the whole body deleted, which looks like catastrophic drift and is not (found by the #189 engineer, 2026-08-25).
|
|
104
|
+
|
|
100
105
|
<!-- core:continuous-operation -->
|
|
101
106
|
## Continuous operation
|
|
102
107
|
|
|
@@ -73,9 +73,7 @@ mx-agent escalate --to '<team>' --priority '<p0|p1|p2|p3>' --body-file '<path-to
|
|
|
73
73
|
|
|
74
74
|
Check other teams via `{{PRODUCT_SLUG}}-<team>-leader-state` and `{{PRODUCT_SLUG}}-<team>-known-issues` named memories.
|
|
75
75
|
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
`gh` is pinned to 2.97.0 in `.devcontainer/Dockerfile`; older `gh` (Debian's 2.46.0, still present in any devcontainer not rebuilt since) fails on several commands and one of them fails **silently** — affected-command table and substitutes in `mx-agent-system/docs/gh-cli-version-pin.md`. An exit-0 or "created"/"sent" confirmation says the call succeeded, not that the stored content is what you wrote: after any write of a PR body, a comment, or memory content, read it back and compare.
|
|
76
|
+
{{> core:read-back}}
|
|
79
77
|
|
|
80
78
|
## Instructions that arrive mid-task — the leader channel
|
|
81
79
|
|
|
@@ -29,7 +29,7 @@ lost?**
|
|
|
29
29
|
|
|
30
30
|
| Tier | A fail-open kill means | Size against | Examples |
|
|
31
31
|
|---|---|---|---|
|
|
32
|
-
| **GUARD** | An action the hook exists to prevent is **permitted**. The kill is a bypass primitive: anything that makes the hook slow becomes a way past it. | **Bypass risk.** Be generous — generous enough that only a genuine hang trips it — and bound the hook's own slow calls internally so the hook decides first, on its own fail direction. | `worktree-guard`, `git-mutation-guard`, `mx-guard-hook`, `ci-validate-hook`, `workflow-dispatch-guard`, `named-memory-write-guard`, `gh-pr-edit-guard`, `session-idle-gate` |
|
|
32
|
+
| **GUARD** | An action the hook exists to prevent is **permitted**. The kill is a bypass primitive: anything that makes the hook slow becomes a way past it. | **Bypass risk.** Be generous — generous enough that only a genuine hang trips it — and bound the hook's own slow calls internally so the hook decides first, on its own fail direction. | `worktree-guard`, `git-mutation-guard`, `mx-guard-hook`, `ci-validate-hook`, `workflow-dispatch-guard`, `named-memory-write-guard`, `gh-pr-edit-guard`, `subagent-write-guard`, `session-idle-gate` |
|
|
33
33
|
| **ENFORCED-PROCESS CONTROL** | A **required step is skipped**. No security boundary is crossed, but process discipline the team relies on quietly stops applying. | **False-trip probability.** The risk is not a bypass, it is that a normal slow moment drops the enforcement. Size so ordinary slowness never trips it. | `memory-checkpoint-reminder`, `deploy-verification-reminder` |
|
|
34
34
|
| **ADVISORY** | **Information is lost** and nothing else. No action is permitted, no step is skipped. | Keep it short. A lost reminder or a lost telemetry line is cheap; holding a tool call open is not. | `delegation-audit`, `set-terminal-appearance`, `auto-capture-*`, `auto-checkpoint`, `observability-sync`, `iteration-log-check` |
|
|
35
35
|
|
|
@@ -139,8 +139,34 @@ including the 5s on `set-terminal-appearance`. It never runs on the normal path.
|
|
|
139
139
|
| `reload-checkpoint` | SessionStart | ADVISORY | 20s |
|
|
140
140
|
| `iteration-log-check` | Stop | ADVISORY | 20s |
|
|
141
141
|
| `delegation-audit` | Stop | ADVISORY | 15s |
|
|
142
|
+
| `verify-hooks --check-all` | SessionStart | ADVISORY | 15s |
|
|
142
143
|
| `set-terminal-appearance` | SessionStart | ADVISORY | 5s |
|
|
143
144
|
|
|
145
|
+
`verify-hooks --check-all` is the one row that is not a hook file. It is a CLI
|
|
146
|
+
command the registration runs directly, because a present-but-stale hook file
|
|
147
|
+
never reaches `hook-launcher.sh` and the check must not be a file that can
|
|
148
|
+
itself go stale (#306). Two limits, not one: the inner `timeout 10` is the
|
|
149
|
+
budget the command is measured against (300 ms in criterion 1(d), so 10s is 33x
|
|
150
|
+
headroom), and the outer `timeout: 15` is the fail-open kill. A kill loses one
|
|
151
|
+
staleness report and permits nothing, which is the ADVISORY tier.
|
|
152
|
+
|
|
153
|
+
THE REGISTRATION EXITS 0 ON EVERY PATH, and that is the one place this row
|
|
154
|
+
departs from the exit-code rule two sections above. The rule there governs a
|
|
155
|
+
hook whose message is on STDERR: it exits 1 so the transcript shows the first
|
|
156
|
+
stderr line. This check's whole output is on STDOUT, and a non-zero exit
|
|
157
|
+
suppresses a hook's stdout, so the same exit that makes a stderr message visible
|
|
158
|
+
would make this one disappear. Measured at 583ebf9 (PR #309): with `mx-agent`
|
|
159
|
+
absent the bare command exited 127 with nothing on stdout, and with the
|
|
160
|
+
installed 0.1.72 build it wrote `error: unknown option '--check-all'` to stderr
|
|
161
|
+
and exited 1. Both are states the check exists to report, and in both the
|
|
162
|
+
session saw nothing. The registration is therefore a `bash -c` guard that tests
|
|
163
|
+
for `mx-agent` on PATH, probes `verify-hooks --help` for the option, runs the
|
|
164
|
+
check, and turns every outcome including its own failure to run into exit 0 with
|
|
165
|
+
one line on stdout. The CLI keeps its own codes for anyone calling it directly:
|
|
166
|
+
0 fresh, 2 could-not-compare, 3 stale. Behaviour of the guard string is asserted
|
|
167
|
+
in `session-start-freshness.test.sh`; its exact text is pinned in
|
|
168
|
+
`cli/src/__tests__/config-generation-gate.test.ts`.
|
|
169
|
+
|
|
144
170
|
The two coordination hooks are advisory by tier — being killed loses information
|
|
145
171
|
rather than permitting an action — but the information is cross-team escalation
|
|
146
172
|
delivery, so they are sized and instrumented as if the loss were expensive,
|
|
@@ -29,13 +29,9 @@ Audit of every `|| true` pattern in hook scripts, classifying each by failure im
|
|
|
29
29
|
| `iteration-log-check.sh` | 88 | B | `grep ... \|\| true` | Counting merge commands in transcript; 0 on failure is safe. |
|
|
30
30
|
| `iteration-log-check.sh` | 112, 115 | B | `git rev-parse / jq ... 2>/dev/null \|\| true` | Resolving project slug; empty = use default log name. |
|
|
31
31
|
| `iteration-log-check.sh` | 167 | B | `mx memories get ... 2>/dev/null \|\| true` | Reading iteration log; failure = skip log check (advisory). |
|
|
32
|
-
| `coordination-brief.sh` |
|
|
33
|
-
| `coordination-brief.sh` |
|
|
34
|
-
| `coordination-brief.sh` |
|
|
35
|
-
| `coordination-brief.sh` | 164, 172 | **A** | `az keyvault ... 2>/dev/null \|\| true` | **Token fetch from Azure Key Vault.** Failure means no coordination token; brief will fail silently. Mitigated: the brief itself reports "no token" and the coordination-brief.sh logs to stderr. |
|
|
36
|
-
| `coordination-brief.sh` | 179 | B | `printf ... > "$CACHE" 2>/dev/null \|\| true` | Caching fetched token; loss = re-fetch next time. |
|
|
37
|
-
| `coordination-brief.sh` | 202 | B | `mktemp ... 2>/dev/null \|\| true` | Creating temp file for stderr capture; failure = no stderr capture. |
|
|
38
|
-
| `coordination-brief.sh` | 235 | B | `rm -f ... 2>/dev/null \|\| true` | Cleaning up temp file; standard cleanup. |
|
|
32
|
+
| `coordination-brief.sh` | 150, 151 | B | `mktemp ... 2>/dev/null \|\| true` | Creating the stdout and stderr capture files; failure prints the `no-capture` could-not-run line and the brief then runs unclassified. |
|
|
33
|
+
| `coordination-brief.sh` | 156, 157, 164 | B | `rm -f ... 2>/dev/null \|\| true` | Cleaning up the capture files; standard cleanup. |
|
|
34
|
+
| `coordination-brief.sh` | 161 | B | `mx-agent coordination brief ... \|\| true` | The unclassifiable branch only (mktemp failed). The could-not-run line is printed BEFORE this call, so the branch is never silent. |
|
|
39
35
|
| `deploy-verification-reminder.sh` | 21 | B | `touch ... 2>/dev/null \|\| true` | Touching lock file; failure = cosmetic. |
|
|
40
36
|
| `deploy-verification-reminder.sh` | 64 | B | `>/dev/null 2>&1 \|\| true` | Advisory memory save; non-blocking. |
|
|
41
37
|
| `deploy-verification-reminder.sh` | 74 | B | `touch ... 2>/dev/null \|\| true` | Marking verify-sent; loss = duplicate reminder (harmless). |
|
|
@@ -63,7 +59,11 @@ Audit of every `|| true` pattern in hook scripts, classifying each by failure im
|
|
|
63
59
|
|
|
64
60
|
## Summary
|
|
65
61
|
|
|
66
|
-
- **Class A occurrences:
|
|
62
|
+
- **Class A occurrences: 0.**
|
|
63
|
+
|
|
64
|
+
This entry read "Class A occurrences: 2 (coordination-brief.sh lines 164, 172 — Azure Key Vault token fetch). These already have downstream visibility: the brief command itself reports 'no token' to stderr when the fetch fails." Both halves were wrong by #297. The claim was wrong when written: the branch guarded by those two `|| true` calls was `if [ -z "$fetched" ]; then exit 0; fi`, which printed nothing on any stream, so there was no downstream visibility to rely on. That silence is the defect #291 recorded and #297 fixes. The `az` calls themselves are gone: the hook no longer resolves a token, and the CLI owns the fetch and reports its own failure (`resolveCoordinationToken`, `lib/coordination-token.ts`).
|
|
65
|
+
|
|
66
|
+
Nothing in this file is Class A now, and no `|| true` in `coordination-brief.sh` can produce a silent exit: with the opt-in gate on, every path prints either the brief or one could-not-run line to stdout, pinned by `coordination-brief.test.sh`.
|
|
67
67
|
- **Class B occurrences: all others.** Silent failure is the correct behavior for cosmetic, cleanup, advisory, and parsing-guard patterns.
|
|
68
68
|
|
|
69
69
|
The observability-sync `|| true` that previously lived inline in `settings.json` (line 99) was **Class A** and has been replaced by `observability-sync.sh`, which logs failures to the startup JSONL before exiting 0 (v2.59, #4377).
|
|
@@ -298,6 +298,284 @@ mx_verbatim_guard() {
|
|
|
298
298
|
return 0
|
|
299
299
|
}
|
|
300
300
|
|
|
301
|
+
# ── 5b. Resolve project scope (codeContext) ──────────────────────────────
|
|
302
|
+
#
|
|
303
|
+
# BACKPORT. The block below is the "Resolve project scope" block of
|
|
304
|
+
# @memnexus-ai/cli@1.7.235, hooks/capture-precompact.sh lines 204 to 459, copied byte
|
|
305
|
+
# for byte apart from the three points this note names. Product owner ruling,
|
|
306
|
+
# 2026-08-22 (AskUserQuestion): "Approve both halves in v5" (plan #67, fixes #62).
|
|
307
|
+
#
|
|
308
|
+
# WHERE THIS FORK DIFFERS FROM UPSTREAM:
|
|
309
|
+
# 1. Section number. Upstream numbers the block 6b. This file's guard is
|
|
310
|
+
# section 5 and its save is section 6, so the block is 5b here. Its
|
|
311
|
+
# position is the same: after the content is built, before the create call.
|
|
312
|
+
# 2. The trap paragraph below names section 2, which is where THIS file arms
|
|
313
|
+
# `trap 'rm -rf "$tmpdir"; exit 0' EXIT ERR`.
|
|
314
|
+
# Upstream names its own section 4.
|
|
315
|
+
# 3. The create call keeps this fork's `timeout "${AUTO_CAPTURE_TIMEOUT_SECS:-20}"` and
|
|
316
|
+
# `|| true`, not upstream's TIMEOUT_CMD and CREATE_STATUS reporting. The one
|
|
317
|
+
# addition is the --code-context argument.
|
|
318
|
+
#
|
|
319
|
+
# auto-checkpoint.sh gets none of this. It writes a NAMED memory, and scope must
|
|
320
|
+
# not reach that path until memnexus#5470 is resolved (#62).
|
|
321
|
+
#
|
|
322
|
+
# ── upstream block, verbatim from here ──
|
|
323
|
+
# Auto-captured memories carried no scope at all, so they leaked into every
|
|
324
|
+
# team's scoped searches and polluted build_context (#5158, #4957). PR #3281
|
|
325
|
+
# fixed that for the commit path only; this is the same resolution for the
|
|
326
|
+
# capture hooks, using the same sources and the same precedence.
|
|
327
|
+
#
|
|
328
|
+
# Mirrors resolveCommitCodeContext() in cli/src/lib/commit-context/code-context.ts:
|
|
329
|
+
# 1. MX_CODE_CONTEXT env var — operator-controlled, higher trust. It wins over
|
|
330
|
+
# the file (CWE-345): a checked-in file from an untrusted clone must not
|
|
331
|
+
# override the scope the operator set explicitly.
|
|
332
|
+
# 2. <projectRoot>/.mx-code-context.json — repo-controlled, lower trust.
|
|
333
|
+
# 3. Neither present or neither usable -> NO scope. The memory is created
|
|
334
|
+
# unlabeled, exactly as it was before this block existed. No default is
|
|
335
|
+
# invented: a guessed label is invisible to the scope that should see it
|
|
336
|
+
# and visible to one that should not, which is worse than no label.
|
|
337
|
+
#
|
|
338
|
+
# Every command in this block must end up returning 0. The EXIT/ERR trap set in
|
|
339
|
+
# section 2 exits the hook, so a non-zero status here would discard the
|
|
340
|
+
# pre-compaction context over a missing config file — a far worse regression
|
|
341
|
+
# than the unlabeled memories this fixes. The absent-config path is the common
|
|
342
|
+
# one today.
|
|
343
|
+
CODE_CONTEXT_MAX_BYTES=65536
|
|
344
|
+
|
|
345
|
+
# Walk up for the git project root, mirroring findProjectRoot() in
|
|
346
|
+
# cli/src/lib/commit-context/local-cache.ts. `-e`, not `-d`: inside a git
|
|
347
|
+
# worktree `.git` is a FILE, and the worktree root — not the main repo — is the
|
|
348
|
+
# project root (the TS uses fs.existsSync, which makes no such distinction).
|
|
349
|
+
find_project_root() { # <start-dir> -> project root on stdout, or nothing
|
|
350
|
+
local dir
|
|
351
|
+
dir=$(cd "$1" 2>/dev/null && pwd -P) || return 0
|
|
352
|
+
while [[ -n "$dir" && "$dir" != "/" ]]; do
|
|
353
|
+
if [[ -e "$dir/.git" ]]; then
|
|
354
|
+
printf '%s' "$dir"
|
|
355
|
+
return 0
|
|
356
|
+
fi
|
|
357
|
+
dir=$(dirname "$dir" 2>/dev/null) || return 0
|
|
358
|
+
done
|
|
359
|
+
return 0
|
|
360
|
+
}
|
|
361
|
+
|
|
362
|
+
# Keep only the six known keys whose values are non-empty strings, cap each,
|
|
363
|
+
# and emit NOTHING when nothing usable remains — so an empty or scope-free
|
|
364
|
+
# object is never passed as if it were a label. Malformed JSON makes jq exit
|
|
365
|
+
# non-zero with no output, which lands in the same "no scope" branch.
|
|
366
|
+
#
|
|
367
|
+
# `-s` (slurp) is load-bearing, not a style choice. jq accepts a STREAM of JSON
|
|
368
|
+
# documents: without `-s` the filter runs once per document and `jq -c` prints
|
|
369
|
+
# one line each, so a config holding two concatenated or newline-separated
|
|
370
|
+
# objects produced a MULTI-LINE string that was passed verbatim as one
|
|
371
|
+
# --code-context argument. parseCodeContextFlag() (cli/src/commands/memories.ts)
|
|
372
|
+
# JSON.parse()s it and process.exit(1)s before any network call. In THIS hook
|
|
373
|
+
# that loss is unrecoverable: the transcript the capture would have summarized
|
|
374
|
+
# is compacted away immediately afterwards. The `!= "{}"` guard below did not
|
|
375
|
+
# catch it either: `{"zzz":1}{"team":"b"}` normalizes to the two lines
|
|
376
|
+
# `{}` + `{"team":"b"}`, and that whole string is not `{}`. Slurping into an
|
|
377
|
+
# array and taking the first element means exactly one line can ever be emitted.
|
|
378
|
+
#
|
|
379
|
+
# The cap is 100 CODEPOINTS, deliberately below the server's 200. The server's
|
|
380
|
+
# CodeContextSchema uses Zod `.max(200)`, which counts UTF-16 code units, while
|
|
381
|
+
# jq's `[0:N]` slices by codepoint. Every astral-plane character (emoji, CJK
|
|
382
|
+
# extensions, mathematical alphanumerics) is 1 codepoint but 2 UTF-16 units, so
|
|
383
|
+
# a `[0:200]` cap emitted values of up to 400 units — over the server maximum,
|
|
384
|
+
# a 400 from the API, and the same silent capture loss. Since no codepoint
|
|
385
|
+
# exceeds 2 UTF-16 units, 100 codepoints can never exceed 200 units. Scope
|
|
386
|
+
# labels are short names (product/team/service); the extra truncation is
|
|
387
|
+
# unreachable in practice, and truncating is recoverable where a rejected
|
|
388
|
+
# request is not.
|
|
389
|
+
normalize_code_context() { # JSON on stdin -> normalized JSON object, or nothing
|
|
390
|
+
local out
|
|
391
|
+
out=$(jq -s -c '
|
|
392
|
+
(.[0] // {}) as $raw
|
|
393
|
+
| if ($raw | type) == "object" then
|
|
394
|
+
reduce ("product","repo","service","component","team","role") as $k ({};
|
|
395
|
+
if ($raw[$k] | type) == "string" and ($raw[$k] | length) > 0
|
|
396
|
+
then .[$k] = ($raw[$k][0:100])
|
|
397
|
+
else . end)
|
|
398
|
+
else {} end
|
|
399
|
+
' 2>/dev/null) || return 0
|
|
400
|
+
# The newline test is belt-and-braces: `-s` already guarantees one document,
|
|
401
|
+
# and jq -c escapes newlines inside string values. Nothing multi-line may ever
|
|
402
|
+
# reach --code-context again, whatever the filter above does.
|
|
403
|
+
if [[ -n "$out" && "$out" != "{}" && "$out" != "null" && "$out" != *$'\n'* ]]; then
|
|
404
|
+
printf '%s' "$out"
|
|
405
|
+
fi
|
|
406
|
+
return 0
|
|
407
|
+
}
|
|
408
|
+
|
|
409
|
+
CODE_CONTEXT_JSON=""
|
|
410
|
+
|
|
411
|
+
# 1. Env var. Tested for presence only — the value is never echoed or logged.
|
|
412
|
+
if [[ -n "${MX_CODE_CONTEXT:-}" ]]; then
|
|
413
|
+
CODE_CONTEXT_JSON=$(printf '%s' "$MX_CODE_CONTEXT" | normalize_code_context) || CODE_CONTEXT_JSON=""
|
|
414
|
+
fi
|
|
415
|
+
|
|
416
|
+
# 2. Repo file — consulted only when the env var yielded nothing usable.
|
|
417
|
+
if [[ -z "$CODE_CONTEXT_JSON" ]]; then
|
|
418
|
+
# ORDER IS LOAD-BEARING: harness-provided project dir, then the worktree path,
|
|
419
|
+
# then the cwd. Each source is TRIED IN TURN, and the transcript's directory
|
|
420
|
+
# is not a source at all. Both properties are corrections to earlier forms and
|
|
421
|
+
# both are pinned by the suite; read this before rewriting the expression.
|
|
422
|
+
#
|
|
423
|
+
# WHY EACH SOURCE IS TRIED SEPARATELY. The earlier form collapsed all three
|
|
424
|
+
# into ONE call: `find_project_root "${CLAUDE_PROJECT_DIR:-${CLAUDE_WORKTREE_PATH:-$(pwd)}}"`.
|
|
425
|
+
# `:-` substitutes only when a variable is UNSET or EMPTY — never when it is
|
|
426
|
+
# set to something useless. So a CLAUDE_PROJECT_DIR that is set but resolves
|
|
427
|
+
# to no repository (a stale path, a deleted directory, a path outside any
|
|
428
|
+
# checkout) consumed the single attempt and the cwd was NEVER consulted.
|
|
429
|
+
# Measured: CLAUDE_PROJECT_DIR=/proc and =/nonexistent/zz each produced
|
|
430
|
+
# {"product":"home","team":"DOTFILES-WRONG-SCOPE"} from the $HOME config.
|
|
431
|
+
# The loop below consults the next source instead, which `:-` cannot express.
|
|
432
|
+
#
|
|
433
|
+
# WHAT IS ACTUALLY KNOWN ABOUT CLAUDE_PROJECT_DIR IN THE CUSTOMER CONTEXT.
|
|
434
|
+
# It is the documented hook variable, and it is the right first source when it
|
|
435
|
+
# is present. This repo does NOT evidence that it is set for hooks installed
|
|
436
|
+
# by `mx mcp install`: every other reference to it is fleet code, and it was
|
|
437
|
+
# measured UNSET in a live Claude Code tool process (a tool process is not a
|
|
438
|
+
# hook process, so that is not disproof — but it is not confirmation either).
|
|
439
|
+
# The expression below is therefore designed to be CORRECT WHEN IT IS ABSENT:
|
|
440
|
+
# an unset or empty value is skipped by the loop and the cwd carries the case.
|
|
441
|
+
# Do not restructure this so that a present CLAUDE_PROJECT_DIR is required.
|
|
442
|
+
# WHY THE TRANSCRIPT DIRECTORY IS NOT A SOURCE. It has no legitimate resolving
|
|
443
|
+
# power, and the reason is DEPTH-INDEPENDENT — do not restate it as a claim
|
|
444
|
+
# about the transcript's nesting. An earlier version of this comment argued
|
|
445
|
+
# from a flat ~/.claude/projects/<slug>/<id>.jsonl layout and enumerated the
|
|
446
|
+
# three directories a walk could reach. That premise is false here. Measured
|
|
447
|
+
# on this machine: transcripts sit at BOTH depth 2 and depth 4 under
|
|
448
|
+
# ~/.claude/projects — 310 at depth 2, 5621 deeper — so any argument of the
|
|
449
|
+
# form "the walk can only ever reach these three named directories" does not
|
|
450
|
+
# hold. The premise that does hold, and that does not depend on depth:
|
|
451
|
+
#
|
|
452
|
+
# .git anywhere under ~/.claude, any depth: 0 (also no .hg, no .svn)
|
|
453
|
+
#
|
|
454
|
+
# An upward walk from any transcript directory traverses only directories
|
|
455
|
+
# inside ~/.claude, none of which carries a repository marker, so it cannot
|
|
456
|
+
# terminate inside that subtree at any depth. That leaves $HOME as its ONLY
|
|
457
|
+
# reachable non-empty outcome, which is precisely the defect this block exists
|
|
458
|
+
# to prevent: keeping dotfiles in git is common, so $HOME/.git exists on many
|
|
459
|
+
# machines, and with $HOME/.mx-code-context.json present every capture from
|
|
460
|
+
# every worktree on the machine was labelled from the home config. A
|
|
461
|
+
# confidently wrong label is worse than no label — invisible to the scope that
|
|
462
|
+
# should see it, visible to one that must not. Do not reintroduce it.
|
|
463
|
+
#
|
|
464
|
+
# CAVEAT, stated because this is a claim about a directory OUTSIDE this
|
|
465
|
+
# repository: it could stop being true, and nothing in this codebase would
|
|
466
|
+
# notice if a repository ever appeared under ~/.claude. Removing the leg does
|
|
467
|
+
# not depend on the caveat holding — the leg is simply gone — but any future
|
|
468
|
+
# argument to reinstate it must re-measure rather than cite this line.
|
|
469
|
+
#
|
|
470
|
+
# WHY $HOME IS REFUSED OUTRIGHT, AND WHY BOTH SIDES ARE CANONICALIZED. Belt
|
|
471
|
+
# and braces for the residual where the cwd itself is $HOME or a directory
|
|
472
|
+
# beneath it whose nearest .git is $HOME's. It also closes a consequence that
|
|
473
|
+
# is easy to miss: CC_ROOT is the basis of the symlink containment test below,
|
|
474
|
+
# so a CC_ROOT of $HOME silently widens "contained in the project" to
|
|
475
|
+
# "anywhere in the home directory", and $HOME/.mx-code-context.json symlinked
|
|
476
|
+
# to any other file under $HOME would resolve and be used. The cost is not
|
|
477
|
+
# supporting a user whose real project IS their home directory; that is the
|
|
478
|
+
# same confusion we want rejected.
|
|
479
|
+
#
|
|
480
|
+
# The comparison MUST canonicalize $HOME. CC_ROOT always arrives canonical —
|
|
481
|
+
# find_project_root builds it with `cd … && pwd -P` — while $HOME arrives
|
|
482
|
+
# verbatim from the environment, so a literal `==` against "$HOME" misses on
|
|
483
|
+
# every spelling that is not byte-identical. Four spellings were measured
|
|
484
|
+
# leaking the home label through a symlinked $HOME/.mx-code-context.json: a
|
|
485
|
+
# trailing slash ("/home/x/"), a "/." suffix ("/home/x/."), $HOME set to a
|
|
486
|
+
# SYMLINK to the real home, and a cwd reached through that same symlink.
|
|
487
|
+
# Symlinked home directories are routine — macOS firmlinks, NFS corporate
|
|
488
|
+
# homes, container images mapping /home/user onto another volume — so the
|
|
489
|
+
# trigger is a normal configuration and the miss is silent: the refusal does
|
|
490
|
+
# not fire, and the containment widening above returns with it. `cd … && pwd -P`
|
|
491
|
+
# is the same primitive find_project_root uses and handles all four in one step.
|
|
492
|
+
#
|
|
493
|
+
# HOME unset, or pointing at nothing, leaves _home_real empty and no refusal
|
|
494
|
+
# fires. That is unchanged from the previous `-n "${HOME:-}"` guard, not a
|
|
495
|
+
# regression. The `|| _home_real=""` is REQUIRED, not decorative: without it a
|
|
496
|
+
# failing `cd` leaves the assignment non-zero and last on its path, which fires
|
|
497
|
+
# the ERR trap and abandons the capture.
|
|
498
|
+
#
|
|
499
|
+
# ERR-TRAP SAFETY — verified, not assumed, because a regression here fires
|
|
500
|
+
# `trap 'exit 0' ERR` and silently abandons the capture. The loop body's only
|
|
501
|
+
# status-bearing statement is a `$(...)` assignment of find_project_root, which
|
|
502
|
+
# returns 0 on every path including the `cd` failure. The break is written as
|
|
503
|
+
# an `if` block for the same reason the $HOME refusal is. The earlier one-line
|
|
504
|
+
# form `[[ -n "$CC_ROOT" ]] && break` returns 1 whenever the loop CONTINUES —
|
|
505
|
+
# an earlier version of this comment claimed it returned 0, which was wrong. It
|
|
506
|
+
# was safe only POSITIONALLY: as a non-final command of an `&&` list it is
|
|
507
|
+
# exempt under the errexit rules, so nothing fired. That safety depends on
|
|
508
|
+
# where the statement sits and would evaporate the moment this loop became the
|
|
509
|
+
# last statement of a function: the function would return 1 and any `$(...)`
|
|
510
|
+
# call of it would fire the trap. The `if` form returns 0 and removes the
|
|
511
|
+
# positional dependence.
|
|
512
|
+
#
|
|
513
|
+
# The same reasoning is why the $HOME refusal is an `if` block ON PURPOSE: the
|
|
514
|
+
# one-line `[[ "$CC_ROOT" == "$_home_real" ]] && CC_ROOT=""` returns 1 when the
|
|
515
|
+
# test is false, and was measured firing the ERR trap when it landed last in an
|
|
516
|
+
# enclosing block. `pwd 2>/dev/null` keeps a deleted cwd from printing "error
|
|
517
|
+
# retrieving current directory" onto the hook's real stderr. This safety comes
|
|
518
|
+
# from find_project_root always returning 0, not from this hook omitting
|
|
519
|
+
# `set -E`, so it survives someone adding `set -E` later. Do not introduce a
|
|
520
|
+
# bare command on this path.
|
|
521
|
+
CC_ROOT=""
|
|
522
|
+
for _cand in "${CLAUDE_PROJECT_DIR:-}" "${CLAUDE_WORKTREE_PATH:-}" "$(pwd 2>/dev/null)"; do
|
|
523
|
+
[[ -n "$_cand" ]] || continue
|
|
524
|
+
CC_ROOT=$(find_project_root "$_cand")
|
|
525
|
+
if [[ -n "$CC_ROOT" ]]; then break; fi
|
|
526
|
+
done
|
|
527
|
+
_home_real=$(cd "${HOME:-/nonexistent}" 2>/dev/null && pwd -P) || _home_real=""
|
|
528
|
+
if [[ -n "$_home_real" && "$CC_ROOT" == "$_home_real" ]]; then
|
|
529
|
+
CC_ROOT=""
|
|
530
|
+
fi
|
|
531
|
+
CC_FILE="${CC_ROOT}/.mx-code-context.json"
|
|
532
|
+
if [[ -n "$CC_ROOT" ]]; then
|
|
533
|
+
# CWE-59. `-f`, `-r` and the read all follow symlinks, so a repo could check
|
|
534
|
+
# in `.mx-code-context.json` as a symlink to any file on the user's machine
|
|
535
|
+
# and the six allowlisted keys of it would be uploaded to the user's own
|
|
536
|
+
# MemNexus account. Resolve the path and require the result to stay inside
|
|
537
|
+
# the project root — the containment this same hook already applies to the
|
|
538
|
+
# transcript path earlier. Read through the RESOLVED path, so the link is
|
|
539
|
+
# not traversed a second time.
|
|
540
|
+
CC_REAL=$(realpath "$CC_FILE" 2>/dev/null || printf '')
|
|
541
|
+
if [[ -n "$CC_REAL" && "$CC_REAL" == "$CC_ROOT"/* && -f "$CC_REAL" && -r "$CC_REAL" ]]; then
|
|
542
|
+
# One open, bounded at the source (same 64KB bound as the TS resolver).
|
|
543
|
+
# The previous form size-checked with `wc -c` and then re-opened for jq:
|
|
544
|
+
# two opens on a path an untrusted repo controls, so a concurrent writer
|
|
545
|
+
# could present a small file to `wc` and a huge one to `jq` (TOCTOU) on a
|
|
546
|
+
# hot path. `head -c` bounds the read itself, which changes >64KB from
|
|
547
|
+
# "skipped" to "truncated, then rejected as invalid JSON" — the same
|
|
548
|
+
# observable outcome, no scope.
|
|
549
|
+
#
|
|
550
|
+
# `2>/dev/null` precedes the input redirect ON PURPOSE. Redirections apply
|
|
551
|
+
# left to right, so with `<"$CC_REAL" 2>/dev/null` a file that turned
|
|
552
|
+
# unreadable between the `-r` test and the open makes bash print the full
|
|
553
|
+
# path and "Permission denied" to the hook's REAL stderr, before the
|
|
554
|
+
# discard takes effect. Verified: reversing these two words reintroduces
|
|
555
|
+
# that leak. Do not reorder.
|
|
556
|
+
#
|
|
557
|
+
# The bytes are PIPED into jq, never routed through a variable. Bash
|
|
558
|
+
# strips NUL bytes out of command-substitution output and warns while
|
|
559
|
+
# doing it — from the parent shell reading the substitution, so the
|
|
560
|
+
# `2>/dev/null` above does not suppress that warning. Via a variable,
|
|
561
|
+
# `{"team":"a<NUL>b"}` printed a warning naming this script and line to
|
|
562
|
+
# the hook's real stderr, and then RESOLVED to team "ab": input the file
|
|
563
|
+
# does not contain, silently repaired before validation instead of
|
|
564
|
+
# rejected by it. Piping keeps the NUL inside jq, which rejects the
|
|
565
|
+
# document as malformed. Do not reintroduce an intermediate variable.
|
|
566
|
+
CODE_CONTEXT_JSON=$(head -c "$CODE_CONTEXT_MAX_BYTES" 2>/dev/null <"$CC_REAL" | normalize_code_context) || CODE_CONTEXT_JSON=""
|
|
567
|
+
fi
|
|
568
|
+
fi
|
|
569
|
+
fi
|
|
570
|
+
|
|
571
|
+
# Nothing resolved -> pass nothing at all, so the create command line is
|
|
572
|
+
# byte-identical to the pre-scope version. The `[@]+` guard keeps an empty array
|
|
573
|
+
# safe to expand under `set -u` on bash < 4.4.
|
|
574
|
+
CODE_CONTEXT_ARGS=()
|
|
575
|
+
if [[ -n "$CODE_CONTEXT_JSON" ]]; then
|
|
576
|
+
CODE_CONTEXT_ARGS=(--code-context "$CODE_CONTEXT_JSON")
|
|
577
|
+
fi
|
|
578
|
+
|
|
301
579
|
# ── 6. Save memory ──────────────────────────────────────────────────────
|
|
302
580
|
if mx_verbatim_guard "$TRANSCRIPT_PATH" "$CONTENT"; then
|
|
303
581
|
# Bounded: network write. On timeout we land on the existing `|| true` path —
|
|
@@ -306,6 +584,7 @@ if mx_verbatim_guard "$TRANSCRIPT_PATH" "$CONTENT"; then
|
|
|
306
584
|
--conversation-id "NEW" \
|
|
307
585
|
--content "$CONTENT" \
|
|
308
586
|
--topics "auto-captured,context-compaction" \
|
|
587
|
+
"${CODE_CONTEXT_ARGS[@]+"${CODE_CONTEXT_ARGS[@]}"}" \
|
|
309
588
|
>/dev/null 2>&1 || true
|
|
310
589
|
fi
|
|
311
590
|
|