Skip to content

D2 step 2: the kernel's proxy splits by concern; failover is the kernel's route - #546

Closed
MattJackson wants to merge 1 commit into
p6-d2-kernelfrom
p6-d2-step2
Closed

MattJackson wants to merge 1 commit into
p6-d2-kernelfrom
p6-d2-step2

Conversation

@MattJackson

Copy link
Copy Markdown
Collaborator

D2 step 2, stacked on #526 (base p6-d2-kernel). No predev hop runs on this base.

What moves

  • proxy/ is split by concern:
    • ingress/errors.rs gets the error envelope, plus ingress_error and auth_failure_status_and_kind moved verbatim. D2-PROTO owns those two functions from here.
    • egress/upstream.rs gets the upstream client, its dispositions, the buffer cap and the RTT histogram.
    • hooks/taps.rs (git-detected rename of proxy_vocab.rs) gets the stage taps.
  • failover/ becomes crate::route, beside route_tables (spec Part 3 l.637: "KERNEL | route (pool walk, member, breaker)").
  • MAX_POOL_MEMBERS moves to crate::config. store/planes.rs is untouched; it dies in step 4.
  • The callers (94 files), the config-schema and response-header gate paths, the host-series catalog source and the config-surface evidence refs all follow the new paths.

Row 82: 24 production files (plane_host 20, proto 3, store/planes 1). It was 27 at #526 and 28 at the start.

Proof (Latchkey)

Check Result
fmt, check (all features), check (no default features), clippy (all features), clippy (default) 0
cdylibs: frame, driver, example 0
core-admin, connector, a2a, voice 0
root tests 0
cargo test -p busbar --bin busbar 634 passed, 0 failed
clippy -p xtask 0
gates config-schema and response-header, plus --selftest of each 0 at head, 0 at base

Two reds, both also on the base:

  • kernel root_key_spelling: the llm lane's 081803d (auth/inbound.rs), reported to that lane.
  • the busbar-mcp --lib test build fails on its testkit / register_test_protocol imports.

…el's route

proxy/ is gone. Its pieces land where their concern lives:
- ingress/errors.rs: the error envelope, ingress_error, auth_failure_status_and_kind, the
  route-policy headers and the translate-body cap re-export (the two error functions move
  verbatim; D2-PROTO owns them from here).
- egress/upstream.rs: the upstream client, its dispositions, buffer cap and RTT histogram.
- hooks/taps.rs (renamed from proxy_vocab.rs): the stage taps and their content cap.

failover/ becomes crate::route beside route_tables (spec Part 3: "KERNEL | route (pool walk,
member, breaker)"); MAX_POOL_MEMBERS moves to crate::config. Callers, the config-schema and
response-header gates and the host-series catalog follow the new paths.

Row 82: 24 production files (plane_host 20, proto 3, store/planes 1), from 27.
@github-actions

github-actions Bot commented Oct 7, 2026

Copy link
Copy Markdown

promote into p6-d2-kernel: NO VERDICT @aad0521a7

The hop ended without writing a verdict (runner lost, timeout, cancel, or it died before the engine judged): preflight: failure at step Run cargo run --locked --release --no-default-features -p busbar-release-cli --bin busbar-release -- ci preflight; publish: runner lost at step Run bash "$GITHUB_WORKSPACE/busbar-release/ci/promote/fallback.sh", Post Run actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1.

No failing-test list exists for this run. Run: https://github.com/GetBusbar/busbar/actions/runs/37607981446 . Re-run the hop, or read the job's step list in the run page.

@MattJackson

Copy link
Copy Markdown
Collaborator Author

Closed (dead, not superseded): this D2 step is not on predev, and its base DEL (p3-flip-llm-del, under #526) was deleted unmerged. By ruling, D2 lands after #464 and DEL. That sequencing now waits as task draft-546-d2-kernel-stack (After: #464), which starts from the bundles. Branch bundled at ~/Library/Caches/busbar-release/salvage/GetBusbar_busbar-p6-d2-step2-1791610783.bundle (DEL and the never-pushed ripples onto it are in GetBusbar_busbar-p6-d2-stack-local-ripples-and-del-*.bundle) and deleted.

@MattJackson
MattJackson deleted the p6-d2-step2 branch October 10, 2026 06:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant