Commit graph Idunn/src
Author SHA1 Message Date
Meta Vens
057bdd5c6c B2-3d: status shows a survival-only record on a generation that no longer routes
cargo-mutants on the 3d diff missed `|| -> &&` in render_supervision: no
test held meters with only survival entries under an unrouted generation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-30 12:39:32 +02:00
Meta Vens
e9c718e073 B2-3d: the route actuation ceiling counts only Forward
Ruling 3d A (2026-09-30): the 12/h per-target route actuation ceiling
counts only Forward actuations (deploys). Survival actuations (continuity
restarts, rollbacks, withdrawals, admitted-route repairs) are recorded for
visibility in a separate TargetSupervision.route_survivals log (key 6,
newest 12 kept) and are never counted against the ceiling or refused by it.
A target whose continuity spent its six restarts can therefore always be
rescued by a deploy.

Each Survival path keeps its own bound: a continuity's actuations the
restart log and its doubling wait, an admitted-route repair the challenge
backoff, a deployment's rollback or withdrawal the Forward change it
undoes. A candidate whose route proof keeps failing now reloads at most
twice the ceiling per window (12 installs, each with its rollback) instead
of 12.

status prints the survival record beside the ceiling line.

TargetSupervision stays at v1 with the added slot: no installed Idunn has
written the record (B2 is merged, not installed).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-30 12:21:58 +02:00
Meta Vens
ed07241f34 B2 final: drop the merged history-ceiling test that counts in its own closure
continuity_gives_up_on_a_release_that_will_not_start came from main with the
old rule (three failed restarts per generation, counted from history). The
branch owns the ceiling in TargetSupervision meters now (six per window), and
the test exercised no production code: it filtered transactions in a local
closure and compared to the constant, which the meters changed.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 06:33:56 +02:00
Meta Vens
8b9ed0e8d9 B2 final: pass the pass's snapshot to the lost-race test that predates it
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 06:28:40 +02:00
Meta Vens
eceb742ea3 B2 final: an in-memory challenge wait ends with the write that outlives it
The wait spacing a challenge whose record failed to land was removed only
when a challenge record for that target landed. It now carries the stamp of
the target's stored records (generation, meters, transactions) as they were
when the record failed, and the supervision pass drops it as soon as the
stamp differs: any write for the target landing, or the target retired or
withdrawn, returns the schedule to the stored value. A wait can no longer
hold a drift repair after the disk recovers.

Soul's probes become tests named for the rules: one reload per wait for a
re-drifting fragment, a proved wait of one observation age, a failed wait
that follows the stored doubling, a lost race leaving no wait, the wait
ending on a landed write, the wait ending with its target. The reloads()
helper is gated to unix (its use of the route stubs broke the Windows
--lib --tests check). Comments on the wait field and the failed-challenge
record now say what the code does.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 06:26:04 +02:00
Meta Vens
cccfe8e174 x
# Conflicts:
#	src/control_plane.rs
2026-09-30 06:23:11 +02:00
Meta Vens
d83b1a9c95 B2 fix batch: give the stale-route test a wait that starvation cannot outrun
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 05:04:18 +02:00
Meta Vens
b6e78e5366 B2 fix batch: pin the in-memory wait against the attempt's start, not the clock after fifty laps
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 04:53:25 +02:00
Meta Vens
0703691790 B2 fix batch: widen the stale-route test's wait so load cannot expire it
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 04:49:33 +02:00
Meta Vens
05881ea8d8 B2 fix batch: say a failed challenge record once, not once per temp file name
The store error chain carries a fresh temp file name per attempt, so the
report-once key never matched twice. Report the root cause.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 04:31:48 +02:00
Meta Vens
74e7ed495e B2 fix batch: a lost record race is progress, a refused write is not
replace_generation now tells a lost compare-exchange (another writer moved the
store: the pass ends and re-reads) from a write the store refused.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 04:27:03 +02:00
Meta Vens
757e55be8f B2 fix batch: an unwritable store is not progress and not a hot loop
A supervision pass whose challenge record could not be written reported
progress, so serve() skipped its sleep, and the challenge wait lived only in
the store: a drifted fragment with a failing reload was reloaded every lap.
Progress is now a record that landed; the wait is also held in memory per
target until a record lands; the failed write is said once per target.

The stopped-restarting message says when the route ceiling reopens when the
ledger is full, so "free for a deployment" is true.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 04:15:49 +02:00
Meta Vens
76aaff1e71 B2 fix batch: the stateful routed world names its command kind
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 02:48:34 +02:00
Meta Vens
8447c22201 B2 fix batch: a continuity is survival, and survival runs uncounted
The route gate derives the charge from the transaction's command kind: a
continuity's preflight and install are Survival (never refused, counted), only
a deployment's are Forward. A Survival that cannot be recorded is logged and
proceeds; a Forward that cannot be recorded is refused. A proved route
challenge whose write is lost ends the pass like a failed one instead of
failing it. status() draws its target union from one function.

Tests: continuity through a full ledger, uncounted survival vs refused forward,
the second-failure wait, the lost proved-challenge write, each v3 route
supervision field, and the admitted-or-metered union. The routed world takes a
command kind, so the refusal tests run as deployments.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 02:44:43 +02:00
Meta Vens
ef6cfb177f B2 rework: pin the resume wait's clock-step guard; correct the actuator doc
cargo-mutants-style probe C26 (the resume backoff read without its longest
wait) survived: the clock-step test called is_waiting directly, not the resume
site. An Engine-level test now sets a real half-minute backoff, which holds,
and a day-ahead one, which is attempted.

docs/host-actuator.md said continuity gives up after three attempts; it is six
restarts inside an hour.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 01:53:38 +02:00
Meta Vens
b55bb97f46 B2 rework: the refused-preflight test drives the abort cleanup by steps
The resume backoff, not the ceiling, spaces the cleanup retries after the
abort is recorded; the test asserts the abort at once and then steps it out.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 00:43:29 +02:00
Meta Vens
bdcd23768b Abort cleanup test rows carry only the activation
The workload rows were refused by the fixture on grounds outside the
rule, so they were dropped instead of asserted. The workload operand of
the owed rule stays pinned by the method-level test.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 00:41:58 +02:00
Meta Vens
55f433eb2d B2 rework: read the unsettled meters for the stepped-back wait check
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 00:41:04 +02:00
Meta Vens
e7605efe26 B2 rework: a stepped-back clock is settled where the meter decides
live_entries only reads future entries as now, so a log that is never
written kept looking recent until the clock caught up: a refused route
actuation or an exhausted restart log stalled for the length of the step, not
one window. A refused forward actuation now writes the clamped log when it
changed, and a supervision pass settles the target's meters before deciding
from them, ending the pass with the write. The restart due time comes from the
raw last entry so the longest-wait guard is the one deciding a stepped-back
wait.

Also: the ported restart test tolerates an empty live set, the refused-preflight
test reads the transaction from history, and a held-record test no longer
depends on the host having no nginx.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 00:37:56 +02:00
Meta Vens
e7ee053427 Drop the workload-only rows from the abort cleanup test
A transaction holding a workload and no activation is refused by the
fixture before the cleanup rule is reached, so those rows could not
speak for the rule. The method-level owed test keeps the workload-only
case.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 00:36:31 +02:00
Meta Vens
0bb791d913 B2 rework: name the routed world's killable workload apart from the candidate's
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 00:33:35 +02:00
Meta Vens
8212b9d15d B2 rework: rebuild the tests on the routed world and the target meters
The route-proof world's hand-built promotion is deleted: the world runs over
stub host programs, so Routing installs and proves the route for real and
every former promote_by_hand is a real step. The salvage fixtures of the old
B2 are not ported.

