@swarmcraftai/cli 0.4.0 → 0.4.2

package/CHANGELOG.md

@@ -2,6 +2,19 @@
 
 All notable changes to the SwarmCraft CLI are documented in this file.
 
+## 0.4.2
+
+- Reconciles generated repository skills through a monotonic, owner-preserving template-set contract before new one-shot runs, while retaining the recorded guidance for resumed runs.
+- Adds the company-specific design-system lifecycle across discovery, prototyping, planning, implementation, checking, and review, including executable Storybook workbenches, React prototype consumers, official identity assets, provenance, and owner-facing review guidance.
+- Keeps design conformance and required design gates active during doing when optional checking is disabled, and hardens packet synchronization against concurrent VS Code updates.
+- Allows resumed runs to extend their recorded agent-request ceiling so capacity exhaustion can recover without creating a replacement run.
+
+## 0.4.1
+
+- Conceals passwords, authenticator codes, and recovery codes during interactive login instead of echoing secret input in the terminal.
+- Completes enrolled MFA in the same login attempt, with an explicit recovery-code fallback that does not require placing credentials in command arguments.
+- Refreshes the generated Deep Discovery guidance for exception-first review, coverage-based prototyping, source gathering, product disposition, and temporary replacement integrations.
+
 ## 0.4.0
 
 - Seeds a collaborative plan-first workflow that turns approved phases into SwarmCraft tasks while keeping planning and implementation as explicit, reviewable steps.

package/README.md

@@ -4,7 +4,7 @@ SwarmCraft CLI prepares a local repository for a SwarmCraft project board and ru
 
 Use it to authenticate with SwarmCraft, list available projects, seed workspace guidance files, materialize task packets, run one-shot implementation passes, resume or inspect runs, and create support bundles.
 
-Deep Discovery uses the provider-neutral `@swarmcraft/discovery-package-contract` for exact-text packaging, canonical hashing, and local validation. The CLI never asks an AI provider to generate transport JSON or tasks and never contains SwarmCraft's private seven-slice compiler.
+Deep Discovery uses the provider-neutral `@swarmcraft/discovery-package-contract` for exact-text packaging, canonical hashing, and local validation. The CLI never asks an AI provider to generate transport JSON or tasks and never contains SwarmCraft's private server-side catalogue compiler.
 
 ## Package Shape
 
@@ -87,8 +87,12 @@ swarmcraft status --run <run-id> --workspace <path> --delegation <delegation-id>
 swarmcraft delegation end --delegation <delegation-id>
 ```
 
+Interactive login conceals password input. When MFA is enrolled, the same command securely prompts for the current authenticator code and offers a recovery-code fallback; secrets do not need to be placed in the command line.
+
 `swarmcraft init` validates the workspace git state, seeds the shared SwarmCraft repo guidance files, materializes non-done task packets, links those packets back to SwarmCraft, and prints the next commands.
 
+Repository seeding uses the same monotonic template-set contract as the VS Code extension. A newer CLI adds missing skills and updates unchanged generated guidance, preserves owner edits as conflicts, removes only unchanged retired files, and never downgrades guidance written by a newer client. The CLI leaves these repository changes uncommitted for normal review. New one-shot runs reconcile before agent execution; resumed runs retain their existing run guidance rather than reseeding midway through the run.
+
 The task contract is a clean cutover from the earlier project-ticket format. Upgrade the API, CLI, and VS Code extension together; old `ticketId` packet files and `--ticket` flags are not accepted. Preserve any owner-authored notes, remove the retired generated packet files, and run `swarmcraft init` again to materialize current `taskId` packets from the board.
 
 `swarmcraft discovery prepare` is projectless and deterministic. It requires the versioned discovery binding, `.swarmcraft/discovery.sources.json`, current selected-source digests, and all nine curated documents to be reviewed or explicitly not applicable. Repeated `--source` arguments must exactly match the aggregate owner-confirmed text projection when supplied by the extension. Empty, draft, unresolved, stale-sidecar, binary, secret-bearing, oversized, or mismatched preparation is blocked before upload.
@@ -101,13 +105,17 @@ Run diagnostics contain only schema version, phase, error class, timestamps, cou
 
 `swarmcraft discovery validate` reruns deterministic package and local-staleness checks without launching a provider. Untracked and ignored owner-selected text is preserved and allowed but remains the owner's backup responsibility. A failed run never truncates, summarizes, or silently drops content: correct the reported review/source issue and prepare again.
 
-`swarmcraft one-shot` bootstraps the workspace, runs the doing lane through the selected agent provider, syncs packet updates back to SwarmCraft, writes `.swarmcraft/runs/<run-id>/manifest.json`, streams progress to the terminal, writes agent logs under `.swarmcraft/runs/<run-id>/logs/`, and moves accepted work to `done` by default. Customer one-shots should normally pair this with `--commit-policy done` so each completed task creates a local commit. Use `--checking on` or `--reviewing on` only for internal validation runs that deliberately need those extra lanes.
+`swarmcraft one-shot` bootstraps the workspace, runs the doing lane through the selected agent provider, syncs packet updates back to SwarmCraft, writes `.swarmcraft/runs/<run-id>/manifest.json`, streams progress to the terminal, writes agent logs under `.swarmcraft/runs/<run-id>/logs/`, and moves accepted work to `done` by default. With checking off, the driver ignores the reusable implementation skill's normal checking handoff, syncs its evidence, moves the task directly to `done`, commits when requested, and continues. Before synchronization, the CLI reloads the server-authoritative board and retries bounded optimistic-revision conflicts, allowing one-shot to run while the VS Code extension is open and observing the same packets. Customer one-shots should normally pair this with `--commit-policy done` so each completed task creates a local commit. Use `--checking on` or `--reviewing on` only for internal validation runs that deliberately need those extra lanes.
+
+For interface-bearing packets, the generated `swarmcraft-do` contract owns design conformance even when checking is off: it resolves the owner-controlled locator, uses applicable system capabilities, covers relevant states, runs existing required design commands, and records exact evidence in packet notes. A failing required deterministic design gate must leave doing incomplete. One-shot does not install design tooling, infer authority to mutate the design system, or treat unavailable visual evidence as passing.
 
 Useful safety and support commands:
 
 ```bash
-swarmcraft one-shot --project <project-id> --workspace <path> --agent-provider codex --max-agent-requests 40
+swarmcraft one-shot --project <project-id> --workspace <path> --agent-provider codex --max-agent-requests 100
 swarmcraft one-shot --project <project-id> --workspace <path> --agent-provider custom --agent-command '<command with {command}>' --agent-api-key-env-name MY_AGENT_KEY
 swarmcraft doctor --workspace <path> --agent-provider codex
 swarmcraft support-bundle --run <run-id> --workspace <path>
 ```
+
+VS Code uses a 100-request default and checks the unfinished board before launch. When the selected lane policy could require more, it asks the operator to approve a sufficient limit before starting. A stopped run can extend its recorded ceiling with `swarmcraft resume --run <run-id> --workspace <path> --max-agent-requests <n>`.