@mytegroupinc/myte-core 0.0.46 → 0.0.47

package/README.md

@@ -21,7 +21,10 @@ This package exists so the public wrapper can stay small and versioned cleanly.
 ## Behavior Summary
 
 - Snapshot-style commands such as `bootstrap`, `sync-qaqc`, `feedback-sync`, and `suggestions sync` write local `MyteCommandCenter` data.
-- `feedback status|edit|assign|archive` writes reviewable local YAML artifacts; `feedback submit|revise|reviews|review` routes them through the backend owner-review membrane.
+- `feedback status|edit|assign|archive|refine` writes reviewable local YAML artifacts.
+- `feedback submit|revise|comment` are live writes that require `--confirm-write --approval-artifact <path>`.
+- `feedback review|move|undo|apply` are governed writes with backend permission checks but no approval artifact flags.
+- `feedback-sync|get|history|reviews|prd-versions|prd-diff|validate` are read/sync/validation commands with no approval artifact flags.
 - `feedback move|comment|undo|prd-versions|prd-diff|history` calls the project-key Feedback API while leaving lifecycle rules and permissions server-side. `feedback move --feedback-ids` sends one batch move request.
 - `feedback validate|apply` remains available for validation and owner-direct apply paths; live authorization, stale checks, and history stay server-side.
 - `query --with-diff` requires project repos to be configured for diff collection and fails fast when no matching local project repo can be resolved.
@@ -41,15 +44,29 @@ This package exists so the public wrapper can stay small and versioned cleanly.
 
 ## Live Write Approval
 
-Project-key write commands add a server-validated approval envelope only after the caller supplies `--confirm-write --approval-artifact <path>`.
+Only selected project-key writes require a server-validated approval envelope. The CLI adds `write_approval` metadata only for those commands after the caller supplies `--confirm-write --approval-artifact <path>`.
 
-- The approval artifact must be a local `.md`, `.yml`, `.yaml`, or `.json` file shown to and approved by the user.
+| Category | Commands | Artifact |
+| --- | --- | --- |
+| Required | `create-prd`, `update-team`, `update-owner`, `update-client`, `feedback submit`, `feedback revise`, `feedback comment`, `suggestions create`, `suggestions revise` | Yes |
+| Not required | `run-qaqc`, `mission status`, `mission archive`, `suggestions review`, `feedback review`, `feedback move`, `feedback undo`, `feedback apply` | No |
+| Never required | `config`, `query`, `bootstrap`, `sync-qaqc`, `feedback-sync`, `suggestions sync`, `feedback get/history/reviews/prd-versions/prd-diff/validate`, local feedback draft commands | No |
+
+- The approval artifact must be a local `.md`, `.markdown`, `.yml`, `.yaml`, or `.json` file shown to and approved by the user.
 - The artifact must list the exact operation, proposed change, and every target id or PRD item.
-- Batch writes must enumerate every item and the CLI sends the matching batch count to the API.
-- The API validates the payload hash after stripping transport metadata, so direct HTTP writes with only the API key do not bypass approval.
-- The package does not bundle the large MyteCody engine binary or the async
-  Responses bridge implementation. See `THIRD_PARTY_NOTICES.md` and
-  `TRADEMARKS.md` for Codex lineage and Myte brand notices.
+- Batch artifacts for required actions must enumerate every item and the CLI sends the matching batch count to the API.
+- For required actions, the API validates the payload hash after stripping transport metadata, so direct HTTP writes with only the API key do not bypass approval.
+- For actions marked `Not required`, the backend still enforces project-key authentication, idempotency, owner/delegate capability rules, stale-state guards, validation, rate limits, and audit history.
+- In plain language, the artifact is the human-reviewed record of the exact write the agent is about to send. It is not a permission grant and it does not bypass project owner/delegate checks, idempotency, stale-state guards, validation, or audit.
+- Minimum artifact contents are the exact command, every target id or PRD item, a complete proposed-change summary, a reason, and `batch_count` when one command sends multiple items.
+- Mission edit/create batches use `suggestions create` or `suggestions revise`; list every item, including `change_type`, `mission_id` for updates, proposed title/description for creates, and `suggestion_id` plus expected revision for revisions.
+- PRD batches use one `create-prd fileA.md fileB.md ...`; list each PRD file/title/client ref and make `batch_count` match the number of PRDs.
+- Feedback submit/revise/comment artifacts are usually the same YAML or markdown file being submitted. For inline text or stdin, use a separate approval memo with the feedback id or request id and exact content.
+- Team, owner, and client update artifacts should name the audience and include the exact message body or a complete summary. Client updates should include target contact ids when used.
+- `feedback review --request-ids`, `feedback move --feedback-ids`, `mission status --mission-ids`, `mission archive --mission-ids`, and `run-qaqc --mission-ids` are batched governed writes, but they are marked `Not required` and should not receive approval artifact flags.
+- The package does not bundle the large MyteCody engine binary or the async
+  Responses bridge implementation. See `THIRD_PARTY_NOTICES.md` and
+  `TRADEMARKS.md` for Codex lineage and Myte brand notices.
 
 ## Agent Usage Contract
 
@@ -57,20 +74,20 @@ Coding agents should treat `MYTE_API_KEY` as a project-scoped Project Assistant
 
 - Load it from the workspace `.env` or environment. `MYTE_PROJECT_API_KEY` is accepted as a compatibility fallback.
 - Call `myte config --json` first when project identity or local repo detection is uncertain.
-- Hydrate mission context with `bootstrap` first instead of scraping the web UI. `bootstrap` writes mission cards and mission suggestion thread state.
+- Hydrate mission context with `bootstrap` first instead of scraping the web UI. `bootstrap` writes mission cards, mission suggestion thread state, and `MyteCommandCenter/AgentsMyteAPI.md`.
 - Use `suggestions sync` only when you need to refresh mission review-thread state without refreshing the full board.
 - Use `query --with-diff` for project-scoped code review, planning, and implementation questions.
-- Use `create-prd` only with reviewed markdown files. The markdown file body is the PRD document; `description` is only the short board/card summary.
-- Use `feedback status|edit|assign|archive` for reviewable local artifacts, `feedback submit` for owner review, and `feedback review` for owner/delegate decisions.
+- Use `create-prd` only with reviewed markdown files and `--confirm-write --approval-artifact <path>`. The markdown file body is the PRD document; `description` is only the short board/card summary.
+- Use `feedback status|edit|assign|archive|refine` for reviewable local artifacts. `feedback submit` and `feedback revise` require an approval artifact; `feedback review` does not because the backend owner/delegate decision is the approval control.
 - Use `feedback review --request-ids` for batch owner/delegate decisions; it sends one grouped backend batch, not one request per item.