New tests pin each ruling under its own mutation: a full ledger still admits
and counts every survival actuation, first deployments are metered, a refused
preflight starts no private-mount unit and fails at once with the reopen time,
the actuation log slides, a clock step stalls nothing past one window, a
failed challenge ends the pass instead of losing a CAS, a proved challenge
clears the degradation, both storms are bounded, restarts are spaced,
counted in the mint and read from the target's own log (unreadable history no
longer stops crash recovery), and the v3 lift is pinned over golden bytes cut
with the 583b2a7 encoder, refusing a record that shows retired meters.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 00:31:12 +02:00
Meta Vens
88ce30905f Judge the post-fencing abort test only on terminal shapes
The Pending post-fencing rows sat in a Fencing-phase transaction that is
refused for unrelated reasons, so the row could not say what it claimed.
Post-fencing rows now cover the recorded values a terminal abort carries.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 00:31:03 +02:00
Meta Vens
61842a3952 Pin the chunk-size line against vertical tab and carriage return
Rows for a vertical tab before an extension, a carriage return before an
extension, and a size line ending in one or two carriage returns, so a
wider trim than SP and HTAB, or a stripped trailing carriage return,
cannot be taken.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 00:17:27 +02:00
Meta Vens
36467153b5 An abort's recorded candidate cleanup is judged by candidate_cleanup_owed
The pre-fencing validator respelled the owed rule inline. Both abort
validators now compare against candidate_cleanup_owed, so the post-fencing
abort, which had no check on its recorded candidate cleanup, is held to
the same rule. One test drives both aborts through every activation and
workload row.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 00:17:23 +02:00
Meta Vens
76c7b13b33 B2 rework: per-target supervision, typed route gate, generation v4 (production)
A target's route actuations and continuity restarts are sliding logs in one
TargetSupervision record (idunn.target_supervision.v1), created by the first
charge so first deployments are metered. The route driver asks a
RouteActuationGate before every group of host mutations; Forward changes can
be refused with a typed RouteActuationRefused, Survival ones (restoring the
admitted or incumbent route) are always admitted and always counted.

Generation moves to v4 with a typed lift from v3 that retires keys 18 and 20,
refuses a record showing the retired meters were written, and adds last_error
at key 21. Continuity restarts are counted in the mint CAS against the
target's own log; the history scan and both carry compensators are gone. Any
write to a generation or to its target record ends that target's supervision
pass. A due time further ahead than its owner's longest wait reads as due.

Tests do not build in this commit; the next one rebuilds them.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 00:02:24 +02:00
Meta Vens
bf5347c370 The chunk-size line admits whitespace only before an extension
RFC 9112 7.1 allows whitespace before a chunk extension and nowhere
else. The reader trimmed both ends of the size, so " 3" and "3 " were
taken. It now splits at the first ';', trims trailing SP and HTAB only
when an extension follows, and leaves parse_digits as the digit
authority. Rows use an honest body so only the size line differs.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-29 23:40:11 +02:00
Meta Vens
5f8417589d Candidate cleanup owed is one method both abort intents share
The two-flag helper let either call site swap or fold an argument
unnoticed. DeploymentTransaction::candidate_cleanup_owed reads the
transaction itself, and a four-row table drives the method and both
intents.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-29 23:38:26 +02:00
Meta Vens
08d94ee61b Fetch blobs in bulk the way Git's lazy fetch does for a promisor remote
In a blob:none partial clone, fetching bare blob ids with --stdin made Git's
post-fetch connectivity check treat the id as a revision and fail with
"bad revision" / "did not send all necessary objects" against GitHub, which
broke a live deploy fetching a vendor gitlink's blob. Add
fetch.negotiationAlgorithm=noop, --recurse-submodules=no and
--filter=blob:none, the arguments Git's own lazy fetch uses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 21:13:22 +02:00
Meta Vens
f9cebb33d0 Pin the partial-clone bulk fetch arguments in the spy test
A file:// origin delivers an explicitly wanted blob with or without the
promisor-style flags, so the real-shape fixture cannot fail on the bug that
GitHub triggers. The spy test already records the bulk fetch line; assert
it carries fetch.negotiationAlgorithm=noop, --recurse-submodules=no and
--filter=blob:none. Fails on the current arguments.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 21:12:06 +02:00
Meta Vens
7f776ec3a6 Pin bulk_fetch_objects against a real blob:none partial clone
Every existing source-driver fixture uses an origin without
uploadpack.allowFilter, so --filter=blob:none is ignored, the clone is
full, and bulk_fetch_objects never has a missing blob to fetch. This
fixture advertises the filter, so the checkout really lacks the blob, and
checks delivery with GIT_NO_LAZY_FETCH=1 so only the bulk fetch can supply
it. It fails on the current fetch arguments.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 21:06:03 +02:00
Meta Vens
d3db58227a Define the frozen-source symlink limit on Windows so idunn-host builds
The constant was unix-only since 9475dfa while its uses are not, so the
Windows idunn-host has not compiled since S1. Found installing B3: Raven's
actuator (built 2026-09-11) cannot decode the new plan types.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 20:57:45 +02:00
Meta Vens
5c49646b81 B3 follow-up: find the cancelled redeploy by id, not by history order
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 19:39:55 +02:00
Meta Vens
d34f5dc3f9 wip: show the completion in the cancel test
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 19:38:28 +02:00
Meta Vens
8432d45bbe B3 follow-up: bound the chunked trailer loop, refuse signed numbers and spaced header names
Trailers draw on the header budget instead of an unbounded loop. Content-Length
and chunk sizes are digits only (RFC 9112), and a header name with whitespace
is refused. Pins found by cargo-mutants: partial trailer, exact bounds on all
three framings, one byte then stop, unterminated chunk from a peer that keeps
going. ChallengeFailure::Silent documents what it actually is.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 19:36:54 +02:00
Meta Vens
137e120ce9 B3 follow-up: cancel accepts a held pre-fence Deploy; test yield by direct supervision
Operator ruling 2026-09-30 (F4): an operator may cancel a held Deploy that has
not fenced. Nothing was fenced, so the incumbent is untouched; the pre-fencing
abort releases the target. Idunn itself still never aborts a held record: the
held_disagreement guard on the yield path is unchanged and pinned.

