Skip to content

Release 0.2.1: docs polish, K3 rationale, real-run screenshots, version bump - #3

Merged
oppnc merged 3 commits into
mainfrom
release/0.2.1
Aug 1, 2026
Merged

oppnc merged 3 commits into
mainfrom
release/0.2.1

Conversation

@oppnc

@oppnc oppnc commented Aug 1, 2026

Copy link
Copy Markdown
Owner

Summary

Companion hardening (#2) + documentation/release polish for 0.2.1.

Documentation & marketing

  • README (CN+EN): K3 benchmark rationale with professional sources (nxcode, Hugging Face), auto-trigger rules explanation, real-run screenshot (LIMS → Linear light theme, 2m55s)
  • README compatibility table: pin minimum Kimi Code ≥ 0.30.0

Bug fixes

  • SECURITY.md: fix Supported versions table (0.4.x → 0.2.x — 0.4.x never existed)
  • bug_report.yml: placeholder 0.1.0 → 0.2.1

Version bump (0.2.0 → 0.2.1)

All version fields synced: package.json, marketplace.json, plugin.json, companion VERSION, acp-client PLUGIN_VERSION, smoke.mjs, README badges/tables, AGENTS.md.

CHANGELOG

  • Mark 0.2.1 as released (drop in development tag)

Checklist

  • npm test passes (90 tests)
  • User-facing docs updated in both CN and EN
  • CHANGELOG updated (CN + EN)
  • Version fields bumped together
  • No secrets / job data / local settings committed

oppnc added 2 commits August 1, 2026 07:30
Task lifecycle / session safety:
- --timeout keeps the ACP session resumable: on request timeout the client
  sends session/cancel, failed jobs record sessionId, and --resume reuses the
  exact same thread (verified end-to-end with real kimi).
- Cancel race (POSIX): failOrphan skips jobs already marked cancelled.

Acceptance fixes:
- Plan mode with read-only tools but zero plan text is now a failed handoff
  (ok:false, exit 1, planEmptyText:true) — the plan itself is the deliverable
  in plan mode; previously it passed with ok:true and empty text.
- Goal framing no longer bypasses Q&A / reply-exactly exclusion: --goal with a
  "Reply with exactly: …" or how-to Objective no longer wastes Mode B continue
  nudges (previously asGoal returned action unconditionally).

Hardening:
- Mode A empty-turn retries default 2→5, configurable via --empty-retries or
  KIMI_EMPTY_RETRIES (0 disables).
- task/goal reject unknown --flags instead of leaking them into Kimi's prompt.
- Media TOCTOU (existsSync→statSync race) is a clean error, not a raw throw.
- Job pruning removes logs/<job>.log with the job file; prunes throttled 30s.
- status --wait / result --wait exit non-zero while the job is still running.
- splitRawArgumentString handles escaped quotes/backslashes inside quotes.
- Docs: default mode documented as full-auto approval (plan rejects writes);
  command docs + AGENTS.md + CHANGELOG updated for 0.2.1.

Tests (90, kimi-free):
- fake-kimi ACP fixture; acp-client (timeout session retention, empty-retry
  budget); companion-cli (wait exit codes, orphan reconcile, cancel race,
  resume hint, unknown flag); turn-policy (plan acceptance, goal framing);
  host-free-attack (planEmptyText contract); args; state.
…on bump to 0.2.1

- Bump all version fields 0.2.0 -> 0.2.1 (package.json, marketplace, plugin.json, companion, acp-client, smoke, README x2, AGENTS)
- README (CN+EN): add K3 benchmark rationale (nxcode + Hugging Face sources), auto-trigger explanation, real-run screenshot (LIMS to Linear light, 2m55s)
- README compatibility table: pin minimum Kimi Code >= 0.30.0
- SECURITY.md: fix Supported versions (0.4.x -> 0.2.x)
- bug_report.yml placeholder: 0.1.0 -> 0.2.1
- CHANGELOG: mark 0.2.1 as released (drop in-development tag)
- Add docs/assets/cc_test.png
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

# Conflicts:
#	CHANGELOG.md
#	CHANGELOG.zh-CN.md
@oppnc
oppnc merged commit 2bd55b0 into main Aug 1, 2026
1 check passed
@oppnc
oppnc deleted the release/0.2.1 branch August 1, 2026 15:02
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