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
flare-ui
Shared UI and schema crates for FLARE and the Warden console. They provide schema forms, navigation, charts, page assets, editors and package validation.
- Licence: MIT.
- Branches:
mainandnext, like flare. Work branches fromnext. - Pinning: consumers vendor a tagged commit (
vN.N.N) and record it inflare-ui.lock. They never pin an untagged commit, and CI jobs hold no cross-repo credential. - Layout: worktree per branch,
flare-ui/.bareplus one folder per branch, kept in step with Gitea byscripts/sync-worktrees.sh(outside the repo). - Toolchain:
rust-toolchain.tomlpins one exact version. - Dash editor:
dash-editor/holds the importedflare-dash-editortree and its history (lane LD owns it). Its tests:cd dash-editor && node --test tests/*.test.mjs. - Flow builder:
flow-builder/holds the automation flowchart (model, form, view). Its tests:cd flow-builder && node --test tests/*.test.mjs. - Validation corpus:
corpus/(lane LB), described incorpus/README.md. - Crates and owners: see
OWNERS. Vendoring and tags:docs/vendoring.md.
Crates
| Crate | Role |
|---|---|
flare-ui |
Schema forms, read-only pages, navigation, chart islands, page assets and editor assets |
flare-ui-axum |
Authenticated-page SSE transport, replay, stream limits, poll responses and the d04 7.4 action routes; host contract |
wschema |
Schema document model, builder DSL, canonical JSON, hashes, lint L01 to L23 |
wschema-cli |
canon, hash, lint and corpus validate for fragment authors and CI; verify-lock and gen-lock for consumer locks (flare-ui.lock, gen.lock) |
wschema-gen |
Generators: the OpenAPI components.schemas of an effective schema and their splice into a template |
warden-sync |
Sync stamps, HLC, windows, digest and planner (d03), and the wire and value limits both ends share, with golden limit vectors (tests/vectors/limits-vectors.jsonl) each end replays |
warden-seal |
Per-Warden sealing (HPKE Auth): suite, info and aad builders, padding, kid, shared vectors |
wapp-core |
App package format, manifests, platform checks and validation |
wapp-pack |
Package creation, verification, signing, index and release guard CLI |
flare-plugin-abi |
Reserved plugin ABI placeholder |
wschema depends on serde, serde_json and sha2 only, and builds for
x86_64 and armv7-unknown-linux-musleabihf.
Checks
cargo fmt --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
scripts/check-owners.sh
scripts/vendor-selftest.sh
cargo test runs the JavaScript unit tests of the browser assets with node
(flare-ui#148): node --test tests/js/<file>.test.js in crates/flare-ui, for
actions, boot, chart, islands, live and page-live. A machine without node
fails those tests. A host that cannot run node sets FLARE_UI_SKIP_NODE_TESTS=1
to skip them. The skip is written to the test's stderr, which cargo shows only
for a failing test or with --nocapture, so a host that skips them runs those
six files with node elsewhere and records that run in its commit.
The chart browser checks run on Chromium and Firefox over plain HTTP, with CSP and real SSE samples. The live client documents typed chart props, server tier links, accessible latest values and named series events. The schema page contract covers authorized read-only snapshots, shared full/HX bodies and stable OOB fragments.
The shared crates also build for the panel:
cargo build --locked --target armv7-unknown-linux-musleabihf \
-p wschema -p warden-sync -p warden-seal -p wapp-core
The OpenAPI emitter's sample output passes an OpenAPI 3.1 validator
(openapi-spec-validator, not part of CI here; the consumer's CI runs it on
the real document):
cargo run -q -p wschema-gen --example openapi_sample > sample.yaml
openapi-spec-validator sample.yaml
Benchmarks for wschema (canonical JSON, hash, lint on a 140-setting
document): cargo bench -p wschema --bench canon_hash.