The P1b test now calls supervise_one_admitted_generation directly with the
redeploy in Warming over a dead held incumbent, with a positive control (the
same redeploy over a dead non-held incumbent yields).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 19:36:54 +02:00
Meta Vens
e8b44878b7 B3 fix: the over-bound header test must be over the bound
The previous commit's over-bound case used floor(bound / line) lines, which
can still fit under the bound once the status and Content-Length lines are
counted; the answer was accepted and the test failed. It now sends one whole
line more.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-29 18:23:11 +02:00
Meta Vens
4b3b86d863 B3 fix: pin the header bound at its edge and the chunked trailer loop
Two more mutants survived: the header-size bound was only tested far from its
edge, so doubling each line's cost went unseen; and the chunked trailer loop
was only exercised with a trailer present, so inverting it went unseen. The
bound is now tested one line inside and at its edge, and a chunked answer with
no trailer is read from a peer that keeps the socket open.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-29 18:19:07 +02:00
Meta Vens
d5669af352 B3 fix: pin what cargo-mutants found unpinned in the framed route reader
The header-size bound was tested only against answers that also stopped
short, so it never had to hold on its own; the interrupted-read retry was
exercised by no reader that could be interrupted. The header test now sends an
honest, whole answer whose headers alone exceed the bound, and a scripted
reader pins the retry and the silent/refused split at the Answer boundary.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-29 17:49:56 +02:00
Meta Vens
2f22dcac96 B3 fix: read a route answer by its framing, and judge a stopped peer one way
The HTTP challenge read to end of stream, so a peer that answered in full and
kept the socket open (or answered 404 and kept it open) read as silence. It
now reads by Content-Length or chunked framing, refuses any non-2xx status,
and refuses bytes that are not a CultNet frame.

One rule for both transports: a peer that sent no byte is silent; a peer that
sent some bytes and stopped is refused. A truncated TCP frame used to read as
silence; that pinned test now expects a refusal.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-29 17:13:37 +02:00
Meta Vens
477927509a B3 fix: a held generation mints no continuity, and nothing yields to a held record
A held, undeclared generation that died reached the continuity mint, which
copied the undeclared Expected, was held at once, and owned the target for
good: cancel refuses continuity, so the declaring redeploy could never freeze.
Supervision now reports a dead held generation once and leaves it down and
its target free. With no continuity minted over it, a declaring redeploy in
Warming no longer yields to one either.

The yield path also aborted a pre-fence Deploy blocker without reading its
hold, which is Idunn aborting a held record. It now leaves a held blocker
alone.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-29 17:13:36 +02:00
Meta Vens
86ee21dac5 B3 fix: pin what cargo-mutants found unpinned, delete what it found redundant
First cargo-mutants --in-diff pass over a61540b..aa1889b left 16 misses.

Deleted:
- the candidate challenge's own route-id check: rendering the Expected next
  holds the same binding, so it could never decide anything.
- odin_can_observe in advance_warming: is_odin && !(!is_odin || observed) is
  is_odin && !observed; two of the misses were operators in that detour.

Moved: which transactions are held for their evidence is now
DeploymentTransaction::held_disagreement, so "finished or aborting work is
never held" is a value with a test, not a local in resume_candidate.

Pinned: the admitted-generation topology refresh (taken once, then not
again), WarmingEvidence shape checks per source, the PresenceDisagrees text,
the plan's readiness declaration needing the shared-infrastructure kind, TCP
framed challenges (exact answer, bound, empty, non-CultNet, silence), RUDP
silence, and ChallengeFailure's text and source.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-29 15:24:45 +02:00
Meta Vens
aa1889b288 B3 fix: kill the three surviving mutants
Boot re-proof by tag: the held-generation test used receipts that still
re-proved cleanly (boot reads the current Odin authority, not the stored
one), so re-proving them passed. The receipts are now authentic but not
Ready, so only skipping them lets the store boot.

