Skip to content

simplify(scout): remove Kev decision engine - #4871

Merged
ScriptedAlchemy merged 10 commits into
masterfrom
t3/remove-kev-systemone-1
Nov 13, 2026
Merged

ScriptedAlchemy merged 10 commits into
masterfrom
t3/remove-kev-systemone-1

Conversation

@ScriptedAlchemy

@ScriptedAlchemy ScriptedAlchemy commented Nov 12, 2026 •

Copy link
Copy Markdown
Owner

Context Scout now selects intent suggestions from deterministic observed tool actions. The Kev/SystemOne client, engine configuration, question/receipt APIs, intent-engine eval corpus, and their callers are removed. Retired persisted shapes are refused, and independent Codex-backed Scout authoring remains available.

The branch is reconciled with the current Tokio runtime and SQLite publication changes. Canonical dashboard/SDK contracts and the embedded ChatGPT bundle were regenerated and verified.

Validation on the reconciled tree:

  • Nine affected unit suites: 3,393 passed; two existing ignored tests.
  • Scout evidence integration: 4 passed; daemon Scout journeys: 19 passed; real hooks/LSP suite: 29 passed.
  • Strict Clippy: all 10 selected targets passed; all nine affected rustfmt targets passed.
  • All eight frontend test/typecheck targets passed: dashboard 2,322 tests, SDK 111, ChatGPT adapter/lifecycle/client 78.
  • contracts:generate, contracts:check, embedded build, and check:embedded passed; regeneration produced no further diff.

The entire bazel test //... suite was not run locally. The earlier fleet reconciliation timeout did not reproduce in the full 311-test session-memory suite; the new head still requires hosted CI confirmation.

@changeset-bot

changeset-bot Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 310dae0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

ScriptedAlchemy and others added 6 commits November 12, 2026 21:24
Staging-row release planned relations and entities as separate pages,
so even a three-row generation paid two fsync-backed commits. One
bounded page now admits relations first and then entities under a
single shared mutation-count and live-byte budget. Entities join a page
only after every remaining relation is admitted, which keeps the
relations-before-entities order, the per-page cancellation boundary,
and the idempotent retry of a partially released generation.

Both fsync-backed guarantees and the typed WAL failure handling are
unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Use the canonical native scheduler policy with a runtime owned by this
fixture. Preserve the async body, sampled cancellation points, retirement
joins, schema assertions, and existing time budget.
Joining the aborted serve task releases its exclusively owned listener.
Its ephemeral address may be reused by another parallel test, so a new
connection there cannot identify the cancelled server.

Retain the joined cancellation, the held-handler drop witness and the
original accepted socket's bounded EOF or reset assertion. Keep both
ten-second waits unchanged.
Preserve the reviewed schema fixture and loopback ownership assertions
while integrating the current master changes.
@ScriptedAlchemy
ScriptedAlchemy merged commit 625b136 into master Nov 13, 2026
18 checks passed
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