-- Use `suggestions create` for both existing-mission edits and new-mission proposals. The only valid `change_type` values are `update` and `create`.
-- Use `suggestions revise` only against an existing `suggestion_id`; do not send `change_type` on revisions because the backend keeps the thread's original type.
-- Use `suggestions review` for owner/elevated mission-review decisions: `approve`, `request_changes`, or `reject`.
+- Use `suggestions create` for both existing-mission edits and new-mission proposals, with `--confirm-write --approval-artifact <path>`. The only valid `change_type` values are `update` and `create`.
+- Use `suggestions revise` only against an existing `suggestion_id`, with `--confirm-write --approval-artifact <path>`; do not send `change_type` on revisions because the backend keeps the thread's original type.
+- Use `suggestions review` for owner/elevated mission-review decisions: `approve`, `request_changes`, or `reject`. No approval artifact is required for review decisions.
 - Use `mission archive` for project-key lifecycle archival. Do not send `Archived` through `mission status`; restore archived missions from the web archived-board view.
 - Use `feedback move` only when a direct audited state move is intended and include a concrete `--reason`. Use `--feedback-ids` for batch active-state moves or authorized batch archive.
-- Use `feedback comment --feedback-id <id> --body-file ./comment.md` for text-only feedback-specific implementation notes. Attachments remain web UI only for this project-key endpoint.
+- Use `feedback comment --feedback-id <id> --body-file ./comment.md --confirm-write --approval-artifact ./comment.md` for text-only feedback-specific implementation notes. Attachments remain web UI only for this project-key endpoint.
 - Do not use the project-key API/CLI to unarchive Feedback. Normal `feedback-sync` excludes archived Feedback; unarchive from the web archived Feedback view.
-- Use `update-team` when an agent needs to leave a project-level implementation note or verification comment.
+- Use `update-team --confirm-write --approval-artifact <path>` when an agent needs to leave a project-level implementation note or verification comment.
 
 Do not use `MYTE_API_KEY` against account/JWT web endpoints. The direct project-key surface is `/api/project-assistant/*`.
 
@@ -91,7 +108,7 @@ Feedback comment support:
 
 - `feedback-sync` includes existing feedback comment turns in local context.
 - Feedback-specific comment creation exists in the web backend at `/api/feedbacks/<feedback_id>/comments`, protected by JWT/project assignment.
-- Project-key comment creation is available through `myte feedback comment --feedback-id <id> --body "..."` or `--body-file ./comment.md`.
+- Project-key comment creation is available through `myte feedback comment --feedback-id <id> --body "..." --confirm-write --approval-artifact ./comment.md` or `--body-file ./comment.md --confirm-write --approval-artifact ./comment.md`.
 - The project-key feedback comment endpoint is text-only in this slice and caps content at 500,000 characters. Use the web UI when comment attachments are required.
 
 ## Mission Action Map
@@ -100,12 +117,12 @@ Feedback comment support:
 | --- | --- | --- |
 | Sync mission cards and review threads | `myte bootstrap --json` | Refreshes `MyteCommandCenter/data/missions/*.yml`, project structure, and `MyteCommandCenter/data/mission-ops.yml`. |
 | Sync only mission review threads | `myte suggestions sync --json` | Refreshes `MyteCommandCenter/data/mission-ops.yml` while preserving local workspace drafts. |
-| Suggest edit to existing mission | `myte suggestions create` with `change_type: update` and `mission_id` | Creates or appends to an active review thread; live mission is unchanged until approval. |
-| Suggest new mission | `myte suggestions create` with `change_type: create` | Requires `change_set.title` and `change_set.description`; creates a review thread only; the mission card is created only after approval. |
-| Revise a suggestion | `myte suggestions revise` with `suggestion_id` | Adds another revision to the same thread. Do not include `change_type`. |
-| Review a suggestion | `myte suggestions review` with `review_action: approve|request_changes|reject` | Project Owner or elevated mission-review delegate required. Approval mutates/creates the mission once; reject archives the thread only; request_changes keeps it actionable. |
-| Update mission status | `myte mission status --mission-ids "M001" --status todo|in_progress|done` | Project-key surface updates canonical mission status for active cards and refreshes local bootstrap + mission-ops by default. |
-| Archive mission | `myte mission archive --mission-ids "M001[,M002]" --reason "..."` | Project Owner or elevated delegate required. Sets `Archived`, removes cards from normal bootstrap/board state, writes mission activity, and refreshes local bootstrap + mission-ops by default. |
+| Suggest edit to existing mission | `myte suggestions create --file ./create.yml --confirm-write --approval-artifact ./create.yml` with `change_type: update` and `mission_id` | Creates or appends to an active review thread; live mission is unchanged until approval. |
+| Suggest new mission | `myte suggestions create --file ./create.yml --confirm-write --approval-artifact ./create.yml` with `change_type: create` | Requires `change_set.title` and `change_set.description`; creates a review thread only; the mission card is created only after approval. |
+| Revise a suggestion | `myte suggestions revise --file ./revise.yml --confirm-write --approval-artifact ./revise.yml` with `suggestion_id` | Adds another revision to the same thread. Do not include `change_type`. |
+| Review a suggestion | `myte suggestions review` with `review_action: approve|request_changes|reject` | Project Owner or elevated mission-review delegate required; no approval artifact required. Approval mutates/creates the mission once; reject archives the thread only; request_changes keeps it actionable. |
+| Update mission status | `myte mission status --mission-ids "M001" --status todo|in_progress|done` | Project-key surface updates canonical mission status for active cards; no approval artifact required; refreshes local bootstrap + mission-ops by default. |
+| Archive mission | `myte mission archive --mission-ids "M001[,M002]" --reason "..."` | Project Owner or elevated delegate required; no approval artifact required. Sets `Archived`, removes cards from normal bootstrap/board state, writes mission activity, and refreshes local bootstrap + mission-ops by default. |
 
 Create payloads:
 
@@ -171,18 +188,18 @@ Agent rule: never guess `suggestion_id`. If `mission-ops.yml` is missing or stal
 | `feedback edit` / `feedback refine` | Creates a local YAML proposal for title, description/body, priority, due date, tags, or notes. | Content changes go through owner-review membrane. |
 | `feedback assign` | Creates a local YAML proposal to change assignee. | Goes through review unless applied through owner-direct path. |
 | `feedback archive` | Creates a local YAML proposal to archive. | Archive is governed by backend owner/delegate capability. |
-| `feedback submit` | Sends a local proposal artifact to the backend as a review request. | Does not mutate live feedback before approval. |
-| `feedback revise` | Resubmits the original submitter's request after `request_changes`. | Only valid for the original submitter and `needs_changes` requests. |
+| `feedback submit` | Sends a local proposal artifact to the backend as a review request. | Requires `--confirm-write --approval-artifact <path>`; does not mutate live feedback before approval. |
+| `feedback revise` | Resubmits the original submitter's request after `request_changes`. | Requires `--confirm-write --approval-artifact <path>`; only valid for the original submitter and `needs_changes` requests. |
 | `feedback reviews` | Lists review requests or fetches one request by `--request-id`. | Read-only; response includes backend permissions. |