Config error as silence: the candidate path renders Expected first, which
parses the same endpoints, so the challenge's own parse is reached only from
the stable path. A new test drives that parse directly.

First-Odin gate by name: the stub can now answer a first-Odin Warming
challenge, and a stateful provider not named odin is accepted while a
stateful target named odin that provides nothing is refused.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-29 14:41:25 +02:00
Meta Vens
e11b457458 B3 fix: pin the route-proof rules, and delete guards another owner already holds
Tests for each rule the Soul pass found unpinned, each written to fail
under its own mutation:
- a stateful route-proof target through the Engine, Fencing to commit: the
  lease is prepared and granted, Ready is refused without the exact lease
  and recorded with it, boot re-authenticates the store at every stage and
  Odin is never read;
- Warming challenges once and then advances on every tick;
- a stateful candidate may not answer its Warming challenge active;
- a presence holds the write lease exactly when it is not warming, and is
  minted after its challenge;
- direct Warming evidence is bound to the bytes and digest it authenticated;
- candidate-vouched evidence is refused on a target Odin reports on;
- a pre-B3 transaction and a pre-B3 generation over a route-proof target are
  held and reported once, not stepped every tick, and not re-derived;
- a stored record with no declared readiness is held;
- Odin is the class OdinSelf, not the name "odin";
- admission refuses an undeclared recipe with a typed error, before the
  source is frozen; a recipe that declares its proof is planned;
- the driver's challenge failures: silence waits, every bad answer and every
  local configuration error is an error;
- the capacity shortfall is read as a typed PresenceDisagrees.

Deleted because another owner already holds them, so no test can reach them:
the Routing and commit "route-proof Ready evidence" ensures (validation
refuses a missing receipt, the hold refuses the other party's), the write
lease comparison's warming arm (the authenticator refuses a warming presence
that claims a lease), and the direct-Warming refresh check (rehydration
authenticates the recorded answer as Odin's first).

Engine.source is a SourcePort, the seam the admission test needs.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-29 13:32:42 +02:00
Meta Vens
6ea824b5a9 B3 fix: readiness class comes from the recipe alone
ReadinessClass::of is the only class authority. A target whose recipe
declares neither a route nor an Odin dependency, and does not provide the
rendezvous, has declared no way to prove readiness: of() returns a typed
UndeclaredReadiness naming the target, and admission refuses it after plan
compile, before anything is frozen or installed. The OdinCorrelated fallback
for an unrouted target is gone.

The evidence tag no longer decides the path. Boot re-authentication and
admitted-topology refresh choose by class; a stored transaction or admitted
generation whose evidence was vouched for by the other party than its
Expected requires is a typed ReadinessDisagreement, reported once and held,
not a step that errors every tick. Nothing re-derives around it.

"Is this Odin" is the class OdinSelf, not the name "odin": validation,
warming, the Odin authority lookup and the direct-warming checks read the
class. canonical_sha256 on WarmingEvidence and the token's unread evidence
field are deleted.

A bad answer to a direct challenge is an error. The driver splits its
failures into ChallengeFailure::Silent (refused, dropped, hung up, timed
out) and ::Refused (a malformed, foreign, oversized or non-raw answer, or a
local configuration error); only Silent waits. The capacity/disagreement
shortfall is returned as a typed PresenceDisagrees, not flattened to prose.

Odin-driven fixture worlds declare the Odin dependency in Expected and the
correlation they sign names its provider.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-29 13:12:46 +02:00
Meta Vens
5ca7760fdd WIP B3: pin route admission past the gate 2026-09-29 11:06:25 +02:00
Meta Vens
4dcdd3608c WIP B3: route admission test 2026-09-29 11:03:47 +02:00
Meta Vens
54507060a5 WIP B3: pin the state rules, the lease refresh and boot re-authentication 2026-09-29 11:02:06 +02:00
Meta Vens
b9864b5041 WIP B3: Odin-providing target is driven through the engine 2026-09-29 11:00:47 +02:00
Meta Vens
66fda86d8f WIP B3: two private ports in the routed world 2026-09-29 10:56:26 +02:00