Skip to content

Document issue timeline and issue wakeup for CLI v0.6.x, raise floor to v0.6.0 - #4

Open
bitstrum wants to merge 2 commits into
multica-ai:mainfrom
bitstrum:docs/cli-0.6.2-drift
Open

bitstrum wants to merge 2 commits into
multica-ai:mainfrom
bitstrum:docs/cli-0.6.2-drift

Conversation

@bitstrum

@bitstrum bitstrum commented Oct 13, 2026 •

Copy link
Copy Markdown

The scheduled Lint job against the latest CLI has failed every day since the CLI added multica issue timeline and multica issue wakeup (coverage check), and UNDOCUMENTED_OK still lists plugin, which is no longer a CLI command.

Changes

  • SKILL.md: document issue timeline (command reference, plus a note in Inspecting Runs: issue get is the current state, issue timeline is how it got there) and issue wakeup (command reference and a short Wakeups section: every fire is a paid run, bound repeating rules with --expires-in / --max-fires, create replaces the whole rule, checkin only from every/cron runs).
  • SKILL.md: state the CLI version the file was last checked against (v0.6.2), and tell the agent that on a newer CLI --help is the source of truth, and to check multica --help / multica issue --help before saying the CLI cannot do something. Points at scripts/lint-skill-commands.py when the skill sits inside a checkout or plugin install. This narrows the window between a CLI release and the next skill refresh.
  • lint: drop the stale plugin entry from UNDOCUMENTED_OK.
  • Minimum CLI raised from v0.4.26 to v0.6.0 (MIN_CLI_VERSION, SKILL.md, README.md, README.zh.md, CURSOR.md, .cursor/rules/multica-cli.mdc). issue wakeup as documented first ships in v0.6.0: v0.5.1–v0.5.3 have an older wakeup without runs, delete, checkin, --until-status, --expires-in and --max-fires; v0.5.0 has none.
  • test-lint: fixtures no longer inherit the real UNDOCUMENTED_OK. Before, the stale plugin entry failed every expect-no-errors case, so CI stopped at the regression tests and never printed the actual drift report.
  • Plugin version 1.1.0 → 1.2.0 in plugin.json and marketplace.json, so installed plugins pick up the change.

On raising the floor

The lint comment calls this a real compatibility decision, so flagging it explicitly. The alternative keeps v0.4.26: a per-command "since" map in the lint ({"issue timeline": "0.4.31", "issue wakeup": "0.6.0"}) that --validity-only skips below that version, plus a "(v0.6.0+)" marker in SKILL.md. Happy to switch to that if you prefer.

Verification

  • scripts/lint-skill-commands.py against v0.6.2: OK (validity + coverage).
  • scripts/lint-skill-commands.py --validity-only against v0.6.0: OK.
  • scripts/test-lint.py: all regression tests pass (v0.6.0 and v0.6.3).
  • scripts/lint-skill-commands.py against v0.6.3 (latest): OK.
  • CLI binaries were downloaded from the multica-ai/multica releases and checked against checksums.txt (darwin-arm64).

Overlap with #3

Disjoint in content. git merge-tree against #3 conflicts only in .claude-plugin/plugin.json and marketplace.json, where #3's description change sits next to this version bump; whichever lands second resolves it in one line.

bitstrum and others added 2 commits October 13, 2026 17:11
…to v0.6.0

The daily lint against the latest CLI has failed since the CLI added
issue timeline and issue wakeup. Document both, drop the stale plugin
entry from UNDOCUMENTED_OK, and tell agents to treat --help as the
source of truth when the installed CLI is newer than the version the
skill was last checked against.

issue wakeup as documented (runs, delete, checkin, --until-status,
--expires-in, --max-fires) first ships in v0.6.0; 0.5.x has an older
shape. Raise MIN_CLI_VERSION and every stated minimum to 0.6.0, and
bump the plugin to 1.2.0.
The fixtures inherited the repo's allowlist, so when the CLI dropped an
exempted command (plugin, in v0.6.2) every expect-no-errors case failed
as "stale" and CI stopped before the real drift report ran.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015FeG6aNDiBWFZNWTagUHVW
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant