feat(workloads): onboard trusted external validation

[Nobodyworld]

Summary

Begins issue #138 as the next large coherent Switchboard product slice after the merged Validation Broker command center.

base / merge base: 33a5836496fa933dd6aae65ec71238d1b5ac9772
branch: feat/trusted-workload-catalog-dogfood
planning head: dc33806e57edd8d0255b3f17c8379a482cf8ab31
state: planning reviewed; draft, open, unmerged
living ExecPlan: .agent/execplans/014_trusted_workload_catalog_dogfood.md

Intended product outcome

Turn Switchboard from a self-validating proof into a trusted multi-repository local execution broker:

trusted workload catalog
    -> repository-compatible manifest selection
    -> worker logical-repository readiness
    -> exact external PR resolution
    -> explicit approval
    -> repository-aware local routing
    -> fresh validation
    -> retained compact evidence
    -> worker-local exact reuse
    -> bounded history/publication

The first external dogfood target is public Nobodyworld/app-accounting-modular PR #126. Its exact current head must be re-resolved immediately before acceptance. Switchboard may validate it locally, but this slice must not modify, merge, close, retarget, mark ready, or automatically publish a comment to that target PR.

Locked scope

• strict source-controlled trusted repository/workload catalog;
• explicit repository-to-manifest compatibility;
• preservation of existing Switchboard manifest identities and digests;
• first external validate-accounting-modular@1 fixed-argv manifest;
• bounded worker logical repository availability with no paths;
• restart-safe existing-database compatibility;
• repository-aware first_available, cheapest_capable, hard pins, assessment, and exact reuse;
• repository-aware command-center onboarding and readiness;
• synthetic real-worker fresh/reuse proof;
• controlled real external exact-SHA dogfood or precise environment blocker;
• complete docs, local matrix, hosted matrix, and connector review.

Connector work already completed

• Issue feat(workloads): onboard trusted external repositories and prove real local dogfood #138 defines the complete product, trust, compatibility, dogfood, and acceptance contract.
• The living ExecPlan is committed and normalized under .agent/execplans/014_trusted_workload_catalog_dogfood.md.
• docs/reports/status.md records the merged PR feat(operator): ship end-to-end validation command center #137 baseline, current main, current single-repository limitation, active slice, and durable release/deployment boundary.
• Epic epic: evolve Switchboard into a cost-aware local execution broker #111 records PR feat(operator): ship end-to-end validation command center #137 as merged and issue feat(workloads): onboard trusted external repositories and prove real local dogfood #138 / PR feat(workloads): onboard trusted external validation #139 as the active large slice.
• The current external target remains open, draft, mergeable, and exact at 613cf89396c41a0ee3c3aa5886a55c264a38daf0 at the latest connector check; it has fully green hosted Python/container evidence and one separate manual literal-200%-zoom blocker.

Planning validation

Exact planning head dc33806e57edd8d0255b3f17c8379a482cf8ab31:

• Commitlint 31337683438 — success;
• CI 31337683431 — success;
• lint, typecheck, full tests, security, full-history Secrets audit, Link check, Coverage, and strict Browser UI tests all succeeded;
• connector planning review 4892665741 found no planning blocker.

The initial planning-head lint failure was only the end-of-file hook adding a final newline to the new ExecPlan. Connector commit 202dc7ec854c8ff59882a3c6c971ef64a8bd7669 normalized it before this final green planning head.

Explicit exclusions

No arbitrary shell, caller-authored manifest, database-authored executable profile, source modification, Git write, automatic external-PR publication, MCP, Secure MCP Tunnel, paid-provider integration, billing/rate-limit polling, browser/desktop/RPA worker, Docker-worker, webhook, Checks API, workflow dispatch, automatic approval/merge, release, deployment, or production/public-internet claim.

Required delivery process

Implementation must remain on this branch and in this existing draft PR. Maintain the living ExecPlan continuously. Use focused Conventional Commits. Run focused tests before the complete protected matrix, strict Playwright with zero skips, public-hygiene cleanup, and ultimate-head hosted checks. Keep the PR draft and unmerged until final connector review is complete. Merge remains a separate exact-head owner decision.

Closes #138 only after an explicitly authorized squash merge.

[Nobodyworld]

Connector planning review complete for issue #138 at exact head dc33806e57edd8d0255b3f17c8379a482cf8ab31 and exact base/merge base 33a5836496fa933dd6aae65ec71238d1b5ac9772.

The planning branch changes only the living ExecPlan and durable status report. Commitlint 31337683438 and CI 31337683431 succeeded, including lint, typecheck, full tests, security, full-history Secrets audit, Link check, Coverage, and strict Browser UI tests.

The accepted scope is one large coherent outcome rather than a catalog-only primitive: strict source-controlled repository/workload definitions, repository-to-manifest compatibility, an external accounting validation manifest, bounded worker logical-repository availability with restart-safe migration, repository-aware routing and reuse, command-center onboarding/readiness, production-path synthetic fresh/reuse coverage, and controlled real local dogfood against the exact current head of public Nobodyworld/app-accounting-modular PR #126.

The target PR must not be modified or published to automatically. MCP, provider execution, browser/desktop/RPA workers, Docker-worker expansion, repository writes, automatic approval/publication/merge, releases, deployments, and production/public-internet claims remain outside this slice.

No planning blocker remains. Keep PR #139 draft, open, and unmerged throughout implementation. Final readiness requires local implementation and dogfood evidence, the complete protected matrix, ultimate-head hosted workflows, and a new connector review.

[Nobodyworld]

Implementation continuation checkpoint

Exact Switchboard state remains suitable for the large local implementation handoff:

main / merge base: 33a5836496fa933dd6aae65ec71238d1b5ac9772
branch: feat/trusted-workload-catalog-dogfood
planning head: dc33806e57edd8d0255b3f17c8379a482cf8ab31
PR: #139 — draft, open, mergeable, unmerged

The planning head remains fully green: Commitlint 31337683438 and CI 31337683431; lint, typecheck, test, security, Secrets audit, Link check, Coverage, and strict Browser UI tests succeeded.

The external target was rechecked immediately before handoff:

repository: Nobodyworld/app-accounting-modular
PR: #126 — open, draft, mergeable, unmerged
exact current head: 613cf89396c41a0ee3c3aa5886a55c264a38daf0
CI: 31330960255 — success
Container Smoke Compatibility: 31330960270 — success

The reviewed target Python quality contract at that exact head is python -m src.tools.quality_gate. Its fixed source-controlled commands cover Ruff lint and format, strict Mypy over the application/API/extensions/CLI surfaces, full pytest with branch coverage plus XML/JSON output, aggregate and critical-module coverage gates, focused accounting-control tests, pip check, hashed container-lock audit, development dependency audit, and repository secret scan.

Implementation must continue only on the existing branch and draft PR. Re-resolve the target PR head again immediately before live dogfood. The dogfood may validate the target exact SHA locally but must not comment on, modify, merge, close, retarget, or mark the target PR ready. Full logs and artifacts remain local; only bounded evidence belongs in Switchboard/GitHub records.

The next step is the local multi-file implementation, migration, real-worker tests, strict browser acceptance, and controlled external dogfood described by issue #138 and the living ExecPlan.