export declare const LOCAL_FILES_REFERENCE_MD = "# Local-files privacy mode \u2014 single source of truth\n\nThis file is the canonical contract for fully local, no-database planning and\nrecaps. It is shared word for word by `/visual-plan` and `/visual-recap`. Read it\nin full before using local-files mode; do not call any hosted Plan tool for a\nlocal plan/recap except the schema-only block-catalog lookup described below.\n\n<!-- SHARED-CORE:local-files START -->\n\n**When to use it.** Use local-files privacy mode when the user explicitly asks\nfor no DB writes, no hosted Plan database writes, no Plan MCP publish, fully local\nfiles, offline/private work, or repo-owned/source-controlled artifacts, or when\n`AGENT_NATIVE_PLANS_MODE=local-files` is set. Also use it when a user or repo\npolicy says the work must stay under their own brand, domain, source control, or\ninfrastructure. In this mode the plan/recap data must never be sent to the Plan\nMCP server or the Plan app action surface. This is the only exception to the\nalways-publish rule in `references/connection.md`.\n\nThe local-files contract:\n\n- **Read context locally.** Read source, diff, and stat context from local files\n  and shell commands only. For recaps, the\n  `npx @agent-native/core@latest recap collect-diff`, `scan`, and\n  `build-prompt --local-files` helpers are safe \u2014 they operate on local files and\n  do not write to the Plan database.\n- **Fetch the block catalog first** (it sends no plan content). Use the MCP\n  `get-plan-blocks` tool if it is already available, or run\n  `npx @agent-native/core@latest plan blocks --out plan-blocks.md` and read that\n  file before authoring MDX; it calls the public no-auth `get-plan-blocks` route.\n  Use `--format schema` when you need exact nested fields. If network access is\n  unavailable, use the bundled `references/*.md` and rely on `plan local check` to\n  catch invalid tags. Copy the catalog examples verbatim for the fields the\n  registry table cannot encode: `checklist` items need `id` and `label`;\n  `question-form` questions need `id`, `title`, and `mode`, and each option needs\n  `id` and `label`; and `Code` / `AnnotatedCode` / `Diff` are whitespace-sensitive\n  \u2014 encode multiline code as JSON string attributes such as `code={\"const x =\\n  y\"}`\n  (a static template literal is accepted only when it has no `${...}`\n  interpolation). `plan local check` is a quick OFFLINE lint (a subset of the\n  renderer schema), so a green `check` does not guarantee the plan renders.\n  `plan local verify` also stays on-device: it uses the offline lint unless it\n  can reach a Plan renderer on an explicit loopback `--app-url`.\n- **Write a local MDX folder.** Use `plans/<slug>/` to check the artifact into the\n  repo, or a repo-ignored/temporary folder such as `.agent-native/plans/<slug>/`\n  or `/tmp/agent-native-plans/<slug>/` when it should not be checked in. The\n  folder holds `plan.mdx`, optional `canvas.mdx`, optional `prototype.mdx`, and\n  optional `.plan-state.json`. For a recap, set `kind: \"recap\"` and\n  `localOnly: true` in the frontmatter/state. Use that exact folder as\n  `<plan-dir>` in every command below.\n- **Check, then serve.** Run\n  `npx @agent-native/core@latest plan local check --dir <plan-dir>` before any\n  preview, then\n  `npx @agent-native/core@latest plan local serve --dir <plan-dir> --kind <plan|recap> --open`\n  (use `--kind plan` for plans, `--kind recap` for recaps). Report the local\n  bridge URL from stdout or `<plan-dir>/.plan-url`; treat `.plan-url` as a local\n  token file and do not commit it. The URL opens the hosted Plan UI but reads from\n  the localhost bridge on this machine, so it is not shareable across machines.\n  The token is carried in the URL fragment (which is not sent to the hosted\n  origin), and the local-plan route disables DOM autocapture and session replay\n  while retaining sanitized pageviews and error monitoring. On\n  macOS `--open` prefers Chromium browsers; if Safari opens, switch to\n  Chrome/Chromium because Safari can block the hosted HTTPS page from fetching the\n  HTTP localhost bridge. If the Plan app itself is running locally with the same\n  `PLAN_LOCAL_DIR`, the `/local-plans/<slug>` route is also valid. In a truly\n  offline environment, hand off the `<plan-dir>` path after `plan local check` and\n  note that interactive preview requires network access to the hosted Plan UI or a\n  running local Plan app.\n- **Headless verify.** Run\n  `npx @agent-native/core@latest plan local verify --dir <plan-dir> --kind <plan|recap>`.\n  It starts the bridge and checks the private-network preflight and JSON payload\n  entirely on loopback. It never sends MDX or assets to a remote validation\n  action. When `--app-url` points to a loopback Plan app, verify also validates\n  against that local app's real renderer schema via `validate-local-plan-source`.\n  A non-`ok` result with\n  `validation.valid: false` lists the renderer's exact schema-path issues (e.g.\n  `blocks[1].data.tabs[0]...`); fix those before handing off. If `validation.ran`\n  is `false`, verify used the offline lint because the app URL was remote or the\n  local Plan app was unavailable. Run a local Plan app and pass\n  `--app-url http://localhost:8096` for the authoritative check. If the browser hangs on\n  \"Loading plan\", fetch the `bridgeUrl` from the verify/serve JSON to read the\n  concrete validation error.\n- **Never call hosted tools for that plan/recap.** Do not call\n  `create-visual-plan`, `create-ui-plan`, `create-prototype-plan`,\n  `create-plan-design`, `create-visual-recap`, `create-visual-questions`,\n  `import-visual-plan-source`, `update-visual-plan`, `patch-visual-plan-source`,\n  `get-plan-feedback`, `export-visual-plan`, `set-resource-visibility`, or any\n  other hosted Plan tool \u2014 except the schema-only block-catalog lookup above.\n- **Feedback is file/chat feedback.** Update the MDX files directly, rerun\n  `plan local check`, and rerun `serve` or `verify` when that preview path is\n  available. Summarize the new local URL when one exists; otherwise summarize the\n  checked `<plan-dir>` path. Hosted comments, sharing, screenshots, history, usage\n  attachment, and publish/export receipts are unavailable until the user\n  explicitly opts into publishing.\n\nLocal-files mode prevents plan/recap content from being uploaded to the\nAgent-Native Plan server or database. It does not by itself make the coding agent's language model local;\nfor that stronger boundary the host agent/model must also be local or otherwise\napproved by the user.\n\n<!-- SHARED-CORE:local-files END -->\n";
//# sourceMappingURL=local-files.d.ts.map