rhema-claw

4 Commits

Author	SHA1	Message	Date
vhaudiquet	00037993af	chore: carry dev.sh over — the claw+UI debug loop from the old tree android / debug (push) Successful in 2m20s Details android / release (push) Successful in 2m13s Details ci / checks (push) Successful in 1m4s Details ci / test (push) Successful in 37s Details ci / chart (push) Successful in 5s Details ci / docker (push) Successful in 1m22s Details ci / web (push) Successful in 13s Details ci / publish-edge-images (deploy/docker/claw.Dockerfile, rhema-claw) (push) Successful in 1m29s Details ci / publish-edge-images (deploy/docker/ui.Dockerfile, rhema-claw-ui) (push) Successful in 9s Details ci / publish-edge-chart (push) Successful in 4s Details Unchanged: the paths are root-relative, so the script works as-is in the standalone workspace.	2026-11-12 19:38:08 +01:00
vhaudiquet	95e2fcfd57	ci: port the rust, chart, docker, web and edge-publish gates from the rhema repository android / debug (push) Successful in 2m20s Details ci / checks (push) Successful in 2m1s Details ci / test (push) Successful in 57s Details ci / chart (push) Successful in 6s Details ci / docker (push) Successful in 1m44s Details ci / web (push) Successful in 13s Details android / release (push) Successful in 2m7s Details ci / publish-edge-images (deploy/docker/claw.Dockerfile, rhema-claw) (push) Successful in 1m25s Details ci / publish-edge-images (deploy/docker/ui.Dockerfile, rhema-claw-ui) (push) Successful in 10s Details ci / publish-edge-chart (push) Successful in 3s Details 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.	2026-11-12 19:29:32 +01:00
vhaudiquet	12ba97c8f1	build: resolve the image manifests from crates.io The Dockerfiles copied every framework crate's manifest because the old root workspace path-patched crossterm and carried in-tree resolution. The claw resolves from crates.io now, so the builder copies only the claw's own manifests, and the vendored-crossterm COPY (and its explanation) is gone.	2026-11-12 17:43:40 +01:00
vhaudiquet	552a76ba99	build: the claw stands alone The claw product (the daemon, the feed integrations, the client tools, and the web and android trees) extracted from the framework repository, keeping its history. The framework crates the product pulls are all on crates.io at 0.2.3, so the in-tree path dependencies became versions and the workspace resolves without the framework checkout.	2026-11-12 17:43:08 +01:00