Seed agentplane local-hybrid slice docs and runtime layout

[mdheller]

Summary

Seed agentplane with the missing architectural spine for the first local-hybrid execution slice.

This PR does not replace the existing artifact schema work. It builds on it by:

• documenting the repo role
• defining the first end-to-end local-hybrid slice
• clarifying cross-repo ownership boundaries
• seeding stable target directories for gateway, capability registry, and worker runtime

Why

We had a real inspection gap: agentplane was initialized and had schema scaffolds, but lacked enough repo-level structure to cleanly target follow-on work.

This PR closes that gap and turns the repo into a reviewable execution-plane surface.

Added

• README.md
• docs/local_hybrid_slice_v0.md
• docs/repository_map.md
• gateway/README.md
• capability-registry/README.md
• worker-runtime/README.md

Existing work preserved and aligned

This repo already had:

• schemas/session-artifact.schema.v0.1.json
• schemas/promotion-artifact.schema.v0.1.json
• schemas/reversal-artifact.schema.v0.1.json
• schemas/bundle.schema.patch.json
• local runtime ignore conventions in .gitignore

The new docs explicitly align the first slice with those artifacts.

Next follow-on

• add typed gateway scaffolding
• add capability binding examples
• add worker runtime contract stubs
• align shared schema and fixture work with TriTRPC and socioprophet-standards-storage

[mdheller]

Reset note after repo-state census:

This PR looks complementary to, not competitive with, the already-landed receipt-path work on main:

• PR Add live receipt integration plan and reference emitter v0.1 #8 landed the live receipt integration plan + reference emitter
• PR Add receipt smoke-test path for GAKW hybrid warm trace v0.1 #9 landed the GAKW hybrid warm trace + smoke-test utility
• PR Seed control matrix v3 import lane #10 landed the control-matrix runtime import lane

Recommended handling:

1. Keep this PR as the architectural spine for the first local-hybrid slice.
2. Add explicit references/cross-links to the landed receipt-path artifacts so this does not read like a parallel lane.
3. Treat the receipt path as the first instrumentation/test harness for this slice, not as a separate doctrine stack.

Concrete suggestion: add a short section in docs/local_hybrid_slice_v0.md that points to docs/instrumentation/live_receipt_integration_plan.md and tools/receipt_smoke_test.py as the initial verification surface for the slice.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f43661a9d2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep execution lane consistent with worker endpoint

When requested_lane is provided, this code rewrites executionLane but always keeps the single binding["workerEndpoint"] value. For descriptors that advertise multiple lanes (for example local + tenant), requesting local currently returns a binding labeled local that still points at the tenant endpoint, which can route work to the wrong execution environment and produce incorrect policy/provenance signals. The resolver should either select lane-specific endpoint data or reject lane overrides when only one lane-specific binding exists.

Useful? React with 👍 / 👎.