The vendored flare-ui was a Nov-4 snapshot with no recorded pin. Advance it to the furthest-along upstream branch: blueflare/flare-ui `sprint` (0e1f5a259faa), which is 247 commits beyond `main`, 71 beyond `next`, and already contains `next` in full. The scattered 1-3 commit leads on individual sp/* feature branches are unmerged side-work, not a more-ahead integration line, so vendoring one of those would drop the 247-commit integration; `sprint` is the single most-ahead branch. This brings sprint's flare-ui crate additions (form.rs, page.rs, page/, table.rs and the flare-ui-axum / flare-plugin-host crates) into the tree. Record the pin in flare-ui.lock so the next re-vendor is reproducible. alkane-os builds against it with no source changes: the console (console.rs) and the rest compile clean, clippy -D warnings is clean, and 183 lib + integration tests pass (including the dashboard schema tests, so the wschema model stayed compatible). Re-verified the live console on sprint: --serve-sim boots, the flare-ui shell and control pages render, and stop -> ambient:18000 -> start all succeed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BdKQBPjAXpCwmigUov5eQk
6 lines
217 B
Plaintext
6 lines
217 B
Plaintext
# Vendored flare-ui pin. Re-vendor with scripts, never edit the tree by hand.
|
|
repo = https://gitea.bluefla.re/blueflare/flare-ui
|
|
branch = sprint
|
|
commit = 0e1f5a259faa32798bbb9ff3fedaa0b5faf5302d
|
|
vendored = 2026-11-10
|