docs(taylor01): add minimum-floor supporting doctrine

[cjarguello]

Summary

• add the minimum-floor supporting doctrine set behind the canonical Claw plan
• keep the Bootstrap mirror subordinate to the umbrella plan
• avoid expanding PR docs(taylor01): reconcile Claw plan to minimum-floor-first #81 beyond the canonical plan surface

Included

• taylor01_runtime_minimum_v1.md
• claw_v1_boundary_model_v1.md
• taylor01_operator_intake_supporting_surface_adapters_v1.md
• openclaw_operator_intake_dispatch_contract_v1.md
• phase4_return_sequence_post_taylor01_2026-03-12.md

Excluded

• phase3_execution_hq_evidence_pack_2026-03-31.md
• bootstrap_closure_gates_matrix_v1.md sequencing expansion

[cjarguello]

Taylor/docs baseline note:

The docs baseline now includes the Taylor01 reset context merged through BitPod-App/bitpod-docs PR #27 — Stabilize policies folder and compatibility shims, merge commit b2b9bf1.

For this PR, use current bitpod-docs/main as the source of truth rather than the earlier WIP policy/docs branch.

Relevant Taylor01 role guidance now reflected in docs:

• taylor01-core is the canonical runtime / product lane
• taylor01-skills is the portable substrate center
• bitpod-taylor-runtime is donor / legacy bridge evidence only, not current runtime authority
• BitPod-local doctrine remains proving-ground context, not final Taylor architecture

I am not editing this PR branch; this is only a coordination note so this thread can rebase/reconcile against the finalized docs baseline.

[cjarguello]

Transition/canon note before merge cleanup:

Live Taylor01 Linear project canon has moved beyond the older minimum-floor supporting-doctrine wording in this stacked PR. Current canon names taylor01-runtime as the execution/runtime repo and taylor01-mind as the long-term cognitive/memory/protocol repo. V1 now stays narrow around Mission Control, one primary executive agent, memory/execution, and native Telegram. Hermes is a near-term cognitive direction, not the active embodied runtime or v1 blocker. Discord is a later evaluation lane, not a v1 requirement.

Please treat this PR as historical/transition context unless the main thread intentionally rewrites it to match the runtime/mind split. Do not merge it as current canonical direction if it conflicts with the Taylor01 project description.