Deep Discovery blocks when it cannot preserve the account, repository, review, package, consent, or generation contract. Treat the message as a boundary to resolve, not something to bypass.
Deep Discovery is not enabled for this account
The route is in a limited account-enabled rollout. Confirm you are signed into the intended account and API environment. If the message remains, read the public guide, prepare only non-sensitive local material you control, and contact support about pilot access. Reinstalling the extension or calling the CLI directly cannot bypass eligibility.
The workspace is not ready
- Open exactly one trusted Git workspace folder.
- If Git is missing, install it and restart VS Code.
- If the folder is not a repository, accept the local initialization offer or run
git inityourself. - A remote, protected default branch, first commit, and clean working tree are not required to start.
- In a multi-root window, select the exact folder before starting or resuming.
Codex or Copilot is unavailable
Confirm the selected provider is installed, signed in, and usable in its own chat. Run SwarmCraft: Choose AI Provider to select the provider that is actually ready. Provider usage is needed for discovery and review, not package preparation.
The sidebar is missing or stale
Run SwarmCraft: Resume Deep Discovery. Check VS Code notifications and use SwarmCraft: Show Output when support needs the content-safe extension log. Reload the window after upgrading the extension.
A source needs attention
- Binary originals require a reviewed Markdown sidecar; the binary is never packaged.
- Changed, missing, or stale selected sources must be corrected and the complete set confirmed again.
- Remove secrets or unsupported file types instead of asking AI to disguise them.
- Source-selection changes invalidate the previous package.
A discovery document blocks preparation
Open the lifecycle row named in the message. Finish owner review, resolve placeholders or open decisions, or use a justified NOT_APPLICABLE state. Supporting sources cannot substitute for a missing curated decision.
The package is too large or exceeds the token budget
Do not truncate or summarize reviewed material silently. Remove irrelevant supporting sources through explicit selection, resolve duplicated source material, or narrow the discovery scope. Curated documents remain required. Prepare again and review the new digest.
Upload was interrupted
Use Prepare Discovery Package Again only when preparation or transport failed before admission. Reopen the preview and authorize the current digest. Once a package is admitted, recover it from Discoveries rather than creating competing snapshots.
Project generation failed
Use Try project creation again for a retryable failure. The original payment or launch-free entitlement and admitted package remain safe. For Support needed, open the authenticated support workspace. Do not pay again, upload a modified package, or paste discovery content into a general support message.
For CLI diagnostics, create the content-safe package support bundle requested by support:
swarmcraft discovery support-bundle --workspace . --run <run-id>
The bundle excludes document text and source paths. Review it before sharing.