-| `feedback review` | Approves, rejects, requests changes, or cancels one review request, or a batch with `--request-ids`. | Backend restricts approval/review decisions to Project Owner or elevated delegate for Feedback scope; batch review uses one grouped notification path. |
-| `feedback move` | Moves a card or batch of cards across allowed board states directly with an audit event. | `--feedback-ids` sends one batch request. Blocked with `pending_feedback_review` while an active linked review request exists; governed states such as archive/reject/deploy/freeze remain backend-authorized. Project-key unarchive is not supported. |
-| `feedback comment` | Creates a text-only comment on one Feedback item. | Backend checks project-key access, owner/assigned permission, idempotency, and the 500,000-character content cap. Attachments remain web UI only. |
-| `feedback undo` | Reverses an audited board event when there is no conflict. | Backend validates event ownership/project scope and conflict state. |
+| `feedback review` | Approves, rejects, requests changes, or cancels one review request, or a batch with `--request-ids`. | No approval artifact required; backend restricts approval/review decisions to Project Owner or elevated delegate for Feedback scope; batch review uses one grouped notification path. |
+| `feedback move` | Moves a card or batch of cards across allowed board states directly with an audit event. | No approval artifact required. `--feedback-ids` sends one batch request. Blocked with `pending_feedback_review` while an active linked review request exists; governed states such as archive/reject/deploy/freeze remain backend-authorized. Project-key unarchive is not supported. |
+| `feedback comment` | Creates a text-only comment on one Feedback item. | Requires `--confirm-write --approval-artifact <path>`; backend checks project-key access, owner/assigned permission, idempotency, and the 500,000-character content cap. Attachments remain web UI only. |
+| `feedback undo` | Reverses an audited board event when there is no conflict. | No approval artifact required; backend validates event ownership/project scope and conflict state. |
 | `feedback prd-versions` | Lists retained PRD baselines/revisions for a feedback item. | Read-only; old S3 objects are retained by reference. |
 | `feedback prd-diff` | Fetches backend-generated text diff for PRD versions. | Read-only; backend controls version access. |
 | `feedback history` | Lists audited feedback board/refinement events. | Read-only; backend checks project access. |
 | `feedback validate` | Sends an artifact to backend validation without mutation. | Useful before submit or owner-direct apply. |
-| `feedback apply` | Applies an artifact through the owner-direct/emergency path. | Not the normal collaborator flow; normal flow is `submit` -> `review`. |
+| `feedback apply` | Applies an artifact through the owner-direct/emergency path. | No approval artifact required; not the normal collaborator flow; normal flow is `submit` -> `review`. |
 
 Canonical feedback lifecycle states are `frozen`, `todo`, `in_progress`, `in_review`, `completed`, `deployed`, `rejected`, and `archived`.
 
@@ -194,13 +211,16 @@ node ./scripts/feedback-live-full-harness.js --confirm-live --base-url https://a
 
 The harness creates five disposable `TEST` feedback items from markdown, verifies batch review and batch board movement, batch archives the disposable items, verifies normal `feedback-sync` excludes archived items, and verifies the project-key surface does not expose Feedback unarchive/restore.
 
-## Direct Project API Surface
-
-All routes use `Authorization: Bearer <MYTE_API_KEY>`. The CLI adds idempotency and client-session headers on mutation routes.
-
-Read/sync routes:
-
-- `GET /api/project-assistant/config`
+## Direct Project API Surface
+
+All routes use `Authorization: Bearer <MYTE_API_KEY>`. The CLI adds idempotency and client-session headers on mutation routes.
+
+`myte ai` is separate from this project-scoped surface. It uses `MYTEAI_API_KEY` and calls `POST https://api.myte.ai/v1/chat/completions`, or `${MYTEAI_API_BASE}/v1/chat/completions` when that base is configured.
+
+Read/sync routes:
+
+- `GET /api/project-assistant/query/<job_id>`
+- `GET /api/project-assistant/config`
 - `GET /api/project-assistant/bootstrap`
 - `GET /api/project-assistant/qaqc-sync`
 - `GET /api/project-assistant/feedback-sync`

package/cli.js

@@ -26,9 +26,9 @@ const DEFAULT_DIFF_LIMIT_CHARS = 500_000;
 const REMOVED_COMMAND_MESSAGES = {
   ask: "The `ask` alias has been removed. Use `myte query \"...\"`.",
   chat: "The `chat` command has been removed. Use repeated `myte query` calls instead.",
-  "create-prds": "The `create-prds` alias has been removed. Use `myte create-prd <file.md> [more.md ...]`.",
-  "add-prd": "The `add-prd` alias has been removed. Use `myte create-prd <file.md> [more.md ...]`.",
-  prd: "The `prd` alias has been removed. Use `myte create-prd <file.md> [more.md ...]`.",
+  "create-prds": "The `create-prds` alias has been removed. Use `myte create-prd <file.md> [more.md ...] --confirm-write --approval-artifact <path>`.",
+  "add-prd": "The `add-prd` alias has been removed. Use `myte create-prd <file.md> [more.md ...] --confirm-write --approval-artifact <path>`.",
+  prd: "The `prd` alias has been removed. Use `myte create-prd <file.md> [more.md ...] --confirm-write --approval-artifact <path>`.",
   "qaqc-status-update": "The `qaqc-status-update` command has been removed. Use `myte mission status --mission-ids \"M001,M002\" --status todo|in_progress|done`.",
   "mission-restore": "The project-key `myte mission restore` command has been removed. Restore archived missions from the Myte web archived missions board.",
 };
