chore(consistency): sync task status from DB [auto]

Updated by fix-consistency on 2026-07-25:
  - RAIL-K8S-WP-0001-T04: progress → wait

workplans/RAIL-K8S-WP-0001-bootstrap-and-wave1-import.md

@@ -0,0 +1,116 @@
+---
+id: RAIL-K8S-WP-0001
+type: workplan
+title: "Bootstrap rail-kubernetes and import the wave-1 contract"
+domain: financials
+repo: rail-kubernetes
+status: active
+owner: codex
+topic_slug: railiance
+created: "2026-07-25"
+updated: "2026-07-25"
+state_hub_workstream_id: "1f2254f5-a873-46fc-a77c-bc725eeaaeb8"
+---
+
+# RAIL-K8S-WP-0001 - Bootstrap rail-kubernetes and import the wave-1 contract
+
+## Goal
+
+Turn `rail-kubernetes` into the concrete home of the default Railiance
+execution rail.
+
+## Boundaries
+
+This workplan may bootstrap the repo, publish the initial declaration, and
+import the generic wave-1 contract.
+
+It must not:
+
+- absorb S2 substrate ownership from `railiance-cluster`
+- normalize workload-specific helper commands into the rail
+- pretend the migration is complete before compatibility shims exist
+
+## T01 - Establish the repo baseline and rail declaration
+
+```task
+id: RAIL-K8S-WP-0001-T01
+status: done
+priority: high
+state_hub_task_id: "9bab36db-e094-4e41-af76-b6bf5e73be78"
+```
+
+Create the baseline repo files, the initial rail declaration, and the first
+wave-1 contract summary.
+
+Acceptance:
+
+- baseline repo files exist
+- `declarations/rail.yaml` exists
+- the repo states its boundary with `railiance-cluster`
+
+2026-07-25: Created the initial repo baseline, declaration, and wave-1
+contract summary.
+
+## T02 - Import the reviewed generic contract material
+
+```task
+id: RAIL-K8S-WP-0001-T02
+status: progress
+priority: high
+state_hub_task_id: "148276a2-2e40-4d56-89dd-2930c5e4309c"
+```
+
+Bring the reviewed generic lifecycle docs, schema, examples, and helper
+surfaces into this repo in a migration-safe sequence.
+
+Acceptance:
+
+- the import sequence is anchored in the reviewed extraction map
+- imported material stays generic to the Kubernetes rail
+- the repo becomes a real home for the default rail rather than only a shell
+
+2026-07-25: Established the repo-local contract summary and explicit source
+import plan. Full import of docs, schema, examples, and helper surfaces is
+still pending.
+
+## T03 - Prepare the compatibility handoff from `railiance-cluster`
+
+```task
+id: RAIL-K8S-WP-0001-T03
+status: wait
+priority: medium
+state_hub_task_id: "18140d90-d10e-47fe-b7da-d454550466b1"
+```
+
+Define the thin compatibility path that keeps current operators functional
+while the extraction proceeds.
+
+Acceptance:
+
+- the compatibility path is explicit
+- current operators do not need a flag day
+- the retained S2 surface stays narrow and temporary
+
+## T04 - Register `rail-kubernetes` in State Hub and Fabric
+
+```task
+id: RAIL-K8S-WP-0001-T04
+status: wait
+priority: medium
+state_hub_task_id: "d78b5712-f305-4967-9034-9b9471633755"
+```
+
+Register the repo from classification and add it to the Fabric repository
+registry with rail-family metadata.
+
+Acceptance:
+
+- State Hub recognizes the repo and its workplan
+- Fabric recognizes the repo as `repo_family: rail`
+- ownership and primary contract metadata are visible
+
+2026-07-25: Registered `rail-kubernetes` in State Hub and generated
+`WORK-RECORDS.md` plus `.custodian-brief.md`. Added `rail-kubernetes` to
+`railiance-fabric/registry/railiance-repos.yaml` as `repo_family: rail` with
+`ownership_repo: railiance-cluster`. Live Fabric registry sync and Forgejo
+remote provisioning remain pending.