nordisk/facett

Downstream Falsett integration patches

These portable patches were prepared and checked in isolated checkouts. Apply them with this modified facett checkout beside the target repository. The knut and dwarves adapters use ../../../facett/facett-flow from their crate directories; Nornir uses ../facett/facett-flow from its root. Registry-only dependency updates and release publishing remain separate steps after the Falsett release.

On 2026-10-04 the reviewed Nornir patch was applied to the supplied ../nornir workspace and the knut patch to ../nordisk/knut. The dwarves patch remains a portable patch only. Nothing has been committed or published.

Facett's actual workspace manifest discovery now succeeds with the restored sibling sources. All eight wasm feature/installation guard tests pass against real cargo metadata output (three feature tests and five installation tests). The actual funnel-core checkout is now available, and the actual-workspace facett-flow --all-features check passes. Cargo has refreshed Facett's lockfile against the restored and reviewed sibling sources. Broader native/wasm builds are recorded separately in the verification record: the selected native component suites, demo library, flow wasm and wrapper wasm checks pass. A full Nornir check still stops before compilation at the absent holger/server/lib/Cargo.toml sibling dependency.

knut

• Patch: knut-flow.patch.
• Base: f1a9e617d09f4f47936e18a40b0225d1ae2eb922.
• Widens knut-pipelines' facett-pipeline requirement to >=0.1.19, <0.4, keeping the existing root git pins.
• Adds optional knut-bifrost/flow_adapter: delivery_graph, snapshot_chain, DeliveryRoute, FlowParts and caller-owned SnapshotInfo { id: i64 }.
• facett-flow explicitly enables skade: the real RoundOutcome is gated by that feature. SnapshotInfo does not exist upstream, so this adapter takes a documented oldest-to-newest input slice; cursor status follows ancestry order, never numeric snapshot-ID order. Rates use actual read+load duration, preserve zero throughput and leave missing or unmeasurable rates unknown.

From the knut root:

git apply --check /path/to/facett/integrations/knut-flow.patch
git apply /path/to/facett/integrations/knut-flow.patch
cargo test -p knut-bifrost --features facett-flow flow_adapter

Validation: four adapter tests passed using the actual adapter source and exact RoundOutcome, RoundReport and SinkReport declarations extracted verbatim from this knut revision. They cover counts, failure/lag statuses, rate calculation, unknown samples, source-to-sink positions, snapshot ancestry, graph validation and 100,000 routes (0.88 s in the measured debug run). Layout scales uniformly when necessary to remain inside Falsett's coordinate budget. This checks the pure adapter, not the full knut crate/dependency graph. The initial isolated full test reached a pre-existing resolver conflict: skade-aegir requires nornir-hash ^0.1.1, while knut's lock selects 0.1.0 via nornir-build-thing. No unrelated dependency pins were changed. The isolated harness was /private/tmp/knut-flow-adapter-validation.

dwarves

• Patch: dwarves-flow.patch.
• Base: de6d1b4d340937185573011ee854d9d0f7460863.
• Adds optional facett-flow and a brokkr::flow_adapter::run_graph adapter for the real Dag and RunReport, grouping by stage and preserving dependency direction and observed statuses.

From the dwarves root:

git apply --check /path/to/facett/integrations/dwarves-flow.patch
git apply /path/to/facett/integrations/dwarves-flow.patch
cargo check -p dwarves --no-default-features --features facett-flow

Validation: the patch applied cleanly to baseline copies and reproduced all three changed files byte-for-byte. Four isolated tests compiled the actual unmodified dwarves model/dag/history/runner/engine/trigger modules with registry jera 0.1.10. They cover topology, stages, validation, live statuses, unchanged geometry, foreign-run exclusion, empty/single graphs and a real failed-engine report with downstream skips. The initial full dwarves check stopped at its absent sibling draupnir manifest. That isolated checkout's complete build has not subsequently been certified by these adapter tests. The isolated command was cargo test --manifest-path /private/tmp/dwarves-flow-adapter-validation/Cargo.toml --test adapter.

Nornir

• Patch: nornir-flow.patch.
• Base: c64abdce90d14157a5ecbf5fe494aa2a959082c9.
• Adds the optional sibling facett-flow dependency to viz, a real BuildPlan adapter, persistent build-tab graph scenes and native GPU install/idle eviction.
• Hosts can supply plugin plans through set_build_plans; the descriptor path uses BuildThing::plan's default materializer. Runner status applies to the observed variant; unreported steps and artifacts carry no asserted status.
• BuildTabMsg wraps the existing BuildThingMsg with a From conversion. Dependency layout delegates to Facett's shared core and preserves Nornir's CrossRepoEdge facade.

From the Nornir root:

git apply --check /path/to/facett/integrations/nornir-flow.patch
git apply /path/to/facett/integrations/nornir-flow.patch
cargo check --offline --no-default-features --features viz --lib

Validation: the patch applied cleanly to a clone of the supplied baseline and reproduced all seven files byte-for-byte. A narrow harness passed 45 tests: four adapter tests, twelve BuildTab tests (ten existing and two new), two dependency layout parity/cycle tests, nine theme tests and all eighteen existing test_boot tests, with no exclusions. It compiles the changed Nornir source modules directly with actual edda build-thing 0.1.24 source and actual jobs/depgraph/Draupnir modules. Draupnir is the supplied 0.2 source at d7e6fde6ecd6dd9c6c74163191948e5e30664b85; isolated dependency manifests rewrite paths to available source or registry packages. This does not certify the complete native binary. The harness was /private/tmp/nornir-flow-validation.

The isolated validation paths are session-local evidence, not portable build instructions. The commands above each patch are the full checks to repeat once the downstream dependency environments are available.