Review, validate, and publish the revised V2 explanation

[jamiepratt]

Orchestration

Issue kind: child implementation
Parent: #16
Depends on: #20
Type: HITL
Parallel group: publication
Conflict risk: low
Expected touchpoints: configured validation wrappers and publication gates, Civitas publication branch/PR, workflow submodule pointer branch/PR

What to Build

Conduct human review of the revised causal explanation, run the complete scoped validation and publication workflow, and publish reviewable pull requests in repository ownership order. This issue creates or updates PRs; it does not merge without separate approval.

Acceptance Criteria

• Human review approves causal wording, reading flow, visible density, and technical-depth boundaries.
• Model findings, software checks, and publication checks are reported separately.
• Historical V2 artifact hashes and non-promotion status remain unchanged.
• Configured CLJ and CLJS validation passes.
• The targeted render passes during iteration and the configured scoped publication gate passes before publication.
• Fresh navigation receives current interactive assets; coordinate with Make article preview dependency-aware for interactive assets #13 or restart the focused preview while it remains open.
• Browser verification covers console errors, desktop/mobile layout, keyboard operation, accessible labels, direct anchors, light/dark contrast, and overflow.
• The staged and outgoing Civitas paths are audited against the configured authored namespace with any outside/shared effects disclosed.
• The publication repository is committed and pushed before the workflow repository records its submodule pointer.
• A focused Civitas PR and then a workflow pointer PR are created; neither is merged without separate approval.

Validation

Use .agents/research-workflow.json and the root-owned wrappers as the command authority. Record model, software, and publication evidence in the PR descriptions. Verify the published preview in a separate internal-browser tab and retain V1 as the documented current target.

Notes

The Civitas submodule owns executable research and publication artifacts; the workflow repository owns orchestration and the exact published submodule pointer. Shared Civitas configuration changes remain outside scope unless separately justified and authorized.