@@ -190,12 +190,12 @@ function printHelp() {
     "  myte mission archive --mission-ids \"M001[,M002...]\" [--reason \"...\"] [--no-sync] [--json]",
     "  myte sync-qaqc [--output-dir ./MyteCommandCenter] [--json]",
     "  myte suggestions sync [--output-dir ./MyteCommandCenter] [--json]",
-    "  myte suggestions create [--file ./payload.yml] [--no-sync] [--json]",
-    "  myte suggestions revise [--file ./payload.yml] [--no-sync] [--json]",
-    "  myte suggestions review [--file ./payload.yml] [--no-sync] [--json]",
-    "  myte update-team \"<content>\" [--json]",
-    "  myte update-owner --subject \"<text>\" [--body-markdown \"...\"] [--body-file ./update.md] [--json]",
-    "  myte update-client --subject \"<text>\" [--body-markdown \"...\"] [--body-file ./update.md] [--target-contact-ids <id1,id2>] [--json]",
+    "  myte suggestions create [--file ./payload.yml] --confirm-write --approval-artifact <path> [--no-sync] [--json]",
+    "  myte suggestions revise [--file ./payload.yml] --confirm-write --approval-artifact <path> [--no-sync] [--json]",
+    "  myte suggestions review [--file ./payload.yml] [--no-sync] [--json]",
+    "  myte update-team \"<content>\" --confirm-write --approval-artifact <path> [--json]",
+    "  myte update-owner --subject \"<text>\" [--body-markdown \"...\"] [--body-file ./update.md] --confirm-write --approval-artifact <path> [--json]",
+    "  myte update-client --subject \"<text>\" [--body-markdown \"...\"] [--body-file ./update.md] [--target-contact-ids <id1,id2>] --confirm-write --approval-artifact <path> [--json]",
     "  myte feedback-sync [--status <value>] [--source <value>] [--with-prd-text|--no-with-prd-text] [--output-dir ./MyteCommandCenter] [--json]",
     "  myte feedback get --feedback-id <id> [--json]",
     "  myte feedback history --feedback-id <id> [--limit 50] [--json]",
@@ -203,23 +203,23 @@ function printHelp() {
     "  myte feedback edit --feedback-id <id> [--title \"...\"] [--feedback-text \"...\"] [--priority High] [--reason \"...\"]",
     "  myte feedback assign --feedback-id <id> --user-id <id> [--reason \"...\"]",
     "  myte feedback archive --feedback-id <id> --reason \"...\"",
-    "  myte feedback submit --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml [--json]",
-    "  myte feedback revise --request-id <id> --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml [--json]",
+    "  myte feedback submit --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml --confirm-write --approval-artifact <path> [--json]",
+    "  myte feedback revise --request-id <id> --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml --confirm-write --approval-artifact <path> [--json]",
     "  myte feedback reviews [--status open|terminal|all] [--request-id <id>] [--json]",
     "  myte feedback review --request-id <id> --action approve|reject|request_changes|cancel [--reason \"...\"] [--json]",
     "  myte feedback review --request-ids \"<id1,id2>\" --action approve|reject|request_changes|cancel [--reason \"...\"] [--json]",
     "  myte feedback move --feedback-id <id> --to-state in_progress --from-state todo --reason \"...\" [--json]",
     "  myte feedback move --feedback-ids \"<id1,id2>\" --to-state in_progress --reason \"...\" [--json]",
-    "  myte feedback comment --feedback-id <id> --body \"...\" [--body-file ./comment.md] [--json]",
+    "  myte feedback comment --feedback-id <id> --body \"...\" [--body-file ./comment.md] --confirm-write --approval-artifact <path> [--json]",
     "  myte feedback undo --feedback-id <id> --event-id <id> --reason \"...\" [--json]",
     "  myte feedback prd-versions --feedback-id <id> [--json]",
     "  myte feedback prd-diff --feedback-id <id> --version-id <id> [--compare-to <id>] [--json]",
     "  myte feedback validate --file ./MyteCommandCenter/reviews/feedback/<id>-status.yml [--json]",
     "  myte feedback apply --file ./MyteCommandCenter/reviews/feedback/<id>-status.yml [--json]",
-    "  myte create-prd <file.md> [more.md ...] [--json] [--title \"...\"] [--description \"...\"]",
-    "  cat file.md | myte create-prd --stdin [--title \"...\"] [--description \"...\"]",
-    "  cat update.md | myte update-owner --stdin --subject \"Owner update\"",
-    "  cat update.md | myte update-client --stdin --subject \"Weekly client update\"",
+    "  myte create-prd <file.md> [more.md ...] --confirm-write --approval-artifact <path> [--json] [--title \"...\"] [--description \"...\"]",
+    "  cat file.md | myte create-prd --stdin --confirm-write --approval-artifact <path> [--title \"...\"] [--description \"...\"]",
+    "  cat update.md | myte update-owner --stdin --subject \"Owner update\" --confirm-write --approval-artifact ./update.md",
+    "  cat update.md | myte update-client --stdin --subject \"Weekly client update\" --confirm-write --approval-artifact ./update.md",
     "",
     "Run forms:",
     "  npm install myte   then npx myte query \"...\" --with-diff",
@@ -328,11 +328,23 @@ function printHelp() {
     "  - project-key API/CLI cannot unarchive archived Feedback; use the web archived Feedback view",
     "  - get/history read current feedback snapshots and audited event history through the project-key API",
     "  - prd-versions/prd-diff expose retained PRD versions and backend-generated text diffs",
-    "  - validate/apply send artifacts to /api/project-assistant/feedback/<id>/refinement/* for validation or owner-direct apply",
-    "  - The backend owns authorization, stale snapshot checks, allowed field/transition rules, and history",
-    "  - apply is idempotent and does not rewrite local feedback.yml; run feedback-sync after apply to refresh local state",
-    "",
-    "feedback action map:",
+    "  - validate/apply send artifacts to /api/project-assistant/feedback/<id>/refinement/* for validation or owner-direct apply",
+    "  - The backend owns authorization, stale snapshot checks, allowed field/transition rules, and history",
+    "  - apply is idempotent and does not rewrite local feedback.yml; run feedback-sync after apply to refresh local state",
+    "",
+    "approval artifact requirements:",
+    "  - Required: create-prd, update-team, update-owner, update-client, feedback submit/revise/comment, suggestions create/revise",
+    "  - Not required: run-qaqc, mission status/archive, suggestions review, feedback review/move/undo/apply",
+    "  - Never required: read/sync/query/validate commands, --print-context, --dry-run, and feedback local draft commands",
+    "  - For required actions, prepare a .md/.markdown/.yml/.yaml/.json artifact, show it to the user, then rerun with --confirm-write --approval-artifact <path>",
+    "  - In plain language, the artifact is the human-reviewed record of the exact write the agent is about to send; it is not a permission grant and does not bypass owner/delegate checks, idempotency, stale-state guards, validation, or audit",
+    "  - Minimum artifact contents: exact command; every target id or PRD item; complete proposed-change summary; reason/approval note; batch_count when one command sends multiple items",
+    "  - Mission edit/create batches use suggestions create/revise and must enumerate each item: update items include change_type: update, mission_id, and changed fields; create items include change_type: create, title, description, and acceptance details; revisions include suggestion_id and expected_revision",
+    "  - PRD batches use one create-prd fileA.md fileB.md ...; list each PRD file/title/client_ref and make batch_count match the number of PRDs",
+    "  - Feedback submit/revise/comment artifacts are usually the same YAML/markdown file being submitted; for inline text or stdin, use an approval memo with feedback_id/request_id and exact content",
+    "  - Team, owner, and client update artifacts should name the audience and include the exact message body or complete summary; client updates should include target contact ids when used",
+    "",
+    "feedback action map:",
     "  - feedback-sync: pull board/PRD context into MyteCommandCenter for IDE work",
     "  - get: read one feedback item's current server snapshot and snapshot_hash",
     "  - status/edit/assign/archive/refine: create reviewable local YAML artifacts; no live mutation",
@@ -392,8 +404,10 @@ function printHelp() {
     "  --no-with-prd-text    Skip PRD text download and write only feedback metadata/comment turns",
     "  --mission-ids <ids>   Comma-separated mission business ids for run-qaqc, mission status, or mission archive (quote multi-id values on PowerShell)",
     "  --reason <text>       Optional reason for governed mission archive or feedback changes",
-    "  --actor-scope <id>    Actor workspace key inside mission-ops.yml (defaults to machine-cwd slug)",
-    "  --wait                Poll batch status until terminal completion for run-qaqc",
+    "  --actor-scope <id>    Actor workspace key inside mission-ops.yml (defaults to machine-cwd slug)",
+    "  --confirm-write       Attach approval metadata for commands that require an approval artifact",
+    "  --approval-artifact   Local .md/.markdown/.yml/.yaml/.json approval artifact for gated write commands",
+    "  --wait                Poll batch status until terminal completion for run-qaqc",
     "  --sync                After run-qaqc completes, refresh local QAQC file",
     "  --force               Allow run-qaqc to bypass stale-state protection when supported",
     "  --no-sync             Skip automatic post-mutation sync for suggestions, missions, and feedback mutations",
@@ -406,33 +420,33 @@ function printHelp() {
     "  myte ai \"Return a JSON object with risks and next_steps\" --json-response",
     "  myte bootstrap",
     "  myte suggestions sync",
-    "  myte suggestions create",
-    "  myte suggestions revise --no-sync",
+    "  myte suggestions create --file ./suggestions/create.yml --confirm-write --approval-artifact ./suggestions/create.yml",
+    "  myte suggestions revise --file ./suggestions/revise.yml --confirm-write --approval-artifact ./suggestions/revise.yml --no-sync",
     "  myte suggestions review --file ./review.yml",
     "  myte run-qaqc --mission-ids \"M001,M002\" --wait --sync",
     "  myte mission status --mission-ids \"M001,M002\" --status done",
     "  myte mission archive --mission-ids \"M001\" --reason \"Duplicate disposable test mission\"",
     "  myte bootstrap --output-dir ./MyteCommandCenter",
     "  myte sync-qaqc",
-    "  myte update-team \"Backend deploy completed; QAQC rerun queued.\"",
-    "  myte update-owner --subject \"QAQC progress\" --body-file ./updates/owner.md",
-    "  myte update-client --subject \"Weekly client update\" --body-file ./updates/week-12.md",
+    "  myte update-team \"Backend deploy completed; QAQC rerun queued.\" --confirm-write --approval-artifact ./updates/team.md",
+    "  myte update-owner --subject \"QAQC progress\" --body-file ./updates/owner.md --confirm-write --approval-artifact ./updates/owner.md",
+    "  myte update-client --subject \"Weekly client update\" --body-file ./updates/week-12.md --confirm-write --approval-artifact ./updates/week-12.md",
     "  myte feedback-sync --json",
     "  myte feedback status --feedback-id 507f1f77bcf86cd799439011 --status in_review --reason \"Ready for owner review\"",
-    "  myte feedback submit --file ./MyteCommandCenter/reviews/feedback/507f1f77bcf86cd799439011-edit.yml --json",
+    "  myte feedback submit --file ./MyteCommandCenter/reviews/feedback/507f1f77bcf86cd799439011-edit.yml --confirm-write --approval-artifact ./MyteCommandCenter/reviews/feedback/507f1f77bcf86cd799439011-edit.yml --json",
     "  myte feedback reviews --status open --json",
     "  myte feedback review --request-id 507f1f77bcf86cd799439022 --action approve --reason \"Looks correct\" --json",
     "  myte feedback move --feedback-id 507f1f77bcf86cd799439011 --to-state in_progress --reason \"Started\" --json",
-    "  myte feedback comment --feedback-id 507f1f77bcf86cd799439011 --body \"Implementation notes are ready for review.\" --json",
+    "  myte feedback comment --feedback-id 507f1f77bcf86cd799439011 --body-file ./comments/implementation.md --confirm-write --approval-artifact ./comments/implementation.md --json",
     "  myte feedback validate --file ./MyteCommandCenter/reviews/feedback/507f1f77bcf86cd799439011-status.yml --json",
     "  myte feedback apply --file ./MyteCommandCenter/reviews/feedback/507f1f77bcf86cd799439011-status.yml --json",
-    "  myte suggestions create --file ./suggestions/create.yml",
-    "  myte suggestions revise",
+    "  myte suggestions create --file ./suggestions/create.yml --confirm-write --approval-artifact ./suggestions/create.yml",
+    "  myte suggestions revise --file ./suggestions/revise.yml --confirm-write --approval-artifact ./suggestions/revise.yml",
     "  myte suggestions review",
-    "  myte update-client --subject \"Weekly client update\" --body-markdown \"## Progress\\n- Login complete\" --target-contact-ids 507f1f77bcf86cd799439011,507f1f77bcf86cd799439012",
-    "  myte create-prd ./drafts/auth-prd.md --description \"Short card summary\"",
-    "  myte create-prd ./drafts/auth-prd.md ./drafts/billing-prd.md",
-    "  cat ./drafts/auth-prd.md | myte create-prd --stdin",
+    "  myte update-client --subject \"Weekly client update\" --body-markdown \"## Progress\\n- Login complete\" --target-contact-ids 507f1f77bcf86cd799439011,507f1f77bcf86cd799439012 --confirm-write --approval-artifact ./updates/week-12.md",
+    "  myte create-prd ./drafts/auth-prd.md --description \"Short card summary\" --confirm-write --approval-artifact ./drafts/auth-prd.md",
+    "  myte create-prd ./drafts/auth-prd.md ./drafts/billing-prd.md --confirm-write --approval-artifact ./drafts/prd-batch.md",
+    "  cat ./drafts/auth-prd.md | myte create-prd --stdin --confirm-write --approval-artifact ./drafts/auth-prd.md",
     "  myte config",
   ].join("\n");
   console.log(text);
@@ -2355,11 +2369,6 @@ async function runRunQaqc(args) {
   };
   const clientSessionId = firstNonEmptyString(args["client-session-id"], args.clientSessionId, args.client_session_id);
   if (clientSessionId) payload.client_session_id = clientSessionId;
-  payload = withWriteApproval(args, payload, {
-    artifactKind: "yaml",
-    targets: missionIds,
-    batchCount: missionIds.length > 1 ? missionIds.length : null,
-  });
   const idempotencyKey = resolveProjectMutationIdempotencyKey({
     args,
     operation: "run-qaqc",
@@ -2515,11 +2524,6 @@ async function runMissionStatus(args) {
   };
   const clientSessionId = firstNonEmptyString(args["client-session-id"], args.clientSessionId, args.client_session_id);
   if (clientSessionId) payload.client_session_id = clientSessionId;
-  payload = withWriteApproval(args, payload, {
-    artifactKind: "yaml",
-    targets: missionIds,
-    batchCount: missionIds.length > 1 ? missionIds.length : null,
-  });
   const idempotencyKey = resolveProjectMutationIdempotencyKey({
     args,
     operation: "mission-status-update",
@@ -2624,15 +2628,9 @@ async function runMissionArchiveCommand(args) {
   if (reason) payload.reason = reason;
   const clientSessionId = firstNonEmptyString(args["client-session-id"], args.clientSessionId, args.client_session_id);
   if (clientSessionId) payload.client_session_id = clientSessionId;
-  payload = withWriteApproval(args, payload, {
-    artifactKind: "yaml",
-    targets: missionIds,
-    batchCount: missionIds.length > 1 ? missionIds.length : null,
-  });
-
-  const operation = "mission-archive";
-  const idempotencyKey = resolveProjectMutationIdempotencyKey({
-    args,
+  const operation = "mission-archive";
+  const idempotencyKey = resolveProjectMutationIdempotencyKey({
+    args,
     operation,
     payload,
   });
@@ -3099,7 +3097,7 @@ function resolveWriteApprovalArtifact(args) {
   }
   const ext = path.extname(absPath).toLowerCase();
   if (![".md", ".markdown", ".yml", ".yaml", ".json"].includes(ext)) {
-    console.error("Approval artifact must be a local .md, .yml, .yaml, or .json file.");
+    console.error("Approval artifact must be a local .md, .markdown, .yml, .yaml, or .json file.");
     process.exit(1);
   }
   return { displayPath: String(artifactPath), absPath };
@@ -3109,8 +3107,20 @@ function approvalTargets(values) {
   return uniqueNormalizedStrings(Array.isArray(values) ? values : [values]);
 }
 
-function withWriteApproval(args, payload, { artifactKind = "yaml", targets = [], batchCount = null } = {}) {
+function hasWriteApprovalArtifactArg(args) {
+  return Boolean(firstNonEmptyString(
+    args["approval-artifact"],
+    args.approvalArtifact,
+    args.approval_artifact
+  ));
+}
+
+function withWriteApproval(args, payload, { artifactKind = "yaml", targets = [], batchCount = null, required = true } = {}) {
   const confirmed = Boolean(args["confirm-write"] || args.confirmWrite || args.confirm_write);
+  if (required && (!confirmed || !hasWriteApprovalArtifactArg(args))) {
+    console.error("Missing --confirm-write --approval-artifact <path> for this live Myte write.");
+    process.exit(1);
+  }
   if (!confirmed) return payload;
   const { displayPath } = resolveWriteApprovalArtifact(args);
   const nextPayload = { ...(payload || {}) };
@@ -3416,19 +3426,123 @@ function resolvePortableWorkspace(repoNames) {
   };
 }
 
-function resolveCommandCenterRoots(wrapperRoot, outputDir) {
-  const targetRoot = outputDir
-    ? path.resolve(process.cwd(), String(outputDir))
-    : path.join(wrapperRoot, "MyteCommandCenter");
-  return {
-    targetRoot,
-    dataRoot: path.join(targetRoot, "data"),
-  };
-}
-
-function pruneLegacyCommandCenterArtifacts(dataRoot, options = {}) {
-  const {
-    bootstrap = false,
+function resolveCommandCenterRoots(wrapperRoot, outputDir) {
+  const targetRoot = outputDir
+    ? path.resolve(process.cwd(), String(outputDir))
+    : path.join(wrapperRoot, "MyteCommandCenter");
+  return {
+    targetRoot,
+    dataRoot: path.join(targetRoot, "data"),
+  };
+}
+
+function buildAgentsMyteApiMarkdown() {
+  return ensureTrailingNewline([
+    "# AgentsMyteAPI",
+    "",
+    "This file is generated by `myte bootstrap` as contextual guidance for coding agents using a project-scoped Myte API key.",
+    "It does not grant permission, approve a write, or replace project authorization. Prefer the `myte` CLI over direct HTTP.",
+    "",
+    "## Auth And Discovery",
+    "",
+    "- Use `MYTE_API_KEY` or `MYTE_PROJECT_API_KEY` for `/api/project-assistant/*`.",
+    "- Default API base: `https://api.myte.dev/api`.",
+    "- Start with `myte config --json`, then `myte bootstrap --json`.",
+    "- Use local IDs from `MyteCommandCenter/data/missions/*.yml`, `data/mission-ops.yml`, and `data/feedback.yml`.",
+    "- `myte ai` is intentionally outside this project-scoped table. It uses `MYTEAI_API_KEY` and the Myte AI gateway, not `/api/project-assistant/*`.",
+    "",
+    "## Approval Artifact Rule",
+    "",
+    "Only the commands marked `required` below need `--confirm-write --approval-artifact <path>`.",
+    "Approval artifacts are local `.md`, `.markdown`, `.yml`, `.yaml`, or `.json` files that list the operation, exact target IDs, proposed change, and batch count when relevant.",
+    "The artifact is the human-reviewed record of the intended mutation. It does not grant permission, bypass owner/delegate checks, or replace idempotency; it gives the API enough evidence that a human approved this exact write payload.",
+    "",
+    "Minimum artifact contents for required actions:",
+    "",
+    "- `command`: the exact CLI command you plan to run.",
+    "- `targets`: every affected project, feedback, request, suggestion, mission, PRD file, client ref, or contact id.",
+    "- `proposed_change`: a complete summary of the text/status/content being sent.",
+    "- `batch_count`: required when the command sends more than one item in one API call.",
+    "- `reason` or `approval_note`: why the write is being sent now.",
+    "",
+    "Batch guidance:",
+    "",
+    "- Mission edit/create batches use `myte suggestions create` or `myte suggestions revise`; the artifact must list each item. For mission edits include `change_type: update`, the existing `mission_id`, and the changed fields. For new missions include `change_type: create`, the proposed title, description, and acceptance details. For revisions include each `suggestion_id` and expected revision.",
+    "- PRD batches use one `myte create-prd fileA.md fileB.md ...`; the artifact must list each PRD file/title/client ref. `batch_count` must match the number of PRD items.",
+    "- Feedback submit/revise/comment artifacts are usually the same YAML or markdown file being submitted. If the command uses inline text or stdin, create a separate approval memo that includes the feedback id or request id and the exact content.",
+    "- Team, owner, and client update artifacts should name the audience and include the exact message body or a complete summary; client updates should include target contact ids when used.",
+    "- `feedback review --request-ids`, `feedback move --feedback-ids`, `mission status --mission-ids`, `mission archive --mission-ids`, and `run-qaqc --mission-ids` are batched governed writes, but they are marked `no` below and should not receive approval artifact flags.",
+    "",
+    "Example approval artifact:",
+    "",
+    "```yaml",
+    "command: myte suggestions create --file ./mission-suggestions.yml --confirm-write --approval-artifact ./mission-suggestions-approval.yml",
+    "reason: Human approved this mission review batch after inspecting the proposed changes.",
+    "batch_count: 2",
+    "targets:",
+    "  - mission_id: M093",
+    "    change_type: update",
+    "    proposed_change: Mark acceptance criteria complete and clarify final QA note.",
+    "  - new_mission: Add deployment verification",
+    "    change_type: create",
+    "    proposed_change: Create a mission to verify deploy logs, smoke test, and rollback note.",
+    "```",
+    "",
+    "| Action | CLI shape | API route | Class | Artifact approval |",
+    "|---|---|---|---|---|",
+    "| Config | `myte config --json` | `GET /project-assistant/config` | read | no |",
+    "| Query | `myte query \"...\" --with-diff` | `POST /project-assistant/query`; polls `GET /project-assistant/query/<job_id>` when queued; `--with-diff` also reads `GET /project-assistant/config` | query job | no |",
+    "| Bootstrap | `myte bootstrap --json` | `GET /project-assistant/bootstrap` and `GET /project-assistant/suggestions` | local sync | no |",
+    "| QAQC sync | `myte sync-qaqc --json` | `GET /project-assistant/qaqc-sync` | local sync | no |",
+    "| Run QAQC | `myte run-qaqc --mission-ids \"M001,M002\" --wait --sync --json` | `POST /project-assistant/run-qaqc`; `--wait` polls `GET /project-assistant/run-qaqc/<batch_id>`; `--sync` reads `GET /project-assistant/qaqc-sync` | governed write | no |",
+    "| Mission status | `myte mission status --mission-ids \"M001\" --status done --json` | `POST /project-assistant/mission-status-update` | governed write | no |",
+    "| Mission archive | `myte mission archive --mission-ids \"M001\" --reason \"...\" --json` | `POST /project-assistant/mission-archive` | governed write | no |",
+    "| Suggestions sync | `myte suggestions sync --json` | `GET /project-assistant/suggestions` | local sync | no |",
+    "| Suggestions create | `myte suggestions create --file ./create.yml --confirm-write --approval-artifact ./create.yml --json` | `POST /project-assistant/suggestions` | review-thread write | required |",
+    "| Suggestions revise | `myte suggestions revise --file ./revise.yml --confirm-write --approval-artifact ./revise.yml --json` | `POST /project-assistant/suggestions/revise` | review-thread write | required |",
+    "| Suggestions review | `myte suggestions review --file ./review.yml --json` | `POST /project-assistant/suggestions/review` | governed review write | no |",
+    "| Feedback sync | `myte feedback-sync --json` | `GET /project-assistant/feedback-sync` | local sync | no |",
+    "| Feedback get | `myte feedback get --feedback-id <id> --json` | `GET /project-assistant/feedback/<id>` | read | no |",
+    "| Feedback history | `myte feedback history --feedback-id <id> --json` | `GET /project-assistant/feedback/<id>/events` | read | no |",
+    "| Feedback local drafts | `myte feedback status/edit/assign/archive/refine ...` | none | local artifact only | no |",
+    "| Feedback validate | `myte feedback validate --file ./review.yml --json` | `POST /project-assistant/feedback/<id>/refinement/validate` | validation | no |",
+    "| Feedback submit | `myte feedback submit --file ./review.yml --confirm-write --approval-artifact ./review.yml --json` | `POST /project-assistant/feedback/<id>/refinement/requests` | review-request write | required |",
+    "| Feedback revise | `myte feedback revise --request-id <id> --file ./review.yml --confirm-write --approval-artifact ./review.yml --json` | `POST /project-assistant/feedback-review-requests/<id>/revise` | review-request write | required |",
+    "| Feedback reviews | `myte feedback reviews [--status open/terminal/all] [--request-id <id>] --json` (`requests` alias) | `GET /project-assistant/feedback-review-requests` or `GET /project-assistant/feedback-review-requests/<id>` | read | no |",
+    "| Feedback review | `myte feedback review --request-id <id> --action approve/reject/request_changes/cancel [--reason \"...\"] --json` | `POST /project-assistant/feedback-review-requests/<id>/review`, `/request-changes`, or `/cancel` | governed review write | no |",
+    "| Feedback batch review | `myte feedback review --request-ids \"<id1,id2>\" --action approve/reject/request_changes/cancel --json` | `POST /project-assistant/feedback-review-requests/batch-review` | governed review write | no |",
+    "| Feedback move | `myte feedback move --feedback-id <id> --to-state in_progress --reason \"...\" --json` | `POST /project-assistant/feedback/<id>/board-move` | governed write | no |",
+    "| Feedback batch move | `myte feedback move --feedback-ids \"<id1,id2>\" --to-state in_progress --json` | `POST /project-assistant/feedback/batch-board-move` | governed write | no |",
+    "| Feedback comment | `myte feedback comment --feedback-id <id> --body-file ./comment.md --confirm-write --approval-artifact ./comment.md --json` | `POST /project-assistant/feedback/<id>/comments` | comment write | required |",
+    "| Feedback undo | `myte feedback undo --feedback-id <id> --event-id <id> --reason \"...\" --json` | `POST /project-assistant/feedback/<id>/events/<event_id>/undo` | governed write | no |",
+    "| Feedback PRD versions | `myte feedback prd-versions --feedback-id <id> --json` | `GET /project-assistant/feedback/<id>/prd/versions` | read | no |",
+    "| Feedback PRD diff | `myte feedback prd-diff --feedback-id <id> --version-id <id>` | `GET /project-assistant/feedback/<id>/prd/versions/<version_id>/diff` | read | no |",
+    "| Feedback apply | `myte feedback apply --file ./review.yml --json` | `POST /project-assistant/feedback/<id>/refinement/apply` | governed write | no |",
+    "| Create PRD | `myte create-prd ./prd.md --confirm-write --approval-artifact ./prd.md --json` | `POST /project-assistant/create-prd` | PRD write | required |",
+    "| Batch create PRDs | `myte create-prd ./a.md ./b.md --confirm-write --approval-artifact ./approval.md --json` | `POST /project-assistant/create-prds` | PRD write | required |",
+    "| Team update | `myte update-team \"...\" --confirm-write --approval-artifact ./team.md --json` | `POST /project-assistant/project-comment` | project comment | required |",
+    "| Owner update | `myte update-owner --subject \"...\" --body-file ./owner.md --confirm-write --approval-artifact ./owner.md --json` | `POST /project-assistant/update-owner` | owner email | required |",
+    "| Client update | `myte update-client --subject \"...\" --body-file ./client.md --confirm-write --approval-artifact ./client.md --json` | `POST /project-assistant/client-update-drafts` | client draft | required |",
+    "",
+    "## Agent Rules",
+    "",
+    "- For `required` actions, draft the artifact, show it to the user, get explicit approval, then rerun with the approval flags.",
+    "- For `no` actions, do not add approval flags. The API still enforces key binding, project permissions, idempotency, stale-state checks, and route validation.",
+    "- For local draft actions, inspect the generated YAML before submitting or applying it.",
+    "- Use `--print-context` or `--dry-run` where available to inspect payloads without sending a write.",
+  ].join("\n"));
+}
+
+function writeAgentsMyteApiGuide({ wrapperRoot, outputDir }) {
+  const { targetRoot } = resolveCommandCenterRoots(wrapperRoot, outputDir);
+  const guidePath = path.join(targetRoot, "AgentsMyteAPI.md");
+  writeTextFile(guidePath, buildAgentsMyteApiMarkdown());
+  return guidePath;
+}
+
+function pruneLegacyCommandCenterArtifacts(dataRoot, options = {}) {
+  const {
+    bootstrap = false,
     qaqc = false,
     feedback = false,
     missionOps = false,
@@ -3506,11 +3620,12 @@ function writeBootstrapSnapshot({ snapshot, wrapperRoot, outputDir }) {
     writeYamlFile(path.join(missionsDir, `${missionPathId}.yml`), mission);
   });
 
-  if (snapshot.project && typeof snapshot.project === "object") {
-    writeYamlFile(path.join(dataRoot, "project.yml"), scrubBootstrapValue(snapshot.project));
-  }
-
-  const manifest = {
+  if (snapshot.project && typeof snapshot.project === "object") {
+    writeYamlFile(path.join(dataRoot, "project.yml"), scrubBootstrapValue(snapshot.project));
+  }
+  const agentsMyteApiPath = writeAgentsMyteApiGuide({ wrapperRoot, outputDir });
+
+  const manifest = {
     schema_version: snapshot.schema_version || 1,
     generated_at: snapshot.generated_at || null,
     snapshot_hash: snapshot.snapshot_hash || null,
@@ -3523,12 +3638,13 @@ function writeBootstrapSnapshot({ snapshot, wrapperRoot, outputDir }) {
       missions: missions.length,
     },
   };
-  return {
-    targetRoot,
-    dataRoot,
-    manifest,
-  };
-}
+  return {
+    targetRoot,
+    dataRoot,
+    agentsMyteApiPath,
+    manifest,
+  };
+}
 
 function writeQaqcSnapshot({ snapshot, wrapperRoot, outputDir }) {
   const { targetRoot, dataRoot } = resolveCommandCenterRoots(wrapperRoot, outputDir);
@@ -4821,10 +4937,11 @@ async function runBootstrap(args) {
     return;
   }
 
-  const writeResult = writeBootstrapSnapshot({ snapshot, wrapperRoot, outputDir });
-  summary.data_root = writeResult.dataRoot;
-
-  if (includeSuggestions) {
+  const writeResult = writeBootstrapSnapshot({ snapshot, wrapperRoot, outputDir });
+  summary.data_root = writeResult.dataRoot;
+  summary.agents_myte_api_path = writeResult.agentsMyteApiPath;
+
+  if (includeSuggestions) {
     let missionOpsSnapshot;
     try {
       missionOpsSnapshot = await fetchSuggestionsSyncSnapshot({ apiBase, key, timeoutMs, actorScope });
@@ -4855,9 +4972,10 @@ async function runBootstrap(args) {
   console.log(`Output root: ${summary.output_root}`);
   console.log(`Configured repos: ${summary.repo_names.join(", ") || "(none)"}`);
   console.log(`Found locally: ${summary.local.found.join(", ") || "(none)"}`);
-  if (summary.local.missing.length) console.log(`Missing locally: ${summary.local.missing.join(", ")}`);
-  console.log(`Wrote: phases=${summary.counts.phases}, epics=${summary.counts.epics}, stories=${summary.counts.stories}, missions=${summary.counts.missions}`);
-  if (summary.mission_ops?.included) {
+  if (summary.local.missing.length) console.log(`Missing locally: ${summary.local.missing.join(", ")}`);
+  console.log(`Wrote: phases=${summary.counts.phases}, epics=${summary.counts.epics}, stories=${summary.counts.stories}, missions=${summary.counts.missions}`);
+  if (summary.agents_myte_api_path) console.log(`Wrote AgentsMyteAPI: ${summary.agents_myte_api_path}`);
+  if (summary.mission_ops?.included) {
     console.log(`Wrote mission ops: total_threads=${summary.mission_ops.total_threads}, actionable_threads=${summary.mission_ops.actionable_threads}`);
   } else {
     console.log("Skipped mission ops sync.");
@@ -5210,15 +5328,9 @@ async function runFeedbackValidateOrApply(args, mode) {
     args.client_session_id,
     payload.client_session_id
   );
-  if (mode === "apply") {
-    payload = withWriteApproval(args, payload, {
-      artifactKind: "yaml",
-      targets: [feedbackId],
-    });
-  }
   const idempotencyKey = mode === "apply"
-    ? resolveProjectMutationIdempotencyKey({
-        args,
+    ? resolveProjectMutationIdempotencyKey({
+        args,
         operation: `feedback_refinement_apply:${feedbackId}`,
         payload,
       })
@@ -5576,13 +5688,8 @@ async function runFeedbackReviewDecision(args) {
       action,
       reason: reason || undefined,
     };
-    payload = withWriteApproval(args, payload, {
-      artifactKind: "yaml",
-      targets: items.map((item) => item.request_id || item.id).filter(Boolean),
-      batchCount: items.length,
-    });
     const timeoutMs = resolveTimeoutMs(args);
-    const apiBase = resolveApiBase(args);
+    const apiBase = resolveApiBase(args);
     const clientSessionId = firstNonEmptyString(args["client-session-id"], args.clientSessionId, args.client_session_id, payload.client_session_id);
     const idempotencyKey = resolveProjectMutationIdempotencyKey({
       args,
@@ -5639,12 +5746,8 @@ async function runFeedbackReviewDecision(args) {
     process.exit(1);
   }
   const endpointAction = action === "request_changes" ? "request-changes" : action === "cancel" ? "cancel" : "review";
-  payload = withWriteApproval(args, payload, {
-    artifactKind: "yaml",
-    targets: [requestId],
-  });
   const timeoutMs = resolveTimeoutMs(args);
-  const apiBase = resolveApiBase(args);
+  const apiBase = resolveApiBase(args);
   const clientSessionId = firstNonEmptyString(args["client-session-id"], args.clientSessionId, args.client_session_id, payload.client_session_id);
   const operationAction = action === "request_changes" ? "request_changes" : action;
   const idempotencyKey = resolveProjectMutationIdempotencyKey({
@@ -5717,14 +5820,9 @@ async function runFeedbackMove(args) {
     }
     const batchId = firstNonEmptyString(args["batch-id"], args.batchId, args.batch_id);
     if (batchId) payload.batch_id = batchId;
-    payload = withWriteApproval(args, payload, {
-      artifactKind: "yaml",
-      targets: feedbackIds,
-      batchCount: feedbackIds.length,
-    });
     const idempotencyKey = resolveProjectMutationIdempotencyKey({
-      args,
-      operation: `feedback_board_batch_move:${toState}:${feedbackIds.join(",")}`,
+      args,
+      operation: `feedback_board_batch_move:${toState}:${feedbackIds.join(",")}`,
       payload,
     });
     let data;
@@ -5758,13 +5856,9 @@ async function runFeedbackMove(args) {
   }
 
   payload.from_state = fromState;
-  payload = withWriteApproval(args, payload, {
-    artifactKind: "yaml",
-    targets: [feedbackId],
-  });
   const idempotencyKey = resolveProjectMutationIdempotencyKey({
-    args,
-    operation: `feedback_board_move:${feedbackId}`,
+    args,
+    operation: `feedback_board_move:${feedbackId}`,
     payload,
   });
 
@@ -5901,13 +5995,9 @@ async function runFeedbackUndo(args) {
   const timeoutMs = resolveTimeoutMs(args);
   const apiBase = resolveApiBase(args);
   const clientSessionId = firstNonEmptyString(args["client-session-id"], args.clientSessionId, args.client_session_id);
-  payload = withWriteApproval(args, payload, {
-    artifactKind: "yaml",
-    targets: [feedbackId, eventId],
-  });
   const idempotencyKey = resolveProjectMutationIdempotencyKey({
-    args,
-    operation: `feedback_event_undo:${feedbackId}:${eventId}`,
+    args,
+    operation: `feedback_event_undo:${feedbackId}:${eventId}`,
     payload,
   });
 
@@ -6213,11 +6303,13 @@ async function buildSuggestionsMutationContext(args, mode) {
     validateSuggestionsRevisePayload(payload);
   }
   const items = Array.isArray(payload?.items) ? payload.items : [];
-  payload = withWriteApproval(args, payload, {
-    artifactKind: "yaml",
-    targets: suggestionWriteTargets(items),
-    batchCount: items.length > 1 ? items.length : null,
-  });
+  if (mode === "create" || mode === "revise") {
+    payload = withWriteApproval(args, payload, {
+      artifactKind: "yaml",
+      targets: suggestionWriteTargets(items),
+      batchCount: items.length > 1 ? items.length : null,
+    });
+  }
   const idempotencyKey = resolveSuggestionsIdempotencyKey({
     args,
     mode,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mytegroupinc/myte-core",
-  "version": "0.0.46",
+  "version": "0.0.47",
   "description": "Myte CLI core implementation.",
   "type": "commonjs",
   "main": "cli.js",