fix(#1296): align config docs/prompts/schema with consumers (#1299)

* fix(#1296): align config docs/prompts/schema with consumers

The user-facing config surface disagreed with what the consumers actually do
(subset of the #1216 audit). No runtime consumption behavior changes.

- workflow.subagent_timeout: settings-advanced.md prompt + docs/CONFIGURATION.md
  said "seconds (default 600)" but the consumer (map-codebase.md) uses
  milliseconds (default 300000). Relabeled all four spots in settings-advanced.md
  (prompt, parse-default list, example, confirmation table) + the CONFIGURATION.md
  row.
- review.models.<cli>: settings-integrations.md, docs/CONFIGURATION.md (Integration
  Settings), and docs/CLI-TOOLS.md documented a shell command, but review.md injects
  the value into a --model/-m flag. Relabeled to a bare model id and reconciled the
  contradictory CONFIGURATION.md sections.
- workflow.test_command + workflow.build_command: consumed via config-get
  (test_command in verify-phase/execute-phase/audit-fix/post-merge-gate;
  build_command in post-merge-gate) and documented, but absent from validKeys so
  `config set` rejected them. Registered both in config-schema.manifest.json and
  documented them in references/planning-config.md (overview + complete reference).

Regression tests: behavioral config-set tests (tests/config.test.cjs) + doc-parity
content guards (tests/config-field-docs.test.cjs).

Deferred to other #1216 clusters: security-gate wiring, search_gitignored wiring,
mvp_mode, source_grounding_authority labeling, and config-set enum enforcement.

Closes #1296
Refs #1216

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* chore(changeset): Fixed fragment for #1296 config-surface alignment

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

gsd-core/workflows/settings-advanced.md

@@ -50,7 +50,7 @@ Planning Tuning:
 - `workflow.plan_bounce` (default: `false`)
 - `workflow.plan_bounce_passes` (default: `2`)
 - `workflow.plan_bounce_script` (default: `null`)
-- `workflow.subagent_timeout` (default: `600`)
+- `workflow.subagent_timeout` (default: `300000`)
 - `workflow.inline_plan_threshold` (default: `3`)
 
 Execution Tuning:
@@ -155,12 +155,12 @@ AskUserQuestion([
     ]
   },
   {
-    question: "Subagent timeout (seconds)? (current: <value or 600>)",
+    question: "Subagent timeout (milliseconds)? (current: <value or 300000>)",
     header: "Subagent Timeout",
     multiSelect: false,
     options: [
       { label: "Keep current", description: "Leave timeout unchanged." },
-      { label: "Enter seconds", description: "Integer number of seconds. Non-numeric rejected. Default: 600" }
+      { label: "Enter milliseconds", description: "Integer number of milliseconds. Non-numeric rejected. Default: 300000 (5 minutes)." }
     ]
   },
   {
@@ -498,7 +498,7 @@ keys and sibling sub-objects.
 ```bash
 # Example — only write keys the user changed. "Keep current" selections are skipped.
 gsd_run query config-set workflow.plan_bounce_passes 5
-gsd_run query config-set workflow.subagent_timeout 900
+gsd_run query config-set workflow.subagent_timeout 300000
 gsd_run query config-set git.base_branch main
 gsd_run query config-set context_window 1000000
 # Runtime model tier examples:
@@ -751,7 +751,7 @@ Display:
 | workflow.plan_bounce                       | {on/off} |
 | workflow.plan_bounce_passes                | {n} |
 | workflow.plan_bounce_script                | {path/null} |
-| workflow.subagent_timeout                  | {seconds} |
+| workflow.subagent_timeout                  | {milliseconds} |
 | workflow.inline_plan_threshold             | {n} |
 | workflow.node_repair                       | {on/off} |
 | workflow.node_repair_budget                | {n} |

gsd-core/workflows/settings-integrations.md

@@ -173,20 +173,20 @@ AskUserQuestion([
     multiSelect: false,
     options: [
       { label: "Claude", description: "review.models.claude — defaults to session model when unset" },
-      { label: "Codex", description: "review.models.codex — e.g. 'codex exec --model gpt-5'" },
-      { label: "Gemini", description: "review.models.gemini — e.g. 'gemini -m gemini-2.5-pro'" },
-      { label: "OpenCode", description: "review.models.opencode — e.g. 'opencode run --model claude-sonnet-4'" }
+      { label: "Codex", description: "review.models.codex — bare model id injected into --model, e.g. 'gpt-5'" },
+      { label: "Gemini", description: "review.models.gemini — bare model id injected into -m, e.g. 'gemini-2.5-pro'" },
+      { label: "OpenCode", description: "review.models.opencode — bare model id injected into --model, e.g. 'claude-sonnet-4'" }
     ]
   }
 ])
 ```
 
 For the selected CLI, show the current value (or `(unset)`) and offer
-Leave / Replace / Clear, followed by a text-input prompt for the new command
+Leave / Replace / Clear, followed by a text-input prompt for the model id
 string. Write via:
 
 ```bash
-gsd_run query config-set review.models.<cli> "<command string>"
+gsd_run query config-set review.models.<cli> "<model id>"
 ```
 
 After each update, return to the "Review model CLI mapping — what next?" question.