feat: provide stable CLI wrappers for Comet state and archive commands

[jacobleft]

🔎 Existing issue check

• I have searched the existing issues.

🧭 Problem

Comet skill docs correctly say to discover scripts through comet/reference/scripts.md, but agents can still easily reach for stale or guessed internal paths. In one archive session, a stale path was attempted:

/home/luo/.codex/skills/comet/bin/comet-state.js

The actual installed script was:

/home/luo/.codex/skills/comet/scripts/comet-state.mjs

The canonical bootstrap works, but requiring agents to locate .mjs files directly is brittle across Comet package/runtime migrations.

✨ Proposed solution

Expose stable wrapper commands for agent-facing operations, for example:

comet state check <change> archive
comet guard <change> build --apply
comet archive <change>
comet next <change>

These wrappers should remain stable even if internal files move from shell to Node, .js to .mjs, or bundled runtime paths.

🎯 Primary area

CLI command / user interaction (app/)

🪐 Workflow phase

Not phase-specific

🔀 Alternatives considered

Continue requiring agents to run the bootstrap block from comet/reference/scripts.md. This works but remains fragile after context compression or when agents remember older layout paths.

🧰 Compatibility notes

• Installed package: @rpamis/comet@0.4.0-beta.3
• Current installed skill scripts are under ~/.codex/skills/comet/scripts/*.mjs.
• Wrapper commands could keep script discovery as a fallback for older installs.

🧩 Additional context

This is especially useful for recovery flows where agents need to run state/guard/archive commands after context compaction.