vhaudiquet
95e2fcfd57
android / debug (push) Successful in 2m20s
ci / checks (push) Successful in 2m1s
ci / test (push) Successful in 57s
ci / chart (push) Successful in 6s
ci / web (push) Successful in 13s
ci / docker (push) Successful in 1m44s
android / release (push) Successful in 2m7s
ci / publish-edge-images (deploy/docker/claw.Dockerfile, rhema-claw) (push) Successful in 1m25s
ci / publish-edge-images (deploy/docker/ui.Dockerfile, rhema-claw-ui) (push) Successful in 10s
ci / publish-edge-chart (push) Successful in 3s
The android workflow came over with the tree; the rest of the old repo's CI was framework-shaped. What the claw needs is the rust gate (fmt, clippy, release build with the binary artifact, offline tests), the chart lint/render suite, the daemon image smoke test, the web bundle, and the edge + release publishing pair (latest/sha images on main, exact-version images and chart on a v* tag). Dropped on the way: the crates.io publish-order and claw-boundary checks (nothing here publishes to crates.io; the boundary is enforced by the tree layout now), the cloudflare wasm gate, the binary release legs, and the manifest/crates.io release jobs — all framework concerns that stayed in the rhema repository. Release tags are checked against the workspace version by a verify-tag job that the image legs wait on.