Add NEXUS consolidation audit and MANUS dispatch schema (Fable 5 routing)

[jwk2588]

Motivation

• Provide a technical-only consolidation audit and roadmap for the NEXUS Klein‑Team ADR platform to guide repo consolidation, orchestration, and staging work.
• Capture an explicit MANUS-as-conductor configuration model so task routing, write‑back policies, and protected ID rules are machine-readable.
• Evaluate where Anthropic Claude Fable 5 fits into the orchestration (multi-day agent harness, vision workloads, and escalation routing) to inform routing and budget decisions.

Description

• Add a comprehensive audit and roadmap at docs/klein_team_adr_platform_audit.md covering local repo inventory, partial public repo inventory, overlap/dependency mapping, consolidation recommendations, MANUS sequence diagram, a $100 Codex constrained staging plan, and an objective Fable 5 deployment recommendation.
• Add a JSON Schema config/manus_dispatch.schema.json that defines the MANUS dispatch configuration shape including sourceOfTruth, routingTargets, routingRules, and a write‑back idPolicy enforcing additive-only EV-/SB-style IDs.
• Add a runnable example configuration config/manus_dispatch.example.json that includes routing targets for codex, claude_sonnet, claude_opus, claude_fable, kimi_swarm, and python_scripts and example routing rules that escalate vision and multi-day migration tasks to claude_fable with human review gates.
• Document operational constraints and guardrails (privilege boundaries, PR-only writeback, Fable cost/retention considerations, and required user inputs to proceed).

Testing

• Successfully validated JSON formatting for the schema and example using python -m json.tool config/manus_dispatch.schema.json and python -m json.tool config/manus_dispatch.example.json.
• Verified presence of key topics in the deliverables using rg -n "Fable 5|Repo audit|manus_dispatch|claude_fable|EV-/SB-|What Codex needs" docs/klein_team_adr_platform_audit.md config/manus_dispatch.*.json.
• Attempted schema semantic validation with jsonschema.Draft202012Validator but the environment lacked the jsonschema package, so full schema validation was not executed in CI.
• No other automated tests were modified or required by these additions.

---

Codex Task

[gemini-code-assist]

Code Review

This pull request introduces a MANUS dispatch configuration schema, an example configuration file, and an architectural decision record (ADR) document outlining repository consolidation and Fable 5 deployment strategies. The feedback suggests strengthening the JSON schema by adding a semantic versioning pattern constraint to the version field and enforcing uniqueness on the taskTypes and signals arrays to prevent duplicate matching criteria.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

To ensure that configuration versions strictly adhere to semantic versioning (SemVer), it is recommended to add a pattern constraint to the version property.

        "version": {
            "type": "string",
            "pattern": "^[0-9]+\\.[0-9]+\\.[0-9]+(-[a-zA-Z0-9.]+)?$",
            "description": "Semantic version for the conductor configuration."
        },

[gemini-code-assist]

To prevent redundant or duplicate matching criteria within routing rules, consider enforcing uniqueness on the taskTypes array by adding "uniqueItems": true.

                            "taskTypes": {
                                "type": "array",
                                "items": {
                                    "type": "string"
                                },
                                "uniqueItems": true
                            },

[gemini-code-assist]

To prevent redundant or duplicate matching criteria within routing rules, consider enforcing uniqueness on the signals array by adding "uniqueItems": true.

                            "signals": {
                                "type": "array",
                                "items": {
                                    "type": "string"
                                },
                                "uniqueItems": true
                            },

[jwk2588]

review