@open-agent-toolkit/cli 0.3.23 → 0.3.25

package/assets/skills/oat-docs-apply/SKILL.md

@@ -5,7 +5,7 @@ disable-model-invocation: true
 user-invocable: true
 allowed-tools: Read, Write, Edit, Bash(git:*), Bash(gh:*), Bash(oat:*), Bash(pnpm:*), Bash(bash:*), Bash(jq:*), Bash(mkdir:*), Bash(date:*), Bash(echo:*), Bash(cd:*), Bash(pwd:*), Glob, Grep, AskUserQuestion
 metadata:
-  version: '1.4.4'
+  version: '1.4.6'
 ---
 
 # Docs Apply
@@ -33,12 +33,12 @@ Before a parent-branch commit, verify `oat internal commit-paths --help` succeed
 
 - No unapproved documentation changes.
 - No branch creation before the recommendation plan is reviewed.
-- No changes outside the documentation scope except deterministic nav sync and tracking updates.
+- No changes outside the documentation scope except the approved IA record/config mirrors, owner-authorized nav sync, tracking updates, and the individually approved tooling-update carve-out below.
 
 **ALLOWED Activities:**
 
 - Reading analysis artifacts and the current docs surface.
-- Creating or updating docs files and `mkdocs.yml` when approved. Fumadocs `meta.json` files change only through `oat docs nav sync`.
+- Creating or updating docs files and hand-authored navigation when approved. Nav-sync-owned navigation changes only through `oat docs nav sync`; undeclared ownership blocks regeneration.
 - Running `oat docs nav sync` after approved structural changes.
 - Creating branches, commits, and optional PRs.
 
@@ -93,7 +93,13 @@ When executing this skill, provide lightweight progress feedback so the user can
 
 ### Step 0: Intake - Find Analysis Artifact
 
