@corvio/cli 0.1.0-beta.40 → 0.1.0-beta.41

package/dist/cli.js

@@ -39,7 +39,7 @@ import {
   agentCredentialPath,
 } from "./core.js";
 
-const VERSION = "0.1.0-beta.40";
+const VERSION = "0.1.0-beta.41";
 const DEFAULT_API_BASE = "https://api.corvio.ai/v1";
 const DEFAULT_APP_BASE = "https://corvio.ai";
 const USER_AGENT = `corvio-cli/${VERSION}`;
@@ -200,13 +200,13 @@ const COMMAND_HELP = Object.freeze({
   workspaces: `Usage:\n  corvio workspaces list\n  corvio workspaces use <workspace-id>\n  corvio workspaces current\n  corvio workspaces create --name <name> [--kind personal|team]\n\nWorkspace status and blocked capability reasons are returned with each item.`,
   capabilities: `Usage: corvio capabilities [--json]\n\nShow live API resources, principal scopes, selected Workspace status, and CLI compatibility.`,
   collaboration: `Usage:\n  corvio collaboration status [--project <path>] [--provider codex|claude_code|copilot|grok_build|muse_code|workbuddy]\n\nCheck local Corvio prerequisites and every discoverable Corvio Skill copy. Current copies stay quiet; non-current receipts include one compact Agent notice and a source-aware next action. Standalone refresh commands pin the verified installer when available and preserve project/global scope. Muse Code and Grok Build inspect their native and shared Agent Skill roots; WorkBuddy inspection is read-only. The CLI cannot prove that the current host task loaded a particular copy, or whether remote MCP or host memory is active.`,
-  ask: `Usage: corvio ask --prompt <text> [--file <path>] [--asset-ids <id,id>] [--inline-material-file <path> --inline-material-title <title>] [--conversation-id <id>] [--sources workspace,web,memory] [--allow-actions] [--background] [--processing-profile auto|economy|standard|deep] [--max-processing-profile economy|standard|deep] [--scan-mode auto|always|off] [--skills-extraction-mode auto|always|off] [--caller-model <host-model>] [--context-file <json>] [--idempotency-key <key>]\n\nAnswer-only is the default: omit --allow-actions; there is no --mode option. Keep the user's natural question unchanged, then append the smallest complete decision-relevant context or stable handles as a separate clause. A carried Project handle normally bounds a cross-branch question without enumerating all descendants. Handles are evidence addresses: do not invent a comparison rubric, prescribe reasoning steps, substitute another user objective, or turn current Tree labels into a detailed task plan. Unless the user chose them, do not invent taxonomy, titles, artifact count, or Corvio's internal plan; Corvio chooses the cognitive structure and carriers. In a bounded read-only continuation, start this foreground command exactly once when a trusted current-task or prior receipt already proves this authenticated CLI and exact Workspace; do not launch an identical Question concurrently or retry before terminal exit. If the shell tool yields a running-session handle, wait on that exact handle until the CLI exits instead of answering from prior context. It returns the terminal Question without model-visible polling. Use --background for work that should outlive the current shell; it returns one durable operation immediately. Inspect it with questions operation, stop it with questions cancel, and use the terminal conversation_id for a corrected follow-up instead of silently changing an in-flight objective. Transport continuity does not prove a cheaper processing profile; leave processing on auto unless the remaining transformation independently justifies another profile. Do not install, probe, or switch to the CLI only to avoid MCP polling, and do not extend it to an unbound Workspace. --file retains an original selected local file, verifies its hash, and attaches the finalized Asset to this exact question. --asset-ids attaches already-retained Corvio Assets. --inline-material-file is only for Markdown the Host just composed: it carries that text as source evidence without first creating a root Page. Use it with --allow-actions when durable owner, structure, Memory, or Skill reconciliation remains semantic; do not use it instead of --file for original local evidence, and do not run a second cleanup Question after docs create. For this route keep --skills-extraction-mode auto; the returned knowledge_policy owns Memory/Skill disposition. Do not force or suppress Memory/Skill creation in the Question. Rejection, blocking, or pre-acceptance failure leaves that owner unresolved: follow typed recovery or report the unresolved effect without a direct Page or synthetic Asset fallback. Use --allow-actions when Corvio should create the Page, Spreadsheet, Presentation, Code, HTML Artifact, Memory, or qualifying Project Skill that best serves the result. A continuation handle is subject evidence, not necessarily the durable write destination: for a reusable pattern or method, resolve the fitting same-scope Memory or Skill owner before admitting or merging it. If the current turn already supplies a complete current owner receipt plus the exact Memory/Skill correction or non-merge boundary, pass them directly to one allow-actions Question; do not search or open an answer-only Question first. Read first only when a missing fact could change target, scope, authority, or constraints. Read the terminal Question receipt and use artifact.url or links.primary_artifact verbatim; reader_output artifacts are deliverables, structure_container artifacts are hierarchy, and node_id is never a document URL. Upload alone is not evidence of interpretation. Skill extraction mode always requires --allow-actions and an evidence-backed decision, not forced Skill creation; answer-only questions may use auto or off.`,
+  ask: `Usage: corvio ask --prompt <text> [--file <path>] [--asset-ids <id,id>] [--inline-material-file <path> --inline-material-title <title>] [--conversation-id <id>] [--sources workspace,web,memory] [--allow-actions] [--background] [--processing-profile auto|economy|standard|deep] [--max-processing-profile economy|standard|deep] [--scan-mode auto|always|off] [--skills-extraction-mode auto|always|off] [--caller-model <host-model>] [--context-file <json>] [--idempotency-key <key>]\n\nAnswer-only is the default: omit --allow-actions; there is no --mode option. Keep the user's natural question unchanged, then append the smallest complete decision-relevant context or stable handles as a separate clause. A carried Project handle normally bounds a cross-branch question without enumerating all descendants. When exact continuation handles lack current content, read the narrowest relevant handles before any Workspace search or action; never search to rediscover an exact carried owner; multiple handles alone do not justify semantic synthesis. Handles are evidence addresses: do not invent a comparison rubric, prescribe reasoning steps, substitute another user objective, or turn current Tree labels into a detailed task plan. If the smallest required exact-owner reads can supply every operand for a bounded deterministic judgment, read them and answer in the Host; unless the user explicitly requests only a verdict, state the decisive reusable rule and current operands instead of omitting a retrieved threshold or condition; do not run this answer-only command before or after merely to restate them. Use this command only when the remaining answer still requires semantic synthesis. Unless the user chose them, do not invent taxonomy, titles, artifact count, or Corvio's internal plan; Corvio chooses the cognitive structure and carriers. In a bounded read-only continuation, start this foreground command exactly once when a trusted current-task or prior receipt already proves this authenticated CLI and exact Workspace; do not launch an identical Question concurrently or retry before terminal exit. If the shell tool yields a running-session handle, wait on that exact handle until the CLI exits instead of answering from prior context. It returns the terminal Question without model-visible polling. Use --background for work that should outlive the current shell; it returns one durable operation immediately. Inspect it with questions operation, stop it with questions cancel, and use the terminal conversation_id for a corrected follow-up instead of silently changing an in-flight objective. Transport continuity does not prove a cheaper processing profile; leave processing on auto unless the remaining transformation independently justifies another profile. Do not install, probe, or switch to the CLI only to avoid MCP polling, and do not extend it to an unbound Workspace. --file retains an original selected local file, verifies its hash, and attaches the finalized Asset to this exact question. --asset-ids attaches already-retained Corvio Assets. --inline-material-file is only for Markdown the Host just composed: it carries that text as source evidence without first creating a root Page. Keep the selected file title and all remaining Markdown content verbatim after only user-required safety exclusions, including headings, internal blank lines, spaces, and punctuation; only terminal newline normalization is allowed. Corvio owns the semantic transformation. A known destination owner does not turn that Host body into prompt prose: when the body participates in the semantic effect, --inline-material-file remains required. Use it with --allow-actions when any durable owner, structure, Memory, or Skill decision or semantic incorporation remains; do not use it instead of --file for original local evidence, and do not run a second cleanup Question after docs create. For this route keep --skills-extraction-mode auto; the returned knowledge_policy owns Memory/Skill disposition. Do not force or suppress Memory/Skill creation in the Question. Rejection, blocking, or pre-acceptance failure leaves that owner unresolved: follow typed recovery or report the unresolved effect without a direct Page or synthetic Asset fallback. Use --allow-actions when Corvio should create the Page, Spreadsheet, Presentation, Code, HTML Artifact, Memory, or qualifying Project Skill that best serves the result. A continuation handle is subject evidence, not necessarily the durable write destination: for a reusable pattern or method, resolve the fitting same-scope Memory or Skill owner before admitting or merging it. search.content_complete closes discovery only; a returned title or snippet is not the owner's complete current body. Read before an effect that updates that same content-bearing Page, Memory, or Skill when its current wording can change preservation, removal, ordering, or merge; this does not relax exact continuation: read a carried Project when its receipt lacks current body or topology needed for handoff; do not read a Project newly selected by complete search merely to route new current-turn material or reconfirm an archive/non-merge boundary established there. If the current turn already supplies a complete current owner receipt plus the exact Memory/Skill correction or non-merge boundary, pass them directly to one allow-actions Question; do not search or open an answer-only Question first. Read first only when a missing fact could change target, scope, authority, or constraints. If user-excluded bytes were removed before dispatch and the accepted source receipt identifies the sanitized input, do not read an output solely to prove those bytes were never sent. Read the terminal Question receipt and return every user-visible result with artifact.url or links.primary_artifact verbatim; keep those URL values through any justified post-effect content read because a later owner read without a URL does not erase the earlier link receipt; reader_output artifacts are deliverables, structure_container artifacts are hierarchy, and node_id is never a document URL. Upload alone is not evidence of interpretation. Skill extraction mode always requires --allow-actions and an evidence-backed decision, not forced Skill creation; answer-only questions may use auto or off.`,
   agents: `Usage:\n  corvio agents list\n  corvio agents connect [--provider codex|claude_code|copilot|grok_build] [--project <path>] [--permission-profile read_only|workspace_write|danger_full_access] [--trigger-policy owner_only|workspace_members] [--display-name <name>] [--recover-credential] [--no-listen]\n  corvio agents create --handle <handle> --display-name <name> [--provider codex|claude_code|copilot|grok_build|grok_bot|muse|muse_code|custom] [--permissions read,comment,edit]\n  corvio agents update <id> [--display-name <name>] [--status active|paused|revoked] [--permissions <list>]\n  corvio agents rotate <id>\n\n'connect' binds the current Git project (or --project path) to one stable personal Agent. Repeating it is idempotent; another project creates another Agent. It reports provider/CLI, listener, and local Skill prerequisites separately; run corvio collaboration status after installing or refreshing the Skill. The CLI cannot prove that the current host task loaded those surfaces. The default workspace_write profile is limited by the provider's native sandbox. owner_only is the safe trigger default. Secrets and absolute project paths stay local.`,
   agent: `Usage:\n  corvio agent claim [--worker-id <id>] [--wait-seconds <0-30>]\n  corvio agent renew <event-id> --lease-token <token> [--lease-seconds <30-900>]\n  corvio agent complete <event-id> --lease-token <token> [--result-file <json>]\n  corvio agent fail <event-id> --lease-token <token> --error <message>\n  corvio agent mentions --document-id <id> [--query <name>]\n  corvio agent comments --document-id <id>\n  corvio agent comment --document-id <id> --body <text> [--selection-file <json>] [--start-new-chain] [--idempotency-key <key>]\n  corvio agent reply <thread-id> --document-id <id> --body <text> [--source-event-id <id> --source-event-lease-token <token>|--start-new-chain] [--idempotency-key <key>]\n  corvio agent status <thread-id> --document-id <id> --status open|resolved\n  corvio agent closeout --document-id <id> [--thread-id <id>] --body <verified-result> [--status open|resolved] [--idempotency-key <key>]\n  corvio agent run [--provider codex|claude_code|copilot|grok_build|custom] [--handler <executable>] [--agent <id>] [--once] [--processing-profile auto|economy|standard|deep] [--max-processing-profile economy|standard|deep] [--scan-mode auto|always|off] [--skills-extraction-mode auto|always|off] [--caller-model <host-model>]\n\nUse mentions before commenting when the target is uncertain; aliases resolve to stable user or Agent IDs and ambiguity fails closed. Use closeout when a Corvio document or comment owned the task: it returns the verified result to that surface and reads document/comments back. Agent-to-Agent comments require either a claimed source event or explicit --start-new-chain. The runner iteratively exchanges origin-scoped evidence with Corvio Query/Writer, then invokes the bound provider inside its local project. Local code changes use the recorded provider permission profile; complex Corvio document changes belong to Query/Writer. Provider children never receive Corvio credentials.`,
-  questions: `Usage:\n  corvio questions list [--limit <n>] [--cursor <cursor>] [--conversation-id <id>]\n  corvio questions get <question-id>\n  corvio questions operation <operation-id> [--after-cursor <n>] [--wait-until-terminal] [--timeout-seconds <1-7200>]\n  corvio questions cancel <operation-id> --yes\n\nA Question operation is the durable owner for background work. operation returns only new user-visible milestones after --after-cursor and never exposes hidden reasoning or provisional answer text. --wait-until-terminal keeps deterministic polling in this process and returns a typed deadline receipt if the local deadline expires. cancel is idempotent; treat cancellation_requested as non-terminal and verify cancelled before telling the user the task stopped. Cancellation does not roll back effects that already settled. To correct the objective, stop or finish the current operation, then use corvio ask --conversation-id <conversation_id> so the new Question is an explicit successor.`,
+  questions: `Usage:\n  corvio questions list [--limit <n>] [--cursor <cursor>] [--conversation-id <id>]\n  corvio questions get <question-id>\n  corvio questions operation <operation-id> [--after-cursor <n>] [--wait-until-terminal] [--timeout-seconds <1-7200>]\n  corvio questions cancel <operation-id> --yes\n\nA Question operation is the durable owner for background work. operation returns only new user-visible milestones after --after-cursor and never exposes hidden reasoning or provisional answer text. --wait-until-terminal keeps deterministic polling in this process and returns a typed deadline receipt if the local deadline expires. readback_verified proves the identity, revision, topology and other fields actually returned; it does not prove omitted body text. Effect summaries, include/exclude lists, hashes, excerpts, and readback_verified prove only those returned fields; none is the exact owner body. A typed field that explicitly returns every required per-owner inclusion/exclusion closes semantic separation when exact wording is not required; it proves no unreturned fact or exact body. Otherwise, adding, preserving, or removing specific statements in an existing owner, or keeping named facts out of a reusable owner, makes exact post-effect wording part of acceptance: if the receipt omits the body, read each affected exact owner once with a direct read command, never another Question. Merely retaining or connecting selected material and reporting its final location does not require another body read after a terminal owner/topology/link receipt. Corvio naturally choosing several new owners for that general request does not change this boundary. If excluded bytes were removed before dispatch and the accepted source receipt identifies that sanitized input, do not read an output solely to prove those bytes were never sent. Before replying, compare the user's acceptance wording with the receipt: if they asked to add, preserve, or remove specific content and neither the exact body nor complete typed include/exclude results were returned, read that identified content owner once. A verified terminal owner/topology receipt stays authoritative when Corvio chooses a title different from the user's descriptive phrase; that difference alone does not justify asking the user to recheck or offering another move. Return every user-visible result with its canonical URL, and keep that URL through any justified post-effect content read; a later owner read without a URL does not erase the earlier link receipt. cancel is idempotent; treat cancellation_requested as non-terminal and verify cancelled before telling the user the task stopped. Cancellation does not roll back effects that already settled. To correct the objective, stop or finish the current operation, then use corvio ask --conversation-id <conversation_id> so the new Question is an explicit successor.`,
   conversations: `Usage:\n  corvio conversations list [--limit <n>] [--cursor <cursor>]\n  corvio conversations get <conversation-id>`,
-  search: `Usage: corvio search <query> [--limit <n>] [--page-id <id>] [--node-id <id>]\n\nUse one narrow query for initial owner discovery. When content_complete=true and hit_count=0, continue from current-turn facts; do not retry with synonyms, translations, broader wording, or another language in the same turn.`,
-  docs: `Usage:\n  corvio docs list [--limit <n>] [--cursor <cursor>] [--lifecycle active|archived]\n  corvio docs get <id> [--output <path>]\n  corvio docs read <id> [--mode auto|overview|line-range|section|search|full] [--start-line <n> --end-line <n>|--section-ref <S#>|--query <text>] [--max-chars <n>]\n  corvio docs patch <id> --input <json> --yes [--operation-id <id>] [--change-summary <text>]\n  corvio docs table-read <id> [--table-id <id>] [--after-row-id <id>] [--limit <1-100>]\n  corvio docs table-mutate <id> --input <json> --yes [--operation-id <id>] [--change-summary <text>]\n  corvio docs create --title <title> [--file <path>|--markdown <text>] [--parent-node-id <id>] [--idempotency-key <key>]\n  corvio docs update <id> [--title <title>] [--file <path>|--markdown <text>] [--expected-revision <n>] [--change-summary <text>]\n  corvio docs move <id> --parent-node-id <id>\n  corvio docs archive <id> --yes\n  corvio docs restore <id> --yes\n  corvio docs share <id> --yes [--display-name <name>]\n  corvio docs open <id>\n\nUse \`docs read --mode auto\` first for a small full body or a large-document overview, then read an exact section or line range. Use \`docs patch\` when the host already knows 1-20 exact L# replacements; it preserves untouched lines and returns a compact verified delta. A selected Markdown file can become an editable Page without resending the body through the model. Use direct \`docs create\` only when one Page and its durable owner are already decision-ready; when the exact standalone body, Page carrier, and root position are fixed, skip owner discovery because it cannot change the write. If the Host just composed Markdown for future use but its owner, Work Model structure, Memory, or Skill outcome remains semantic, use one \`corvio ask --allow-actions --inline-material-file <path>\` before any durable write; never follow direct create with an automatic cleanup Question. A rejected, blocked, or failed inline-material Question still has an unresolved owner and is not permission to fall back to \`docs create\` without a later independent user decision. Use \`docs update\` only when whole-body replacement is the smallest faithful change. Delegate document-wide judgment, cross-source synthesis, structure/formatting interpretation, and typed Spreadsheet, Presentation, Code, or HTML work to \`corvio ask --allow-actions\`. A Project is a structure container; body writes fail with project_structure_container_body_write_disabled, while a title-only Project rename remains valid. Projects stay at the Workspace root and cannot be nested; use \`files organize\` or \`ask --allow-actions\` for Work Model maintenance. Use table-read plus table-mutate for bounded stable-ID cell updates or row appends. Agent-authenticated document changes require --change-summary and create a visible document-level comment after the guarded update. When a document/comment is the task owner, use \`corvio agent closeout\` to return verified work to that same collaboration surface and read it back.`,
+  search: `Usage: corvio search <query> [--limit <n>] [--page-id <id>] [--node-id <id>]\n\nUse one narrow query for initial owner discovery. Skip search when an exact continuation or owner receipt already binds the subject and use docs get/read for any needed current content. A missing matching leaf, assignee, or old wording does not override unambiguous current-user update facts inside that bound Project. content_complete describes the discovery result set, not the full body of a returned owner. Fetch before an effect that updates that same content-bearing Page, Memory, or Skill when current wording can change preservation, removal, ordering, or merge; this does not relax exact continuation: fetch a carried Project when its receipt lacks current body or topology needed for handoff; do not fetch a Project newly selected by complete search merely to route new current-turn material or reconfirm an archive boundary established there. When content_complete=true and hit_count=0, continue from current-turn facts; do not retry with synonyms, translations, broader wording, or another language in the same turn.`,
+  docs: `Usage:\n  corvio docs list [--limit <n>] [--cursor <cursor>] [--lifecycle active|archived]\n  corvio docs get <id> [--output <path>]\n  corvio docs read <id> [--mode auto|overview|line-range|section|search|full] [--start-line <n> --end-line <n>|--section-ref <S#>|--query <text>] [--max-chars <n>]\n  corvio docs patch <id> --input <json> --yes [--operation-id <id>] [--change-summary <text>]\n  corvio docs table-read <id> [--table-id <id>] [--after-row-id <id>] [--limit <1-100>]\n  corvio docs table-mutate <id> --input <json> --yes [--operation-id <id>] [--change-summary <text>]\n  corvio docs create --title <title> [--file <path>|--markdown <text>] [--parent-node-id <id>] [--idempotency-key <key>]\n  corvio docs update <id> [--title <title>] [--file <path>|--markdown <text>] [--expected-revision <n>] [--change-summary <text>]\n  corvio docs move <id> --parent-node-id <id>\n  corvio docs archive <id> --yes\n  corvio docs restore <id> --yes\n  corvio docs share <id> --yes [--display-name <name>]\n  corvio docs open <id>\n\nUse \`docs read --mode auto\` first for a small full body or a large-document overview, then read an exact section or line range. Use \`docs patch\` when the host already knows 1-20 exact L# replacements; it preserves untouched lines and returns a compact verified delta. A selected Markdown file can become an editable Page without resending the body through the model. Use direct \`docs create\` only when one Page and its durable owner are already decision-ready; when the exact standalone body, Page carrier, and root position are fixed, skip owner discovery because it cannot change the write. If Host-composed Markdown participates in a future-use semantic effect, use one \`corvio ask --allow-actions --inline-material-file <path>\` before any durable write even when the destination owner is known; an owner handle is routing evidence and does not turn the body into prompt prose; never follow direct create with an automatic cleanup Question. A rejected, blocked, or failed inline-material Question still has an unresolved owner and is not permission to fall back to \`docs create\` without a later independent user decision. Use \`docs update\` only when whole-body replacement is the smallest faithful change. Delegate document-wide judgment, cross-source synthesis, structure/formatting interpretation, and typed Spreadsheet, Presentation, Code, or HTML work to \`corvio ask --allow-actions\`. A Project is a structure container; body writes fail with project_structure_container_body_write_disabled, while a title-only Project rename remains valid. Projects stay at the Workspace root and cannot be nested; use \`files organize\` or \`ask --allow-actions\` for Work Model maintenance. Use table-read plus table-mutate for bounded stable-ID cell updates or row appends. Agent-authenticated document changes require --change-summary and create a visible document-level comment after the guarded update. When a document/comment is the task owner, use \`corvio agent closeout\` to return verified work to that same collaboration surface and read it back.`,
   projects: `Usage:\n  corvio projects list [--limit <n>]\n  corvio projects create --title <title> [--idempotency-key <key>]\n\nProjects are durable root-level grouping owners in the Corvio Docs tree and cannot be nested under another Project. Reuse a matching Project instead of creating one ceremonial Project per file; use semantic branch Pages and leaves for deeper Work Models. 'corvio folders' is an alias.`,
   files: `Usage:\n  corvio files list [--limit <n>]\n  corvio files get <id> [--content]\n  corvio files download <id> [--output <path>]\n  corvio files upload --file <path> [--mime-type <type>] [--organize --instruction <text> --additional-asset-ids <id,id> --yes] [--wait-until-terminal] [--timeout-seconds <1-7200>]\n  corvio files organize <id> --instruction <text> --yes [--additional-asset-ids <id,id>] [--target-root-node-id <project-node-id>] [--processing-profile auto|economy|standard|deep] [--scan-mode auto|always|off] [--skills-extraction-mode auto|always|off] [--wait-until-terminal] [--timeout-seconds <1-7200>]\n  corvio files operation <operation-id> [--wait-until-terminal] [--timeout-seconds <1-7200>]\n  corvio files resume <operation-id> --yes [--wait-until-terminal] [--timeout-seconds <1-7200>]\n  corvio files cancel <operation-id> --yes\n  corvio files open <id>\n\nUse --content only when source facts are needed. It returns one bounded AI-safe projection with hash, completeness, and truncation receipts; it does not rewrite or materialize the original. Upload alone preserves the exact original, provenance, hash, policy, and stable Asset ID. Organization is a separate asynchronous value step: one coherent source set can produce reader-facing structure, source reconciliation, Memory candidates, and qualifying Project Skills. Pass --instruction a weak natural goal plus explicit user constraints and only authority facts needed to prevent wrong identity or scope. Keep source-derived facts in the source; do not precompute an outline, edit checklist, taxonomy, titles, artifact count, or sole leaf target from current visibility. A heterogeneous source may update several real Projects while its provenance carrier stays a standalone document; do not direct Corvio to make the source Page an umbrella Project. For a newly finalized Asset that should enter a Work Model or Skill evaluation, use one organize operation as the sole semantic owner; do not open ask before or after it for the same Asset set. --target-root-node-id is optional and accepts only a Project node_id returned by projects list, never a Page/document UUID or leaf node; omit it when the Project is not known. Use --wait-until-terminal when a filesystem-capable Host should keep deterministic polling inside this one foreground CLI invocation; --timeout-seconds is a local wait deadline, and reaching it returns the latest non-terminal receipt rather than claiming completion. Without that flag, 'files operation' remains an immediate read. Inspect terminal output_document plus skills_evaluation; evaluated_no_qualifying_skill is valid. Resume reuses the same durable operation after resolving its blocker; cancel is idempotent.`,
   sync: `Usage:\n  corvio sync init --root-node-id <id> [--dir <path>] [--name <name>]\n  corvio sync status|plan|pull [--dir <path>]\n  corvio sync push --yes [--dir <path>]\n  corvio sync resolve --conflict-id <id> --strategy use-remote|keep-local --yes [--dir <path>]`,
@@ -221,7 +221,7 @@ function contextualHelp(command, action) {
   if (normalizedCommand === "docs") {
     commandHelp = `${baseCommandHelp}\n\nDocument commands accept either a bare document ID or the canonical workspace_id/document_id handle returned by Corvio. A canonical handle that disagrees with the selected Workspace fails before any remote request. Document reads return canonical_id for direct reuse.`;
   } else if (normalizedCommand === "ask") {
-    commandHelp = `${baseCommandHelp}\n\nFor one coherent authorized future-use outcome that combines original files with Host-generated Markdown, finalize the originals and make one allow-actions call with both --asset-ids (or --file) and --inline-material-file. The original remains an Asset, the Host result remains a typed inline resource, and this Question is the single semantic effect owner; do not run files organize before or after it for the same mixed packet.`;
+    commandHelp = `${baseCommandHelp}\n\nFor one coherent authorized future-use outcome that combines original files with Host-generated Markdown, finalize the originals and make one allow-actions call with both --asset-ids (or --file) and --inline-material-file. The original remains an Asset, the Host result remains a typed inline resource, and this Question is the single semantic effect owner; do not run files organize before or after it for the same mixed packet. Use search and docs get/read for owner discovery and current readback; never use an answer-only ask as an owner lookup or preview before an allow-actions ask for the same objective. A complete owner receipt contains both its stable binding and every current decision-grade fact, not merely a handle. A bound Project plus unambiguous current-user update facts is enough to delegate reconciliation; absence of a matching leaf, assignee, or old wording does not reopen authority. Carry exact handles for the chosen owner and any stale, archived, wrong-scope, or non-merge owner that constrains the effect.`;
   } else if (normalizedCommand === "files") {
     commandHelp = `${baseCommandHelp}\n\nThe one-organize rule applies to Asset-only Work Model intake. If the same coherent authorized outcome also includes Host-generated Markdown, use one corvio ask --allow-actions call with the finalized Asset IDs and --inline-material-file instead of splitting the packet across files organize and ask.`;
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@corvio/cli",
-  "version": "0.1.0-beta.40",
+  "version": "0.1.0-beta.41",
   "description": "Official Corvio Workspace CLI for questions, knowledge search, documents, and Agent workflows.",
   "type": "module",
   "bin": {