docs(taylor01): reconcile Claw plan to minimum-floor-first

[cjarguello]

Summary

• reconcile the retained Taylor01 Claw umbrella plan to the minimum-floor-first ordering
• record the live Linear alignment and updated issue hierarchy
• add checklist-style guidance so the active plan can be followed operationally

Included

• update linear/docs/process/taylor01_claw_v1_umbrella_plan.md
• update linear/docs/process/taylor01_claw_v1_linear_issue_packet.md
• update linear/docs/process/taylor01_backlog_seed_v1.md

Linear alignment

• BIT-198 — Plan: Taylor01 runtime boundary and Claw-direction architecture remains the single architecture owner
• BIT-205 — Define Taylor01 operator intake and supporting surface adapters is now in Taylor01 Phase 4 under BIT-198 — Plan: Taylor01 runtime boundary and Claw-direction architecture
• BIT-214 — Taylor01: lock minimum real-Taylor runtime contract through BIT-218 — Taylor01: define future dedicated repo extraction trigger for Claw are parented under BIT-198 — Plan: Taylor01 runtime boundary and Claw-direction architecture
• BIT-113 — Phase 3 evidence pack and HQ go/no-go is now the explicit Phase 3 closeout child under BIT-104 — Execute Mac Mini execution-HQ bootstrap for NemoClaw runtime
• BIT-220 — Plan: Normalize T3 local-workspace zone taxonomy and lean-profile semantics and children remain Bootstrap cleanup/meta framing

Retained plan surfaces

• repo canon: /Users/cjarguello/BitPod-App/bitpod-tools/linear/docs/process/taylor01_claw_v1_umbrella_plan.md
• Linear project doc: Taylor01 as Claw on mini-01 — Active minimum-floor-first plan

[cjarguello]

I can't review my own PRs... @chatgpt?

[cjarguello]

@taylor-01 can you do QA_Review QA?

[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 wording used by this PR stack. 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 preserve this PR only insofar as it remains useful transition/context material. Do not let it override the newer runtime/mind split or Mission Control + native Telegram v1 direction.