-Locate the most recent docs analysis artifact:
+The one input is an **analysis artifact path plus approved recommendation IDs**.
+Accept an explicitly supplied artifact; when none is supplied, offer the newest
+artifact below and confirm that it is the reviewed input. Never silently switch
+to a newer artifact after approval. IDs identify recommendations within that
+artifact, remain stable through artifact review, and are never reassigned.
+
+Locate a candidate when no artifact path was supplied:
 
 ```bash
 ls -t .oat/repo/analysis/docs-*.md 2>/dev/null | head -1
@@ -103,6 +109,8 @@ If none exists, stop and instruct the user to run `oat-docs-analyze`.
 
 Validate that each recommendation in the artifact includes:
 
+- a unique stable ID (for example `R-001`)
+- `approval: explicit | default`
 - evidence
 - confidence
 - disclosure
@@ -158,9 +166,19 @@ For review-mode and follow-up decisions, use host-aware prompting:
 
 If the user chooses `apply all`:
 
-- confirm the full plan
-- capture any global notes that apply across the whole plan
-- treat all non-blocked recommendations as approved unless the user names exceptions
+- confirm the full plan and capture global notes
+- approve only non-blocked `approval: default` recommendations, excluding named exceptions
+- Blanket approval never approves an `approval: explicit` recommendation.
+- Ask for individual approval by recommendation ID for each explicit item. A
+  restructure block always needs its own approval, including its full map and
+  old-URL plan; approving a different block does not approve it.
+
+In unattended mode, skip every explicit recommendation even when an input list
+names its ID; report `explicit_requires_interactive_approval` in the structured
+result. Never interpret automation configuration or `apply all` as individual
+approval. Missing/unknown approval classes or duplicate/unknown IDs block intake.
+The approved-ID list is captured at this approval step, not inferred from prose.
+An input list alone does not prove individual approval for an explicit item.
 
 If the user chooses `apply interactively`, ask for each recommendation:
 
@@ -174,11 +192,12 @@ If the user chooses `discuss`, answer questions, revise the plan if needed, and
 - `apply interactively`
 - `discuss`
 
-If all recommendations are skipped, stop without changing files.
+If all recommendations are skipped, emit the structured result with reasons and stop without changing files.
 
 Build an `APPLIED_PLAN_DETAILS` block from approved or modified recommendations with:
 
 - recommendation id
+- approval class and individual approval evidence when required
 - action
 - target path
 - disclosure
@@ -200,6 +219,24 @@ If branch creation fails because of unrelated local changes, ask the user to res
 
 ### Step 4: Apply Approved Changes
 
+Independently probe each exact `authoring-docs/SKILL.md` in order:
+`${SKILL_DIR}/..` from the loaded skill (`SKILL_DIR` is the absolute directory
+containing that loaded `SKILL.md`), `${HOME}/.agents/skills`, then
+`<repo-root>/.agents/skills`. Bind the first matching `authoring-docs` directory
+once as `AUTHORING_DOCS_ROOT`; load `${AUTHORING_DOCS_ROOT}/SKILL.md` and use
+that same root for every authoring-docs reference and script, never ambient
+discovery. If none is found, name `authoring-docs`, stop this handoff, and give
+the intended-scope recovery command: `oat tools install docs --scope <user|project>`
+or `oat tools update --pack docs --scope <user|project>`.
+
+Before content actions, use its page-purpose, landing, placement and five-axis IA
+method within the approved recommendation scope. Carry the analysis artifact's ordered guidance
+locators/provenance into the apply plan; do not silently re-resolve different
+sources. Verify cited inputs still exist and remain read-only outside the repo.
+Local AGENTS/contributing rules stay authoritative; a conflict is `ask_user`
+and blocks that recommendation pending a fresh analysis/user decision. Cite
+sources without copying private contents.
+
 Before the first approved write, initialize `OWNED_OUTPUT_FILES=()`. Append
 each exact successfully created, modified or removed path at that write,
 including both names of a rename and any generated navigation/index file this
@@ -217,10 +254,87 @@ For each approved recommendation:
    - `omit` -> do not encode the item in the docs change
    - `ask_user` -> require explicit user confirmation before writing
 
+#### Record an accepted IA
+
+Only an approved `record-ia` recommendation authorizes persistence. Before any
+PJM/decision write run `oat pjm doctor --json` in the target repo and inspect
+`adoption.state`; absent/partial adoption routes to `oat pjm init` before the
+record, never silently writes an unmanaged decision. Read the target's
+`.oat/repo/AGENTS.md`, decision conventions and existing decision index; update
+an existing matching record rather than duplicate it. Create a new record with
+`oat decision new "Documentation information architecture" --status accepted
+--context "<approved evidence>"` and its supported `--decision`/`--consequences` options
+(check `--help`). The command owns index generation; never hand-edit the index.
+
+Write a short `## Information architecture` section with tracks, organizing
+principle per track, placement rules and verification overlay. For Fumadocs and
+MkDocs put it in the docs-app `AGENTS.md`, preserving existing guidance. For
+Markdown put it in the contributing page; create no docs-root `AGENTS.md`.
+Link the decision and authored section reciprocally. They remain authoritative;
+a conflict with config becomes `ask_user`, never a config-driven rewrite.
+
+Mirror the accepted record using shared repo config only:
+`oat config set documentation.ia '<JSON>'`, with exactly `{preset, decision,
+tracks?: [{path, principle}], verification?: 'triad'|'agent-only'|'none'}`.
+`decision` is repo-relative; preserve guidance and unrelated config. For a
+framework surface, separately record the operator's approved sidebar owner via
+`oat config set documentation.navOwner nav-sync` or `hand-authored`. Missing
+ownership stays undeclared and blocks automatic regeneration. Markdown ignores
+navOwner and never runs nav sync. New-scaffold default ownership and preset
+materialization are not implemented by this persistence step.
+
+#### Restructure one approved block
+
+`restructure` requires `approval: explicit` and one individual approval per
+block before any move. Use the apply-plan block: source→destination map, source
+and destination parent Contents edits, grep-derived inbound references (including
+relative links, anchors and assets), exact rewrite list, and old-URL recovery.
+Search the whole repo for each old path/basename with `rg`; resolve relative
+references from their original file and check them again from their new location.
+Keep links to moved headings working. Do not treat search hits in examples or
+unrelated same-name files as automatic rewrites.
+
+Choose recovery supported by the actual deployment: Next static export does
+not support Next config redirects (see [Next static-export unsupported features](https://nextjs.org/docs/app/guides/static-exports#unsupported-features)).
+Use an authored stub at the old route with a relative pointer, or an approved
+archive pointer; a redirect requires verified framework/host support and stays
+manual when it needs app/host config. Never edit `not-found.tsx` through this
+carve-out. Retired pages retain a stub/archive pointer and a parent Contents
+update, never a silent delete. Preserve stub routes in the approved reader map
+where the framework needs them to build.
+
+Apply one block as one exact-path implementation commit; do not combine it with
+another block. Validate all rewritten inbound links and old URLs under the
+actual base path. With `navOwner: nav-sync`, run nav sync then nav sync --check
+with the explicit app target. With `hand-authored`, update approved hand-authored
+navigation and compare membership/order against Contents read-only; never run a
+writing nav sync. With undeclared ownership, report `ask_user` before navigation
+writes. Markdown checks files/Contents/links only. Re-run `oat-docs-analyze`
+after each block, preserving residual findings instead of claiming a clean run.
+
+#### Individually approved tooling update
+
+A `tooling-update` recommendation has `approval: explicit`. Even with individual
+approval, its out-of-Markdown allowance is only these three operations:
+
+1. Bump the docs app's existing `@open-agent-toolkit/docs-*` dependencies to the
+   bundled versions using the artifact's exact upgrade command (preserve dependency
+   section and package manager; include its resulting lockfile only). Never downgrade
+   an installed version: `ahead` or `unverified` requires CLI selection/update or
+   manual verification before re-analysis, not a docs-package tooling update.
+2. Run `oat docs migrate --docs-dir <authored-root> --apply` only for its currently
+   supported admonition conversions and injected frontmatter; inspect the diff.
+3. Run the docs build verifier from the app's existing scripts.
+
+Scaffold changes the CLI cannot make (app config, routes, package scripts) are
+`manual`: report the required change and ID without editing those files. This
+allowance does not permit application dependencies, host settings, arbitrary
+migrations or an app-shell rebuild. Other out-of-scope prohibitions remain.
+
 When approved actions involve docs app creation or nav updates:
 
 - Use `oat docs init` for scaffolding when appropriate.
-- Use `oat docs nav sync` instead of manually editing nav when the CLI helper can generate it. In Fumadocs apps it writes strict `meta.json` files and reports pages no `## Contents` map lists (`unlisted` in `--json`); resolve a reported page through an approved `## Contents` change, never by hand-editing `meta.json`.
+- Use `oat docs nav sync` instead of manually editing nav only when recorded `navOwner: nav-sync` authorizes it. In Fumadocs apps it writes strict `meta.json` files and reports pages no `## Contents` map lists (`unlisted` in `--json`); resolve a reported page through an approved `## Contents` change, never by hand-editing `meta.json`.
 
 Negative rules:
 
@@ -243,7 +357,7 @@ full configured content tree; keep the authored config index unchanged.
 For framework apps, discover actual scripts and run the smallest relevant
 verification set based on what changed; these examples apply only when present:
 
-- `oat docs nav sync`
+- `oat docs nav sync --target-dir <docs-app>` then `--check` only for `nav-sync` ownership; hand-authored/undeclared navigation gets read-only Contents membership/order comparison
 - `pnpm --dir <docs-app> docs:lint` (no-op when no linter is configured)
 - `pnpm --dir <docs-app> docs:format:check`
 - `pnpm --dir <docs-app> docs:build`
@@ -252,7 +366,7 @@ If no docs app exists yet, use file-level verification and confirm the structura
 
 ### Step 6: Commit and PR
 
-Commit the approved changes:
+Commit the approved changes (for restructure, repeat with one retained identity and exact path list per approved block; exclude already committed blocks from any final aggregate commit and skip an empty aggregate):
 
 ```bash
 OWNED_COMMIT_PATHS=("${OWNED_OUTPUT_FILES[@]}")
@@ -326,6 +440,29 @@ PR creation failed. To create manually:
 
 ### Step 7: Update Tracking and Output Summary
 
+Always emit this structured result, including no-op/unattended runs. Each input
+recommendation ID appears in exactly one outcome; failed verification is a
+failure, never an applied success. Unsupported scaffold work is skipped with
+reason `manual` and its required change. Include individual approval evidence
+in the plan, not invented in this result.
+
+```json
+{
+  "analysisArtifact": ".oat/repo/analysis/docs-example.md",
+  "approvedRecommendationIds": ["R-001"],
+  "applied": ["R-001"],
+  "skipped": [
+    { "id": "R-002", "reason": "explicit_requires_interactive_approval" }
+  ],
+  "failed": []
+}
+```
+
+Failed entries use `{ "id": "R-003", "reason": "<verification/error>" }`.
+Report partial writes and stop on a failure; never continue by widening scope.
+
+### Tracking and summary
+
 Update shared tracking:
 
 ```bash

package/assets/skills/oat-docs-apply/references/apply-plan-template.md

@@ -12,11 +12,20 @@ oat_docs_target: { docs-target-path }
 **Source Analysis:** `{analysis-artifact-path}`
 **Docs Target:** `{docs-target-path}`
 
+## Guidance provenance
+
+- Analysis-selected IA sources, in order: {locators + provenance}
+- Local authority: {AGENTS/contributing citations}
+- Read-only sources verified: {resolved entries or blocked recommendation IDs}
+- Conflicts: {ask_user disposition or none}
+
+Keep the analysis selection; do not copy private contents or invent missing evidence.
+
 ## Instructions
 
 Review the full recommendation set first, then choose a review mode:
 
-- **apply all** — approve the full set as presented
+- **apply all** — approve non-blocked default items; explicit items require individual approval by ID
 - **apply interactively** — review recommendation by recommendation
 - **discuss** — pause to talk through the plan before approving
 
@@ -32,19 +41,21 @@ blocked pending a fresh analysis rather than guessed.
 
 ## Recommendations
 
-### {N}. {Action}: `{target-path}`
-
-| Field        | Value                                                             |
-| ------------ | ----------------------------------------------------------------- |
-| Action       | {create / update / move / scaffold / sync-nav}                    |
-| Target       | `{target-path}`                                                   |
-| Rationale    | {why this recommendation exists}                                  |
-| Source       | {finding # / contract gap / nav issue}                            |
-| Evidence     | {exact file refs / config / docs that justify the recommendation} |
-| Confidence   | {high / medium / low}                                             |
-| Disclosure   | {inline / link_only / omit / ask_user}                            |
-| Link Targets | {path or URL when link_only; otherwise N/A}                       |
-| Helper       | `oat docs nav sync` / `oat docs init` / `manual edit`             |
+### {R-NNN}. {Action}: `{target-path}`
+
+| Field        | Value                                                                                              |
+| ------------ | -------------------------------------------------------------------------------------------------- |
+| ID           | {R-NNN; stable within the source artifact}                                                         |
+| approval     | {explicit / default; never inferred from blanket consent}                                          |
+| Action       | {create / update / move / scaffold / sync-nav / record-ia / restructure / tooling-update / manual} |
+| Target       | `{target-path}`                                                                                    |
+| Rationale    | {why this recommendation exists}                                                                   |
+| Source       | {finding # / contract gap / nav issue}                                                             |
+| Evidence     | {exact file refs / config / docs that justify the recommendation}                                  |
+| Confidence   | {high / medium / low}                                                                              |
+| Disclosure   | {inline / link_only / omit / ask_user}                                                             |
+| Link Targets | {path or URL when link_only; otherwise N/A}                                                        |
+| Helper       | `oat docs nav sync` / `oat docs init` / `manual edit`                                              |
 
 **Context:** {1-2 sentences}
 
@@ -55,6 +66,29 @@ blocked pending a fresh analysis rather than guessed.
 
 {Repeat for each recommendation}
 
+## Restructure block (one individually approved ID, one exact-path commit)
+
+- ID / individual approval evidence: {R-NNN / operator choice, or pending}
+- Source → destination map: {every moved/retired page}
+- Parent Contents edits: {source and destination indexes}
+- Grep-derived inbound rewrites: {command + referring file:line + old/new link,
+  including anchors/assets and rewritten links inside moved pages}
+- Old-URL strategy: {verified host redirect, authored stub, or archive pointer;
+  static export: no assumed Next redirects}
+- Retired-page recovery: {retained stub/archive pointer + parent Contents entry}
+- Sidebar owner: {nav-sync / hand-authored / undeclared; Markdown: ignored}
+- Verification: {nav-sync write then --check, or read-only membership/order
+  comparison; file/link checks; actual base-path old URL; analyze rerun}
+- Exact owned files and commit identity: {list including both rename sides}
+
+## IA recording / tooling limits
+
+- Record IA: {adoption.state from target pjm doctor; decision command/path;
+  framework AGENTS or Markdown contributing section; shared mirror JSON}
+- Tooling update: {individually approved ID; exact docs-app docs-\* upgrade
+  command; supported migrate conversions; existing build verifier}
+- Unsupported app config/routes/scripts: {manual required changes; no edits}
+
 ## Summary of Actions
 
 | #   | Action                                 | Target   | Disclosure                       | Decision                                                 |
@@ -64,6 +98,25 @@ blocked pending a fresh analysis rather than guessed.
 
 **Total:** {N} approved, {N} modified, {N} skipped
 
+## Structured result
+
+```json
+{
+  "analysisArtifact": "{path}",
+  "approvedRecommendationIds": ["R-001"],
+  "applied": ["R-001"],
+  "skipped": [
+    { "id": "R-002", "reason": "explicit_requires_interactive_approval" }
+  ],
+  "failed": []
+}
+```
+
+Every input ID has exactly one outcome. Unattended explicit items are skipped
+regardless of the supplied ID list. Missing/unknown class or ID blocks intake.
+Use reason `manual` with the required change for unsupported scaffold work;
+failed entries carry an ID and error/verification reason.
+
 ## Proceed?
 
 Confirm to begin applying the approved documentation changes.

package/assets/skills/oat-docs-authoring/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: oat-docs-authoring
 description: Use when authoring or restructuring targeted content inside an existing OAT Markdown surface or OAT/Fumadocs docs app. Preserves OAT docs navigation, generated indexes, and validation boundaries.
-argument-hint: '[docs task or target path]'
+argument-hint: '[docs task or target path] [--ia-guidance <path|url>]'
 disable-model-invocation: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
 user-invocable: true
 metadata:
-  version: '1.1.3'
+  version: '1.2.0'
 ---
 
 # OAT Docs Authoring
@@ -14,9 +14,8 @@ metadata:
 Use this skill for targeted documentation authoring and small structural edits
 inside an existing OAT Markdown surface or OAT/Fumadocs docs app.
 
-This is a thin wrapper over `authoring-docs`. Load `authoring-docs` for
-universal evidence gathering, page-type selection, writing style, templates,
-and review standards. Keep this wrapper focused on OAT Markdown/Fumadocs placement,
+This is a thin wrapper over `authoring-docs` for universal evidence gathering,
+page-type selection, writing style, templates, and review standards. Keep this wrapper focused on OAT Markdown/Fumadocs placement,
 navigation, generated artifacts, validation, and lifecycle boundaries.
 
 ## Prerequisites
@@ -111,9 +110,22 @@ Use `references/docs-root-resolution.md` before assuming any path. OAT docs apps
 commonly live outside `apps/oat-docs`, and `.oat/config.json` may describe the
 generated root index separately from the authored docs root.
 
-If the request needs universal documentation standards, load `authoring-docs`
-and use its reference map for evidence gathering, page type, writing style,
-templates, and review rubric.
+Independently probe each exact `authoring-docs/SKILL.md` in order:
+`${SKILL_DIR}/..` from the loaded skill (`SKILL_DIR` is the absolute directory
+containing that loaded `SKILL.md`), `${HOME}/.agents/skills`, then
+`<repo-root>/.agents/skills`. Bind the first matching `authoring-docs` directory
+once as `AUTHORING_DOCS_ROOT`; load `${AUTHORING_DOCS_ROOT}/SKILL.md` and use
+that same root for every authoring-docs reference and script, never ambient
+discovery. If none is found, name `authoring-docs`, stop this handoff, and give
+the intended-scope recovery command: `oat tools install docs --scope <user|project>`
+or `oat tools update --pack docs --scope <user|project>`.
+
+Use the bound skill's reference map for evidence gathering, page type, writing
+style, templates and review rubric. For IA work use its five-axis method and
+`${AUTHORING_DOCS_ROOT}/references/guidance-sources.md`: explicit `--ia-guidance` or
+conversation → repo config → user config → built-in. Cite ordered source
+locators/provenance in the handoff; respect AGENTS/contributing authority,
+keep non-repo sources read-only and report conflicts as `ask_user`.
 
 ### Step 2: Inspect Evidence and Local Maps
 

package/assets/skills/oat-docs-bootstrap/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: oat-docs-bootstrap
 description: Use when bootstrapping or adopting an OAT documentation surface in a repo. Guides the user through preflight detection, richer input gathering than the raw CLI, `oat docs init` invocation with gated post-patches for open CLI gaps, build verification, post-scaffold config inspection, and an educational walkthrough. Supports plain Markdown (file-level path), Fumadocs (full path), and MkDocs (lean path with defined minimum contract).
-argument-hint: '<optional-target-dir>'
+argument-hint: '<optional-target-dir> [--ia-guidance <path|url>]'
 disable-model-invocation: true
 user-invocable: true
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
 metadata:
-  version: '1.3.3'
+  version: '1.4.1'
 ---
 
 # Docs Bootstrap
@@ -114,13 +114,15 @@ OAT ▸ DOCS BOOTSTRAP
 
 The detailed framework procedures below apply to Fumadocs/MkDocs. When the selected tooling is `markdown`, use this path for Steps 2–7 instead; never run framework post-patches, the FP-15 AGENTS bridge, dependency discovery/install, package/Turbo patches, or a site build. Step 1 remains the shared read-only detector.
 
-1. **Preflight and routing:** Read `documentation.tooling` as a non-empty string. A non-string value (including a legacy object with a `framework` field) is invalid/undeclared tooling in the CLI; surface it for a user decision before proceeding, without silently clearing or retagging it. Declared tooling is authoritative: configured Markdown uses `documentation.root` literally, including when it contains a child named `docs`; declared frameworks or unknown stacks are not plain-doc adoption candidates. With no declared tooling, check framework evidence first (`mkdocs.yml`, Fumadocs/Next config and docs-app package scripts/dependencies), then inspect the chosen dedicated content directory for authored `.md`/`.mdx` pages. A repository-root README alone is insufficient; an empty selected directory is fresh setup. For a populated plain tree, lead with **adopt and audit**, **audit only**, or **abort**. Audit only delegates read-only to `oat-docs-analyze` and exits. Adoption requires the explicit user choice and CLI `--adopt`; `--yes` alone never authorizes it. An incompatible declared root/index/tooling requires a user decision, with no silent clearing or retagging. Keep the existing explicitly authorized framework replacement path when a framework is selected.
+1. **Preflight and routing:** Read `documentation.tooling` as a non-empty string. A non-string value (including a legacy object with a `framework` field) is invalid/undeclared tooling in the CLI; surface it for a user decision before proceeding, without silently clearing or retagging it. Declared tooling is authoritative: configured Markdown uses `documentation.root` literally, including when it contains a child named `docs`; declared frameworks or unknown stacks are not plain-doc adoption candidates. With no declared tooling, check framework evidence first (`mkdocs.yml`, Fumadocs/Next config and docs-app package scripts/dependencies), then inspect the chosen dedicated content directory for authored `.md`/`.mdx` pages. A repository-root README alone is insufficient; an empty selected directory is fresh setup. For a populated plain tree, default to `oat-docs-analyze` then `oat-docs-apply` for approved repairs and exit without scaffolding. Offer **adopt and audit**, **audit only**, or **abort** when adoption is explicitly requested. Audit only delegates read-only to `oat-docs-analyze` and exits. Adoption requires the explicit user choice and CLI `--adopt`; `--yes` alone never authorizes it. An incompatible declared root/index/tooling requires a user decision, with no silent clearing or retagging. Keep the existing explicitly authorized framework replacement path when a framework is selected.
 2. **Gather inputs:** Offer “Markdown (plain files), Fumadocs, or MkDocs?” Collect documentation title (`--site-name`), dedicated relative target directory (default `docs` in every repo shape), and optional description. Reuse an existing compatible configured Markdown root. Ask no app/package name, package-manager, site-runtime, or dependency questions. Lint and format default to `none`; describe selected existing repository tools only, without installing them. Validate a nonempty title and a dedicated in-repository target, excluding the repository root and escaping symlinks. Confirm fresh setup or additive adoption, title, root, and audit handoff. `appName` is absent and `conflictResolution` is `adopt`, `audit`, `abort`, or null for this path.
+   Before Markdown CLI invocation, run **Step 2.5** for fresh setup and explicitly selected adoption; it is not bypassed by this condensed path.
+
 3. **Invoke CLI:** Probe `$CLI_CMD docs init --help` and require advertised Markdown/`--adopt` support before invocation; if missing, report the needed CLI update rather than fabricating scaffold files. Run `$CLI_CMD docs init --framework markdown --target-dir <root> --site-name <title> --description <description> --lint none --format none --yes`, adding `--adopt` only for explicit adoption. Pass the selected lint/format values when using existing tools. Never pass app-only flags. An optional `--dry-run` previews file/config/guidance changes without writes; it does not count as a completed bootstrap. Capture terminal/JSON results, exact exit, created/preserved files, config changes, guidance action, and audit advice. `partial`/exit 1 with manual-required or blocked guidance means unresolved guidance; real runs may have created files, whereas dry-runs have only planned files. Report actual state and stop before claiming completion. Other refusals also stop without post-patches. For success, read config back to resolve the actual content root and authored index.
 4. **Verify files:** Print `[4/7] Verifying files…`. Check config root/index, baseline file existence, nonempty `title`/`description`, useful audience/scope context and populated `## Contents` links resolving to actual sibling pages or child `index.md`s. Honor excludes and asset-only exceptions; preserve local AGENTS instructions. Fresh setup creates only authored `index.md` and `contributing.md` in the target; verify no docs-root AGENTS, app package, framework config, dependencies, or root build changes. Run already documented lint/link/format checks when applicable; otherwise inspect files/links directly. Adoption preserves existing bytes and may leave missing child indexes, metadata, context, or links: record these as audit gaps for analyze/apply rather than repairing them or calling the tree fully conformant. Distinguish successful setup verification from content-conformance findings.
 5. **Inspect config:** `documentation.tooling` is the string `markdown`; `root` is the literal content directory; `index` is its authored entrypoint, normally `<root>/index.md`. Markdown introduces no `documentation.config`. Preserve unrelated config/excludes/completion settings. Verify deterministic managed root Documentation guidance names that root, Markdown tooling, authored index, and `<root>/contributing.md`; preserve manual/local guidance and surface unresolved disposition. The Step 5e completion opt-in remains available using the docs root rather than an app name, without silently changing an existing value. No nested app-config reconciliation or framework patch inspection applies.
 6. **Walkthrough:** In short chunks, show actual config and `<root>/index.md`: useful context plus the Contents map, title/description metadata, sibling `page.md` and child `section/index.md` links, exclusions and asset-only exceptions. Explain adding a page/section and updating the nearest authored map without overwriting existing context. Root AGENTS Documentation guidance and `<root>/contributing.md` establish agent/human conventions; a preexisting local AGENTS file remains authoritative, but bootstrap creates none. Authored indexes are edited directly. Optional generated inventories require explicit external output, e.g. `$CLI_CMD docs generate-index --docs-dir <root> --output .oat/docs-manifest.md`; output must stay outside the full configured content root and cannot overwrite the configured authored index even with a narrowed `--docs-dir`. Generation does not repoint `documentation.index`. Markdown bootstrap never generates a manifest automatically. Skip framework deep dives and preview-server/build commands.
-7. **Audit handoff and summary:** Offer `oat-docs-analyze` against the literal configured root, followed by `oat-docs-apply` only for approved repairs. An adopted incomplete tree needs that audit; config/guidance alone prove no full conformance. Explain `oat-project-document` for source-backed project deltas. Summarize tooling, actual root/authored index, created/preserved files, guidance/config disposition, file-check outcomes, unresolved audit gaps, optional manifest ownership, and exact skill handoff. For dry-run/partial/refusal, label the outcome accordingly rather than printing BOOTSTRAP COMPLETE. No app, install, build, patch, or dev-command fields apply.
+7. **Audit handoff and summary:** Offer `oat-docs-analyze` against the literal configured root, followed by `oat-docs-apply` only for approved repairs. An adopted incomplete tree needs that audit; config/guidance alone prove no full conformance. Explain `oat-project-document` for source-backed project deltas. Summarize tooling, actual root/authored index, created/preserved files, guidance/config disposition, ordered IA guidance locators/provenance and proposal recommendation/conflicts, file-check outcomes, unresolved audit gaps, optional manifest ownership, and exact skill handoff. For dry-run/partial/refusal, label the outcome accordingly rather than printing BOOTSTRAP COMPLETE. No app, install, build, patch, or dev-command fields apply.
 
 ### Step 1: Preflight Detector
 
@@ -155,7 +157,7 @@ Read (do not modify):
 
 Build `conflicts: []` by adding an entry for each finding:
 
-- If `configDocumentation` is non-null → `{ kind: 'existing-config', detail: <summary of what's there> }`
+- If `configDocumentation` declares a docs surface (`root`, `tooling`, `index` or `config`) → `{ kind: 'existing-config', detail: <summary of what's there> }`. A guidance-only section is an IA input, not evidence of an existing docs surface; retain it and continue fresh setup.
 - If `docsAppPath` exists on disk → `{ kind: 'existing-app-dir', detail: <path + whether it has uncommitted changes> }`
 - If `agentsMdSection` is true → `{ kind: 'existing-agents-section', detail: <what the section says> }`
 
@@ -208,7 +210,7 @@ Print `[2/7] Gathering inputs…` at the start of this step.
 
 **2a. Resolve Preflight conflicts (if any).**
 
-If `conflicts[]` from Preflight is non-empty, present them together and collect a `conflictResolution`. See the **Conflict Resolution Contract** sub-procedure below for the exact semantics of each option. Do not proceed to input questions until the user has chosen a resolution.
+If `conflicts[]` from Preflight is non-empty, present them together and default to `repair`: run `oat-docs-analyze` (with `--ia` when structure is requested), review its artifact, then `oat-docs-apply` for approved repairs and exit. Use replacement or a second app only after an explicit user choice; a generic request to bootstrap is insufficient. See the **Conflict Resolution Contract** below. Do not scaffold until that contract is satisfied.
 
 If `conflicts[]` is empty, skip conflict handling and go to 2b.
 
@@ -271,14 +273,14 @@ Input Result:
 
 #### Conflict Resolution Contract (sub-procedure)
 
-When Preflight (Step 1) records non-empty `conflicts[]`, present them to the user together and collect exactly one resolution. Each resolution below has a precise definition in terms of **allowed mutations**, **preserved state**, and **stop conditions**. The Scaffold Runner (Step 3) reads the chosen resolution and adjusts its behavior; it never reinvents these semantics.
+When Preflight (Step 1) records non-empty `conflicts[]`, present them together and default to `repair` unless the user explicitly selects another resolution. Record exactly one resolution. Each resolution below has a precise definition in terms of **allowed mutations**, **preserved state**, and **stop conditions**. The Scaffold Runner (Step 3) reads the chosen resolution and adjusts its behavior; it never reinvents these semantics.
 
 Resolution options:
 
 - **`replace`** — Treat the existing docs setup as disposable and scaffold fresh.
   - **Allowed mutations (executed by this sub-procedure before Scaffold Runner begins):**
     - Remove the existing docs app directory (`existingDocs.docsAppPath`), if present on disk.
-    - Remove the `documentation` section from `$REPO_ROOT/.oat/config.json`, if present. The CLI will rewrite it during init.
+    - Clear the replaced surface fields in `documentation` in `$REPO_ROOT/.oat/config.json`, preserving `documentation.guidance` if present. The CLI will rewrite surface ownership during init; advisory guidance is unrelated to the discarded scaffold.
     - Remove the `## Documentation` section from `$REPO_ROOT/AGENTS.md`, if present. The CLI upserts its own.
   - **Preserved state:** Everything outside the three touchpoints above. Git history is preserved — deletions are tracked normally and remain recoverable via `git revert` / `git checkout`.
   - **Stop conditions:**
@@ -319,7 +321,7 @@ Resolution options:
     ```
 
 - **`repair`** — Fix the existing setup in place rather than replacing it. Delegate to the docs-analysis pack.
-  - **Allowed mutations (by this sub-procedure):** None directly. The bootstrap skill does not modify existing docs app files. It hands off to `oat-docs-analyze` (read-only audit) and, with user approval, to `oat-docs-apply` (applies approved recommendations).
+  - **Allowed mutations (by this sub-procedure):** None directly. The bootstrap skill does not modify existing docs app files. It hands off to `oat-docs-analyze` (read-only audit), then passes the analysis artifact plus approved recommendation IDs to `oat-docs-apply`; explicit items require individual approval.
   - **Preserved state:** Existing docs app directory, the `documentation` config section, the root `AGENTS.md` `## Documentation` section — all preserved unless analyze surfaces a recommendation and the user approves it via apply.
   - **Stop conditions:**
     - Invoke `oat-docs-analyze` and surface its report to the user. If analyze cannot produce meaningful recommendations (e.g., `documentation.index` points at a missing file, or the app directory is empty), **stop the flow before Scaffold Runner**, report what analyze found, and ask the user whether to escalate to `replace`.
@@ -336,10 +338,10 @@ Preflight detected existing docs setup:
   - existing-agents-section: AGENTS.md has a ## Documentation section
 
 How should I proceed?
-  1. replace    — remove the existing docs app and scaffold fresh at the same path
-  2. second-app — (deferred) add a new docs app alongside; not available in current CLI
-  3. abort      — exit without changes
-  4. repair     — run `oat-docs-analyze` / `oat-docs-apply` on the existing setup
+  1. repair     — default: run `oat-docs-analyze` / `oat-docs-apply` on the existing setup
+  2. replace    — explicit choice required: remove the existing docs app and scaffold fresh
+  3. second-app — explicit choice required; deferred because current CLI cannot support it
+  4. abort      — exit without changes
 
 Choose:
 ```
@@ -351,10 +353,57 @@ Record the user's choice as `conflictResolution` in the Input Result. If the use
 No matter which resolution the user picks, the Scaffold Runner (Step 3) **never** invokes `oat docs init` until:
 
 1. The chosen resolution's "Allowed mutations" have **completed successfully**, and
-2. The working-tree state **matches what the CLI expects** for that resolution (e.g., for `replace`: the target directory is empty or absent, the `documentation` config section is cleared, the root `AGENTS.md` `## Documentation` section is cleared; for `abort` / `repair`: the skill has already exited).
+2. The working-tree state **matches what the CLI expects** for that resolution (e.g., for `replace`: the target directory is empty or absent, the `documentation` surface fields are cleared (any `guidance` input is preserved), the root `AGENTS.md` `## Documentation` section is cleared; for `abort` / `repair`: the skill has already exited).
 
 If any mutation fails or any invariant check fails, **stop the flow before scaffold** and surface the error. A partial resolution followed by a scaffold produces a worse end state than either doing nothing or completing the resolution cleanly.
 
+### Step 2.5: IA Discovery and Proposal
+
+Run for fresh Markdown, Fumadocs and MkDocs setup, and explicit adoption, before
+any scaffold invocation. An existing surface routed to repair takes this stage
+through `oat-docs-analyze --ia`; it does not return to scaffold afterward.
+
+1. Independently probe each exact `authoring-docs/SKILL.md` in order:
+   `${SKILL_DIR}/..` from the loaded skill (`SKILL_DIR` is the absolute directory
+   containing that loaded `SKILL.md`), `${HOME}/.agents/skills`, then
+   `<repo-root>/.agents/skills`. Bind the first matching `authoring-docs` directory
+   once as `AUTHORING_DOCS_ROOT`; load `${AUTHORING_DOCS_ROOT}/SKILL.md` and use
+   that same root for every authoring-docs reference and script, never ambient
+   discovery. If none is found, name `authoring-docs`, stop this handoff, and give
+   the intended-scope recovery command: `oat tools install docs --scope <user|project>`
+   or `oat tools update --pack docs --scope <user|project>`.
+   Read `${AUTHORING_DOCS_ROOT}/references/guidance-sources.md` and
+   `${AUTHORING_DOCS_ROOT}/references/information-architecture.md`.
+   Resolve explicit `--ia-guidance`/conversation → repo → user → built-in and
+   retain ordered locators/provenance. These are skill inputs, not new CLI flags.
+2. Read repo signals: manifests, UI navigators and journeys, CLI `bin`, routers,
+   IaC, `e2e/` or `.maestro/`, existing docs, independently consumed monorepo units.
+   Read AGENTS/contributing authority first. Do not infer triad needs from UI alone.
+3. Ask only decision-changing questions about readers/work contexts, independent
+   verification, canonical facts elsewhere and links that must survive.
+4. Use the shared five axes and IA Proposal template to present **two plausible
+   candidate structures**, each a **two-level tree with 5–8 representative page
+   placements**, one page job per placement and the **nearest approved preset**.
+   Size controls materialized depth; it does not select audience. For Flat Small,
+   use grouped index headings rather than new directories.
+5. Recommend one with evidence and tradeoffs; retain unresolved conflicts as
+   `ask_user` with local/external source citations. Non-repo guidance stays read-only
+   and private exemplars are never copied. Cite ordered sources in the proposal
+   and final summary, including the built-in path when it wins.
+6. Obtain explicit approval of the selected IA before persistence. After setup,
+   use apply's `record-ia` procedure: target-repo `oat pjm doctor --json` and
+   adoption check before `oat decision new`, an Information architecture section
+   in the framework docs-app AGENTS.md or Markdown contributing page, and shared
+   `documentation.ia` mirror. Preserve existing guidance; the authored record is
+   authoritative. If approval/adoption is pending, retain the proposal and report
+   it unrecorded. Do not silently initialize PJM. For an existing surface, hand
+   off an analysis artifact plus approved recommendation IDs to apply, with
+   individual approval for explicit record/restructure/tooling items.
+   This stage does not materialize preset trees or change scaffold/nav defaults.
+   Sidebar ownership is separately chosen for existing framework apps; absent
+   remains undeclared, Markdown ignores it, and no automatic nav generation is
+   authorized by IA approval alone.
+
 ### Step 3: Scaffold Runner
 
 Invoke `oat docs init` with the collected inputs and then apply gated post-patches for any CLI gaps the Capability Detection sub-procedure reports as still-open. The Scaffold Runner probes CLI capabilities, invokes the CLI, and applies the AGENTS.md bridge if still needed. Template content is CLI-owned; report old-scaffold shapes through `oat-docs-analyze`.
@@ -797,7 +846,13 @@ Delegate — do not re-implement analyze/apply logic here.
 
 1. Invoke the `oat-docs-analyze` skill against the scaffolded app. Pass the Inspection Result's `documentation.root` path so analyze targets the right surface. Wait for analyze to complete.
 2. Surface analyze's report to the user in its native form — do not re-summarize. The user reads it, decides which recommendations to approve.
-3. If the user approves any recommendations, invoke the `oat-docs-apply` skill with the approved subset. Wait for apply to complete.
+3. Capture the analysis artifact path and approved recommendation IDs, then
+   invoke `oat-docs-apply` with exactly that input. Preserve every approval class:
+   blanket approval covers only default items; explicit items need individual
+   approval by ID, and unattended runs skip/report them. Wait for apply's
+   structured applied/skipped-with-reason/failed IDs; report partial/manual work.
+   Never pass an unexplained "approved subset" or treat kickoff consent as
+   approval of every recommendation.
 4. Report the outcome back briefly: branch name, PR URL if opened, files changed count.
 
 If analyze produces no recommendations (the scaffold is complete and nothing's missing — unlikely on a fresh scaffold but possible), tell the user and skip apply.
@@ -826,6 +881,10 @@ OAT ▸ DOCS BOOTSTRAP COMPLETE
 App:         {appName}
 Location:    {appRoot}
 Framework:   {framework}
+IA guidance: {ordered selected locators + explicit/conversation/shared/user/builtin provenance}
+IA proposal: {candidate recommendation, nearest preset, conflicts or none}
+IA record: {decision + authored section + shared mirror, or pending reason}
+Apply handoff: {artifact path, approved IDs, applied/skipped/failed result or not run}
 Config:      {configPath} (documentation section)
 
 Created:

package/dist/commands/config/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/commands/config/index.ts"],"names":[],"mappings":"AAIA,OAAO,EAAE,mBAAmB,EAAE,KAAK,cAAc,EAAE,MAAM,sBAAsB,CAAC;AAIhF,OAAO,EAEL,KAAK,aAAa,EACnB,MAAM,iCAAiC,CAAC;AAoBzC,OAAO,EAUL,KAAK,SAAS,EACd,KAAK,aAAa,EAClB,KAAK,cAAc,EAQnB,KAAK,UAAU,EAqBhB,MAAM,oBAAoB,CAAC;AAE5B,OAAO,EAGL,KAAK,cAAc,EAEpB,MAAM,iBAAiB,CAAC;AAIzB,OAAO,EAGL,KAAK,8BAA8B,EACnC,KAAK,yBAAyB,EAC/B,MAAM,kCAAkC,CAAC;AAE1C,OAAO,EACL,mCAAmC,EACnC,0BAA0B,EAC3B,MAAM,yCAAyC,CAAC;AACjD,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAyKpC,UAAU,yBAAyB;IACjC,mBAAmB,EAAE,CACnB,OAAO,EAAE,UAAU,CAAC,OAAO,mBAAmB,CAAC,CAAC,CAAC,CAAC,KAC/C,cAAc,CAAC;IACpB,kBAAkB,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;IACrD,aAAa,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,SAAS,CAAC,CAAC;IACxD,kCAAkC,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,SAAS,CAAC,CAAC;IAC7E,2CAA2C,EAAE,CAC3C,QAAQ,EAAE,MAAM,KACb,OAAO,CAAC,SAAS,CAAC,CAAC;IACxB,gDAAgD,EAAE,CAChD,QAAQ,EAAE,MAAM,KACb,OAAO,CAAC,SAAS,CAAC,CAAC;IACxB,6CAA6C,EAAE,CAC7C,QAAQ,EAAE,MAAM,KACb,OAAO,CAAC,SAAS,CAAC,CAAC;IACxB,yBAAyB,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,aAAa,CAAC,CAAC;IACxE,cAAc,EAAE,CAAC,QAAQ,EAAE,MAAM,EAAE,MAAM,EAAE,SAAS,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IACvE,kBAAkB,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,cAAc,CAAC,CAAC;IAClE,mBAAmB,EAAE,CACnB,QAAQ,EAAE,MAAM,EAChB,MAAM,EAAE,cAAc,KACnB,OAAO,CAAC,IAAI,CAAC,CAAC;IACnB,cAAc,EAAE,CAAC,aAAa,EAAE,MAAM,KAAK,OAAO,CAAC,UAAU,CAAC,CAAC;IAC/D,eAAe,EAAE,CAAC,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,UAAU,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IAC9E,mBAAmB,EAAE,CACnB,QAAQ,EAAE,MAAM,EAChB,GAAG,EAAE,MAAM,CAAC,UAAU,KACnB,OAAO,CAAC,MAAM,CAAC,CAAC;IACrB,sBAAsB,EAAE,CACtB,QAAQ,EAAE,MAAM,EAChB,aAAa,EAAE,MAAM,EACrB,GAAG,EAAE,MAAM,CAAC,UAAU,KACnB,OAAO,CAAC,cAAc,CAAC,CAAC;IAC7B,iBAAiB,EAAE,MAAM,OAAO,CAAC,MAAM,CAAC,CAAC;IACzC,QAAQ,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;IAC5C,eAAe,EAAE,CAAC,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,OAAO,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IAChE,aAAa,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,aAAa,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC;IACzE,kBAAkB,EAAE,CAClB,QAAQ,EAAE,MAAM,EAChB,KAAK,EAAE,MAAM,EACb,OAAO,EAAE,yBAAyB,KAC/B,OAAO,CAAC,8BAA8B,CAAC,CAAC;IAC7C,mCAAmC,EAAE,OAAO,mCAAmC,CAAC;IAChF,0BAA0B,EAAE,OAAO,0BAA0B,CAAC;IAC9D,UAAU,EAAE,MAAM,CAAC,UAAU,CAAC;CAC/B;AA2tHD,wBAAgB,mBAAmB,CACjC,SAAS,GAAE,OAAO,CAAC,yBAAyB,CAAM,GACjD,OAAO,CAqMT"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/commands/config/index.ts"],"names":[],"mappings":"AAIA,OAAO,EAAE,mBAAmB,EAAE,KAAK,cAAc,EAAE,MAAM,sBAAsB,CAAC;AAIhF,OAAO,EAEL,KAAK,aAAa,EACnB,MAAM,iCAAiC,CAAC;AAoBzC,OAAO,EAUL,KAAK,SAAS,EACd,KAAK,aAAa,EAClB,KAAK,cAAc,EAQnB,KAAK,UAAU,EAwBhB,MAAM,oBAAoB,CAAC;AAE5B,OAAO,EAGL,KAAK,cAAc,EAEpB,MAAM,iBAAiB,CAAC;AAIzB,OAAO,EAGL,KAAK,8BAA8B,EACnC,KAAK,yBAAyB,EAC/B,MAAM,kCAAkC,CAAC;AAE1C,OAAO,EACL,mCAAmC,EACnC,0BAA0B,EAC3B,MAAM,yCAAyC,CAAC;AACjD,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AA4KpC,UAAU,yBAAyB;IACjC,mBAAmB,EAAE,CACnB,OAAO,EAAE,UAAU,CAAC,OAAO,mBAAmB,CAAC,CAAC,CAAC,CAAC,KAC/C,cAAc,CAAC;IACpB,kBAAkB,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;IACrD,aAAa,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,SAAS,CAAC,CAAC;IACxD,kCAAkC,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,SAAS,CAAC,CAAC;IAC7E,2CAA2C,EAAE,CAC3C,QAAQ,EAAE,MAAM,KACb,OAAO,CAAC,SAAS,CAAC,CAAC;IACxB,gDAAgD,EAAE,CAChD,QAAQ,EAAE,MAAM,KACb,OAAO,CAAC,SAAS,CAAC,CAAC;IACxB,6CAA6C,EAAE,CAC7C,QAAQ,EAAE,MAAM,KACb,OAAO,CAAC,SAAS,CAAC,CAAC;IACxB,yBAAyB,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,aAAa,CAAC,CAAC;IACxE,cAAc,EAAE,CAAC,QAAQ,EAAE,MAAM,EAAE,MAAM,EAAE,SAAS,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IACvE,kBAAkB,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,cAAc,CAAC,CAAC;IAClE,mBAAmB,EAAE,CACnB,QAAQ,EAAE,MAAM,EAChB,MAAM,EAAE,cAAc,KACnB,OAAO,CAAC,IAAI,CAAC,CAAC;IACnB,cAAc,EAAE,CAAC,aAAa,EAAE,MAAM,KAAK,OAAO,CAAC,UAAU,CAAC,CAAC;IAC/D,eAAe,EAAE,CAAC,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,UAAU,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IAC9E,mBAAmB,EAAE,CACnB,QAAQ,EAAE,MAAM,EAChB,GAAG,EAAE,MAAM,CAAC,UAAU,KACnB,OAAO,CAAC,MAAM,CAAC,CAAC;IACrB,sBAAsB,EAAE,CACtB,QAAQ,EAAE,MAAM,EAChB,aAAa,EAAE,MAAM,EACrB,GAAG,EAAE,MAAM,CAAC,UAAU,KACnB,OAAO,CAAC,cAAc,CAAC,CAAC;IAC7B,iBAAiB,EAAE,MAAM,OAAO,CAAC,MAAM,CAAC,CAAC;IACzC,QAAQ,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;IAC5C,eAAe,EAAE,CAAC,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,OAAO,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IAChE,aAAa,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,aAAa,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC;IACzE,kBAAkB,EAAE,CAClB,QAAQ,EAAE,MAAM,EAChB,KAAK,EAAE,MAAM,EACb,OAAO,EAAE,yBAAyB,KAC/B,OAAO,CAAC,8BAA8B,CAAC,CAAC;IAC7C,mCAAmC,EAAE,OAAO,mCAAmC,CAAC;IAChF,0BAA0B,EAAE,OAAO,0BAA0B,CAAC;IAC9D,UAAU,EAAE,MAAM,CAAC,UAAU,CAAC;CAC/B;AA22HD,wBAAgB,mBAAmB,CACjC,SAAS,GAAE,OAAO,CAAC,yBAAyB,CAAM,GACjD,OAAO,CAqMT"}