(CODUX-218) Synchronize update parsing documentation

[numnx]

🧩 Task: Synchronize update parsing documentation

Automated task PR opened by Code UX for T03.

📋 Summary

Sprint: Sprint 218 · Fix automatic agent update parsing · Task: T03

Harden automatic agent-update response parsing while preserving strict payload validation, retry behavior, non-mutating failures, and synchronized documentation.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.6-sol

⏱️ Timing

Started	2026-07-13 14:38:23 UTC
Finished	2026-07-13 14:42:58 UTC
Duration	4m 35s

📊 Token Usage

Metric	Value
Input tokens	82,564
Cached input tokens	911,616
Output tokens	10,857
Total tokens	1,005,037
Invocations	1
Tool calls	18
Active time	4m 4s

Included usage estimate (subscription/local login): $1.19

✅ QA Review

⏳ QA review runs after this PR is opened. Check the task card in the dashboard for the outcome once it lands.

📝 Full Task Prompt

## Objective
Bring current automatic base-agent update documentation in line with the repaired invocation parsing behavior and its failure guarantees.

## Scope
- `docs/architecture/agent-preset-foundation.md`
- `docs/architecture/agent-sync-and-planning-agent.md`
- `docs/dashboard/dashboard-guide.md`
- `docs-web/user/dashboard/agents.md`
- `docs-web/content/docs/user-dashboard-agents.mdx`
- `docs-web/developer/http-api.md`
- `docs-web/content/docs/developer-http-api.mdx`

## Implementation Requirements
1. Explain that the provider response may contain supported JSON presentation noise such as markdown fencing, surrounding text, or provider envelopes, while Code UX still requires exactly one non-empty `instructionMarkdown` property after extraction.
2. Document that parsing errors continue through the structured same-session retry path and that malformed, destructive, stale, unsupported-provider, or provider-failure cases leave the preset and bundled revision unchanged.
3. Keep the documented roles, endpoints, planning-route selection, execution type `agent_base_update`, line-preservation rule, and instruction-only mutation contract accurate across canonical and public mirrors.
4. Remove or revise wording that implies every successful provider response must be physically raw JSON when that wording describes the server parser rather than the prompt contract.

## Constraints
- Documentation-only changes in this task; do not introduce a new page, endpoint, setting, migration, or public protocol shape.
- Keep the scope limited to automatic base-agent updates and avoid changing general planning or provider documentation.
- Preserve project-name privacy and the repository’s canonical `docs/` plus public `docs-web/` synchronization policy.

## Verification
- Run `git diff --check`.
- Use `rg` to confirm the affected pages consistently describe tolerant extraction, strict payload validation, retry behavior, and non-mutating failure handling.
- Confirm both Markdown and MDX public mirrors agree with the canonical documentation.

🌿 Branch Info

Base: feature/CODUX-218-fix-automatic-agent-update-parsing
Head: task/feature-codux-21-t03-codex-39b4dcd7-mrjbutw3

---

🤖 Generated by Code UX