[shravan-lambdatest]

kane-cli 0.10.0 lets a team work in one Test Manager project: folders are linked to a shared project, and what one person saves (use-cases, tests, Test Manager cases, coverage) the whole team sees. Skill 0.1.3 never mentions it. An agent following it sets up a local store, never reaches the team's project, and can't recover from the refusals a linked folder gives. This release teaches the shared-project path and the agent contract behind it.

What changes for agents

• Where the work goes, first. In agent mode a folder that isn't set up yet goes local unless it's linked with --project <id>. The decision tree now asks where the work goes before any assurance command.
• New reference shared-projects.md covers:
  • finding or making the project (kane-cli projects list|create --agent) and getting a folder's project id;
  • linking (context ingest|extract --project <id>);
  • the journey: add the documents, save the session, a one-question checkpoint before designing, design, save, fill the variables, run, cover;
  • approximate credit costs per step;
  • where everything lives: test files, Test Manager cases, runs, coverage, variables;
  • a teammate joining, and bringing the team's tests into a folder: kane-cli context pull where the release has it, with a check via --help, else copying only the test files and their recordings;
  • what a linked folder refuses;
  • kane-cli run in a linked folder, and "tests from two projects".
• New reference agent-contract.md: which agent flag each command takes, the stream shapes (first and last line per command), every event in a linked folder, how to use next: [{cmd, why}], exit codes, and each refusal code with what to do and the command to run.
• New reference explore.md, exploration together with assurance:
  • starting one into the team's project, always with --project, since explore doesn't read a folder's link; a
    project nobody has shared yet is shared by its first design job;
  • asking the person before a run that may change data (the default policy is mutating);
  • apps behind a login (--deps, --allow-domain, variables);
  • scope and work limits, a private app through a tunnel, a run from this machine;
  • watching, stopping, running again, and moving to another site;
  • checking what it designed, and turning design off or on;
  • getting its tests into a linked folder (kane-cli context pull) or a fresh one (kane-cli context pull --project <id>), then their first runs.
• Linked-folder sections in assurance.md, testrun.md (designed tests run on their scenario's Test Manager case: first run, replay, heal, counting, the case-stop codes), cards.md (a coverage card), first-run.md, ready-check.md (getting or updating the skill with kane-cli install skill [version]; corrected sign-in and balance rows) and four short notes elsewhere.
• Preflight: preflight.sh and preflight.ps1 print a ## link section with the linked project's name and id, none, or unreadable when kane-cli couldn't read the link either.
• Smaller corrections: --max-steps defaults to 50; the dry run applies to testrun run; redesigning a use-case that is still proposed needs --force --allow-unreviewed; test-manager.md lists exit 1.
• Checked against kane-cli's code. Codex and Claude reviewed every reference against the code, and each finding was
  verified before it was fixed. Outside shared projects, these references now match what kane-cli does today:
  • testmd delete needs --yes;
  • imports may name tests and modules;
  • the lock-conflict default is readonly;
  • exit codes, replay cost, the evidence merge rules, analyzer results, the parsing table;
  • coverage: one figure, --rollup ignored;
  • evolve skips a use-case whose source changed;
  • --limit is 1-200;
  • the login profile default.

What changes for people

New user-guide pages:

• docs/user-guide/assurance/shared-projects.md: working with your team in a Test Manager project.
• docs/user-guide/exploration.md: map your app and design tests from it. First run, whether it can change your data, an app behind a login, a private app through an LT tunnel, keeping a run in bounds, the map, stopping and re-running, the tests it designs and getting them into a folder, exit codes, troubleshooting. Linked from the guide's index, Getting started, Shared projects and Troubleshooting. Shared-project sections are added to the getting-started, agents, assurance (overview, context, design, coverage, sharing, maintain), testrun, Test Manager, variables, configuration and troubleshooting pages, and to the guide's index.

Version

skill-installer/package.json goes to 0.2.0. Its minimum kane-cli is 0.10.0. The three skill copies (skill-installer/skills/, .claude/skills/kane-cli/, .agents/skills/kane-cli/) are byte-identical.

Text that depends on a kane-cli release

Some lines in the user-guide pages need a later kane-cli release:

• kane-cli context pull in a linked folder;
• the "no tests here yet" refusal in a linked folder;
• exploration.

Each of these lines carries a <!-- release: … --> comment, so it can be kept or removed when that release is cut. The skill itself checks kane-cli context pull --help before using the pull.

Tests

skill-installer/test/preflight.test.mjs and preflight-ps1.test.mjs expect the new link section in the section order, and cover link in a plain folder, a linked one, and a link file kane-cli can't read (unreadable). npm test locally: 80 tests, 75 pass, 0 fail, 5 skipped (the PowerShell ones, Windows only); the skill installer tests workflow passes on Ubuntu, macOS and Windows with Node 18 and 22.

Two agents, Codex and Claude, each did a real first run of a designed test in a linked folder with this skill, headless, and both passed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CWzoM9tH5Wua2MvuDasu94