stacktrace-cli 0.2.2__tar.gz → 0.3.0__tar.gz

{stacktrace_cli-0.2.2 → stacktrace_cli-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: stacktrace-cli
-Version: 0.2.2
+Version: 0.3.0
 Summary: CLI for Stacktrace — Detection and Response platform for AI Agents.
 Project-URL: Homepage, https://stacktrace.ai
 Author-email: "Stacktrace AI, Inc" <founders@stacktrace.ai>
@@ -126,14 +126,15 @@ because it is installed.
 ## What leaves your machine
 
 Two of `detect`'s three stages run entirely locally and need no model or
-credential. The third sends flagged sessions to the agent's *own* CLI — the
-provider that produced the transcript, never a different one — capped by
-`--budget`; `--no-escalate` turns it off and leaves the two local stages.
+credential, and they are the two a bare `detect` runs. The third sends flagged
+sessions to the agent's *own* CLI — the provider that produced the transcript,
+never a different one — and runs only when you pass `--reasoning`, capped by
+`--budget`.
 
 `sessions` omits prompts, tool arguments and results unless you pass
 `--include-content`. `monitor` binds to loopback only, refuses a non-loopback
-address rather than warning about it, and escalates nothing unless `--escalate`
-is given.
+address rather than warning about it, and analyses nothing with a model unless
+`--reasoning` is given.
 
 ## Status
 

{stacktrace_cli-0.2.2 → stacktrace_cli-0.3.0}/README.md

@@ -101,14 +101,15 @@ because it is installed.
 ## What leaves your machine
 
 Two of `detect`'s three stages run entirely locally and need no model or
-credential. The third sends flagged sessions to the agent's *own* CLI — the
-provider that produced the transcript, never a different one — capped by
-`--budget`; `--no-escalate` turns it off and leaves the two local stages.
+credential, and they are the two a bare `detect` runs. The third sends flagged
+sessions to the agent's *own* CLI — the provider that produced the transcript,
+never a different one — and runs only when you pass `--reasoning`, capped by
+`--budget`.
 
 `sessions` omits prompts, tool arguments and results unless you pass
 `--include-content`. `monitor` binds to loopback only, refuses a non-loopback
-address rather than warning about it, and escalates nothing unless `--escalate`
-is given.
+address rather than warning about it, and analyses nothing with a model unless
+`--reasoning` is given.
 
 ## Status
 

{stacktrace_cli-0.2.2 → stacktrace_cli-0.3.0}/docs/adrs/0004-three-stage-detector.md

@@ -5,6 +5,8 @@ status: accepted
 date: 2026-08-27
 supersedes: null
 superseded-by: null
+amends: null
+amended-by: 0029
 ---
 
 ## Context

stacktrace_cli-0.3.0/docs/adrs/0029-stage-three-returns-to-opt-in.md

@@ -0,0 +1,115 @@
+---
+id: 0029
+title: Stage three returns to opt-in
+status: accepted
+date: 2026-09-09
+supersedes: null
+superseded-by: null
+amends: 0004
+amended-by: null
+---
+
+## Context
+
+ADR-0004 was amended on 2026-09-03 to default `--escalate` **on** for
+`stacktrace detect`. The reasoning was sound and the amendment said so plainly:
+a stage nobody turns on never runs, and rules that depend on it — `injection-
+marker` above all — can only ever be evaluated against zero verdicts. It also
+named its own exit: *"Revisit once there is a measured escalation rate and
+verdict yield to argue from; if the yield does not justify the spend, the
+honest move is back to opt-in rather than a narrower cap."*
+
+What forces the revisit now is not the yield. It is that the default was only
+ever changed in one of the three places that carry it, and the other two — plus
+everything we publish — kept saying the opposite:
+
+| Surface | Default |
+| --- | --- |
+| `run_detector()` | `escalate=False` |
+| `stacktrace monitor` | `False` — *"a page left open is the wrong place for that to be implicit"* |
+| `remote sync detect` | `False` (ADR-0023) |
+| `stacktrace detect` | `True` |
+
+The published quickstart tells a new user to run `stacktrace detect
+--no-escalate`, annotated *"# Investigate without model escalation"* — a
+documented first command whose only purpose is to undo the default. The site's
+data-handling section makes the same promise in prose: *"Start with detection
+that doesn't send session content to a model."* `docs/plans/004-detector.md`
+still describes the stage as opt-in. One surface out of four, contradicted by
+its own documentation, is not a default; it is a divergence.
+
+Be honest about the evidence this ADR does **not** have. The escalation rate is
+low — an audit on 2026-09-02 measured 3 escalations across 635 sessions, 1 on
+evidence and 2 sampled — but that audit predates the amendment and so describes
+behaviour under the opt-in default it is being used to restore. Verdict yield,
+the other half of what ADR-0004 asked for, has not been measured. Stage 3 has
+also still never run against a real analyzer: the `live_cli` test is opt-in and
+deselected. So this is not the evidence-based revisit ADR-0004 anticipated. It
+is a consistency and consent decision taken ahead of that evidence.
+
+## Decision
+
+`stacktrace detect` defaults `--escalate` off, matching `run_detector`,
+`monitor` and `sync detect`. A bare `stacktrace detect` sends no session content
+off the machine.
+
+Two things travel with it. The verdict cache is no longer gated on `escalate`:
+`run_detector` already states that a verdict already paid for is an answer this
+run *has*, and that `escalate` governs whether new ones may be commissioned, not
+whether old ones may be read — `cli.py` contradicted that, and flipping the
+default without fixing it would have made every stored verdict silently
+unreadable on the default path. And a run that declines to escalate still counts
+and names the sessions that qualified, as `reasoning_not_requested`, so a run
+without stage 3 does not read as a clean one.
+
+## Alternatives considered
+
+- **Leave it on and fix only the docs.** Rejected: the quickstart, the
+  data-handling copy and the plan all describe opt-in, and three of four code
+  surfaces implement it. Changing four things to match one is the wrong
+  direction, and the one is the surface that spends the user's money.
+- **Keep it on until verdict yield is measured, as ADR-0004 asked.** Rejected on
+  consent rather than evidence: the measurement requires a bare `detect` to keep
+  sending transcript content to a provider by default, and the same measurement
+  is obtainable from users who opt in. The amendment accepted that cost
+  deliberately; what it did not anticipate is that we would simultaneously
+  publish the opposite promise.
+- **A narrower cap instead of opt-in.** Rejected by ADR-0004 itself, in advance:
+  *"the honest move is back to opt-in rather than a narrower cap."*
+- **Prompt interactively on first run.** Rejected: `detect` is scriptable and
+  runs unattended; a prompt makes the non-interactive path either hang or pick a
+  default, which is this decision again with extra machinery.
+
+## Consequences
+
+A bare `stacktrace detect` is now local plus the osv.dev coordinate lookup, and
+nothing else leaves. That is the promise the site already makes, kept.
+
+The cost is the one the amendment identified and it returns in full: stage 3
+runs only when asked, so verdict yield and the rules that depend on it stay
+unmeasured unless we go and measure them. That work does not disappear — it
+moves from "collected passively from every user" to "collected deliberately",
+and it should be done, because `injection-marker` cannot be evaluated at all
+without it.
+
+Watch for the stage going dark again. `reasoning_not_requested` in the reasoning
+accounting is the signal: if it is the dominant outcome across real runs for a
+release or two, the stage is not being reached and the rules behind it are still
+untuned. That is the same failure the 2026-09-03 amendment reacted to, and the
+answer will need to be something other than flipping the default a second time.
+
+Users relying on the implicit default silently lose stage 3. `--no-escalate`
+keeps working, so no invocation breaks; the release note carries the change.
+
+## When to revisit
+
+- **Verdict yield gets measured** and justifies the spend — then this is a
+  candidate to revert, but with the docs and the other three surfaces changed in
+  the same commit, which is what went wrong the first time.
+- **`reasoning_not_requested` dominates** real runs for two releases, per above.
+- **Stage 3 runs against a real analyzer** and the `live_cli` test stops being
+  deselected — until then the default-on path was shipping the least-validated
+  stage.
+- **The escalation stops costing the user.** The whole argument is that the
+  stage spends someone else's quota and crosses a content boundary. A stage that
+  did neither would not need to be asked for.

{stacktrace_cli-0.2.2 → stacktrace_cli-0.3.0}/docs/adrs/INDEX.md

@@ -61,3 +61,4 @@ supersedes anything yet.
 - [0025](0025-a-denied-call-is-activity-never-an-invocation.md) — **A denied call is activity, and never an invocation.** ADR-0017 makes a declined repeat a stall while `outcome.py` keeps a denied call out of every count, so a denied-only session produced a finding with no activity and the Cloud rejected the whole run; a separate `denied` counter resolves it without either rule bending, and coverage keeps summing `invocations` alone. Read before changing what `activity[]` counts, or before folding `denied` into a coverage-like ratio.
 - [0027](0027-a-finding-may-name-what-it-could-not-place.md) — **A finding may name the component it could not place.** Narrows ADR-0006 constraint 3 for one field: an unplaced subject carries the name the session addressed it by, never as an identity. Read before removing a name from a finding on trust-boundary grounds, or before widening this to a second field.
 - [0028](0028-the-console-shows-what-it-placed.md) — **The console shows what it placed, and states no coverage.** Unplaceable rows, the `N/M placed` header fraction and the red on refusals are gone from `stacktrace monitor`: an unplaced row names no component, and `outcome.py`'s rule about a denied call makes reddening one the page contradicting its own counters. The snapshot contract, the upload and every rule are unchanged. Read before adding a page-side filter, before restoring a coverage ratio to the console, or if `unsanctioned-mcp-tool-use` returns.
+- [0029](0029-stage-three-returns-to-opt-in.md) — **Stage three returns to opt-in.** Amends ADR-0004: `stacktrace detect` defaults `--escalate` off, matching `run_detector`, `monitor` and `sync detect`, all of which never changed — the 2026-09-03 amendment landed in one of four surfaces while the quickstart, the data-handling copy and `plans/004` kept promising opt-in. Taken on consistency and consent, not on the verdict yield 0004 asked for, which is still unmeasured. The verdict cache is ungated from `escalate` in the same change. Read before changing an escalation default, or before arguing stage 3 should be on again.

{stacktrace_cli-0.2.2 → stacktrace_cli-0.3.0}/docs/plans/007-detection-upload.md

@@ -243,8 +243,8 @@ rewrite*.
 - [x] **Step 1: Keep `sync endpoint`'s side-effect order.** Load config, refuse
   if unconfigured, client, replay spool, **detect**, register, upload per kind.
   Detecting before registering keeps a failed run from creating an asset.
-- [x] **Step 2: `--escalate` defaults off**, the inverse of `stacktrace detect`
-  (ADR-0023).
+- [x] **Step 2: `--escalate` defaults off** — a scheduled unattended run must
+  not spend provider quota or cross a content boundary implicitly (ADR-0023).
 - [x] **Step 3: `--dry-run` prints NDJSON from the same builder.**
 - [x] **Step 4: Cap evidence, refuse everything else.** Keep `evidence[0]` —
   the anchor the Cloud identifies a call-scoped detection by — and order, with

{stacktrace_cli-0.2.2 → stacktrace_cli-0.3.0}/docs/plans/008-monitor.md

@@ -177,7 +177,7 @@ def analyse(
     return Analysis(run=run, view=acquired.view, window_start=window_start, window_end=window_end)
 ```
 
-- [x] **Step 4: Rewire `cli.py`'s `detect`.** Replace the three calls with one `analyse(...)`; keep the `try/except ValueError → ClickException` around it and the `VerdictCache(default_directory()) if cache and escalate else None` argument. Keep `_parse_since` as a thin alias if anything else imports it; delete it if nothing does.
+- [x] **Step 4: Rewire `cli.py`'s `detect`.** Replace the three calls with one `analyse(...)`; keep the `try/except ValueError → ClickException` around it and the `VerdictCache(default_directory()) if cache else None` argument — the cache is opened whenever `--cache` allows it and never gated on `escalate`, which governs whether new stage-3 work may be commissioned and not whether a verdict already paid for may be read. Keep `_parse_since` as a thin alias if anything else imports it; delete it if nothing does.
 
 - [x] **Step 5: Rewire `sync_detect.py`'s `_collect_detect_run`.** One `analyse(...)` call; keep `SyncError` translation, keep the working-directory collection and the per-kind activity walk, and read `window_start`/`window_end`/`collection_failures` off the `Analysis` instead of computing them.
 

stacktrace_cli-0.3.0/docs/releases/v0.2.3.md

@@ -0,0 +1,102 @@
+# 0.2.3 — stage three is opt-in
+
+`stacktrace detect` no longer sends anything session-derived off your machine
+unless you ask it to. The third stage — the one that hands flagged sessions to
+the agent's own CLI — is now behind `--escalate`, which is what the quickstart,
+the data-handling page and three of the four code surfaces already said it was.
+Alongside it, a fix worth reading if you installed with `install.sh`: `correlate`
+was reaching whichever OpenACA your PATH happened to name rather than the one
+this package pins.
+
+## Highlights
+
+- **`stacktrace detect` defaults `--escalate` off.** A bare run is the two
+  stages that need no model and no credential, plus the osv.dev advisory
+  lookup, which sends package coordinates only. `--escalate` turns the third
+  stage on and `--budget` still caps it. The default had been on since
+  2026-09-03 while `run_detector`, `stacktrace monitor` and `remote sync detect`
+  all defaulted it off and the published quickstart told new users to pass
+  `--no-escalate`; one surface out of four, contradicted by its own
+  documentation, was a divergence rather than a default. ADR-0029 records the
+  decision and is explicit that it is a consent decision taken ahead of the
+  verdict-yield evidence ADR-0004 asked for, which is still unmeasured.
+
+  A run that declines to escalate is not a clean run. Sessions that qualified
+  are counted in the reasoning accounting as `reasoning_not_requested`; the
+  session ids are in `--format json`, not the text output, which aggregates
+  them under the reason.
+
+- **A verdict you already paid for is readable on the default path.** Both
+  `detect` and `remote sync detect` built their verdict cache only when
+  escalation was on, so with the new default every stored verdict would have
+  gone unread and the same sessions would have been billed twice on the next
+  `--escalate` run. `run_detector` has always held that the flag governs whether
+  new verdicts may be commissioned, not whether old ones may be read; the two
+  call sites disagreed with it. An exhaustiveness test now covers every cache
+  construction site rather than the two that were found by hand.
+
+- **`correlate` runs the OpenACA this package pins.** Acquisition invoked the
+  bare name `openaca`, a PATH lookup — and `uv tool install stacktrace-cli`,
+  which is what `install.sh` runs, links only the `stacktrace` entry point, so
+  the pinned OpenACA sat one directory away, reachable but unnamed. A machine
+  with a stale global copy silently scanned with the wrong version; a machine
+  with none got a bare `FileNotFoundError`. `stacktrace --version` could not
+  reveal it, because it reports the metadata inside the environment while the
+  subprocess ran something else. The console script is now located through
+  `importlib.metadata`, authenticated against the digest its own install
+  recorded, and fails closed with a legible error where ownership cannot be
+  established. Verified against four real install topologies. The ADR-0007 seam
+  is unchanged.
+
+- **One default, stated once.** The escalation default had also drifted into
+  `docs/specs/detector.md`, `docs/specs/detection-upload.md`, test descriptions,
+  wrapped help text, and `docs/plans/008-monitor.md`, which still instructed the
+  cache gate this release removes. A test now reads the active specs, plans and
+  help text and fails on a stale wording, in any of the three names the repo
+  uses for the stage.
+
+- **The console names the log column `Agent Session Trace`,** dropping the
+  third word from `Agent Session Log Trace` — session, log and trace were three
+  words for one thing. The one-item legend above the columns (`MCP = a link to
+  an outside service`) is gone: an MCP row already carries its category tag and
+  names the server it reached.
+
+- **`detect` stops printing the per-reason "Could not settle" breakdown.** It
+  listed internal reason ids — `mcp_transport_unavailable` dominates on a normal
+  machine — at a reader who cannot act on them one call at a time. The unsettled
+  count stays in the summary line, `--format json` still carries every `Unknown`
+  whole with its spans and detail, and the reasoning stage still names its own
+  outcomes.
+
+## Install
+
+`uv tool install stacktrace-cli==0.2.3` or `pip install stacktrace-cli==0.2.3`.
+
+## Compatibility
+
+**One behaviour change, and the patch version does not signal it: `stacktrace
+detect` no longer escalates by default.** If you relied on a bare `detect`
+reaching stage 3, pass `--escalate` to restore it. Nothing breaks — the
+`--no-escalate` you may already be passing still means what it meant — but a
+default run now produces no reasoning-stage findings, and sessions that would
+have been analysed appear as `reasoning_not_requested` instead. `monitor` and
+`remote sync detect` are unaffected; they already defaulted off.
+
+If you had accumulated verdicts from earlier `--escalate` runs, they are served
+again on the default path rather than ignored, so a `detect` after upgrading may
+report reasoning findings without spending anything.
+
+Text output changes in two places: the `Could not settle:` block is gone, and
+the reasoning accounting's not-requested row names a flag rather than a reason
+id. `--format json` is unchanged — no field added, removed or renamed — and the
+upload payload is untouched, so anything parsing either sees what 0.2.2 served.
+
+On the console, the log column is renamed and the legend line is removed. No
+rule, finding, severity or payload field moves.
+
+If `install.sh` put stacktrace on your machine and you had separately installed
+or upgraded OpenACA to work around a scan failure, that workaround is no longer
+needed; the pinned 0.6.0 is what runs now.
+
+Still pre-alpha, with no back-compat hedging: interfaces can change between
+releases without a deprecation window.

stacktrace_cli-0.3.0/docs/releases/v0.3.0.md

@@ -0,0 +1,53 @@
+# 0.3.0 — the third stage is asked for by name
+
+`--escalate` is now `--reasoning`. The old name described the pipeline's own
+mechanic — stage two promoting a session to stage three — rather than what you
+get for it, which is a reasoning model reading the session. The flag now says
+that, on `stacktrace detect`, `stacktrace monitor` and `remote sync detect`
+alike.
+
+**This release renames a flag and two JSON fields with no aliases.** Everything
+you need to change is in the table below; nothing else about the pipeline moved,
+and the defaults are exactly what 0.2.3 shipped.
+
+## What to change
+
+| 0.2.3 | 0.3.0 |
+| --- | --- |
+| `detect --escalate` | `detect --reasoning` |
+| `monitor --escalate` | `monitor --reasoning` |
+| `remote sync detect --escalate` | `remote sync detect --reasoning` |
+| `--no-escalate` | *(nothing — omit `--reasoning`)* |
+| `summary.escalated` | `summary.reasoning_requested` |
+| `unknowns[].escalated_on` | `unknowns[].reasoning_reasons` |
+| `POST /api/escalate` | `POST /api/reasoning` |
+
+**If you typed `--no-escalate`, ignore what the CLI suggests.** Click offers
+`--no-cache` as the nearest match, which is the wrong flag and an expensive one
+to take: it disables the verdict cache, so a run re-buys answers you have
+already paid for. There is no replacement for `--no-escalate`. Stage three has
+been opt-in since 0.2.3, so leaving `--reasoning` off is the whole of it.
+
+## Highlights
+
+- **`--reasoning` is a plain flag, not an on/off pair.** `--no-reasoning` does
+  not exist, because there is nothing to turn off: stage three is opt-in on all
+  three commands (ADR-0029). A pair would imply a default worth overriding.
+
+- **The vocabulary moved with the flag, so one word covers the whole path.**
+  The stage that answers was already called `reasoning`; the signal that reaches
+  it is now a `ReasoningRequest` rather than an `Escalation`. `--help`, the text
+  output and `--format json` agree. A run that declined now reads `re-run with
+  --reasoning to analyse them`, and the summary line reads `3 for reasoning, 2
+  analysed`.
+
+- **Your stored verdicts survive the upgrade.** The verdict cache is keyed on
+  what the prompt is a function of, not on the names this codebase uses
+  internally, so a session graded under 0.2.3 is still answered from cache under
+  0.3.0. The stage-three prompt is unchanged and still recorded as `v1`, which
+  is what keeps two machines' answers comparable across the rename.
+
+- **The monitor's page and route follow.** `POST /api/reasoning` replaces
+  `POST /api/escalate`, and the page's button reads against the same budget it
+  always did. A monitor and a CLI of the same version are required, as before —
+  the page is served by the process it is talking to.

{stacktrace_cli-0.2.2 → stacktrace_cli-0.3.0}/docs/specs/aidr.md

@@ -42,8 +42,8 @@ version in a named manifest.
 | A discovery tool | OpenACA's existing scan already inventories agent tooling |
 | A fleet service | Only detector findings may travel, agent-keyed and content-free; sessions never leave the machine (ADR-0006) |
 
-One exception, named rather than rounded away: escalating a session for semantic
-analysis sends it to the provider that session already came from. See
+One exception, named rather than rounded away: requesting reasoning on a session
+sends it to the provider that session already came from. See
 [Trust boundary](#trust-boundary).
 
 ## Core tenets
@@ -56,7 +56,7 @@ enforced rather than merely intended.
 |---|---|---|
 | **Trust** — sensitive data does not cross the trust boundary | Transcripts, correlation records and session models are read only on the machine that produced them and have no upload path. What may travel is a detector finding: a verdict, component coordinates, confidence and observed capabilities, keyed to the agent — never conversation, and never an evidence excerpt | ADR-0006, and the local-only markers carried in the session model |
 | **Quality** — precision first; recall from a second source | A false alarm spends a human hour, so precision is a product decision, not a tuning parameter. Recall is bought by **adding an independent kind of evidence**, never by loosening a threshold | The detector's principles; the match outcome carried through correlation |
-| **Cost** — scalable unit economics | Deterministic rules first, then scoring against the component graph. Neither uses a model. **Only what they cannot resolve reaches inference** | The three-stage detector; no local model; a bounded escalation budget |
+| **Cost** — scalable unit economics | Deterministic rules first, then scoring against the component graph. Neither uses a model. **Only what they cannot resolve reaches inference** | The three-stage detector; no local model; a bounded reasoning budget |
 | **Security** — read-only sensing | The JSONL and SQLite caches agents already write, opened read-only. No process hooks, no proxy, no injected agent, no listener in the sensing path | Collection design; ADR-0001 |
 
 Two of these deserve their consequences stated plainly, because they are the ones
@@ -151,7 +151,7 @@ Each is specified where its component is, alongside the sub-component it joins:
 | Contract | Inside | Joins | Specified in |
 |---|---|---|---|
 | **Collection interface** | OpenAIDR | The per-kind readers to OpenAIDR's collector | [One contract, per agent kind](https://github.com/open-agent-security/openaidr/blob/main/docs/specs/session-collection.md#one-contract-per-agent-kind) |
-| **Escalation signal** | Detector | `priors` to `reasoning` — the detector's second and third stages | [The escalation signal](detector.md#the-escalation-signal) |
+| **Reasoning request** | Detector | `priors` to `reasoning` — the detector's second and third stages | [The reasoning request](detector.md#the-reasoning-request) |
 | **Analyzer adapter** | Detector | `reasoning` to the per-kind command-line agent it invokes | [The analyzer adapter](detector.md#the-analyzer-adapter) |
 
 The per-kind rows are pluggable slots, not components: supporting another agent
@@ -223,7 +223,7 @@ go; session input, the Correlator and the Detector do identical work in both.
 | Serves | Production: agent-keyed findings to Stacktrace Cloud (ADR-0006) | Development and demonstration: the local trace console |
 | Trigger | One run over a window of sessions | Changed files, as agents work |
 | Emit | Run to quiescence, emit complete findings | Draw a span when parsed, enrich it in place |
-| Escalation | Looser cap, off-peak | Tight cap, background, never inline |
+| Reasoning request | Looser cap, off-peak | Tight cap, background, never inline |
 
 **Mode lives in the driver, never inside a component.** No component can ask which
 mode it is running in, and nothing in the session model, correlation record or
@@ -235,12 +235,12 @@ cold pass without the tail — which is what stops two modes becoming two pipeli
 | Collect, project to spans | sub-second per changed file | Every change, or once per scheduled run |
 | Correlate | fast **only** against a cached graph | Graph rebuilt on manifest change |
 | `deterministic`, `priors` | milliseconds per evaluation | On each new span, against the session's accumulated evidence — never one span in isolation |
-| `reasoning` | seconds | Background, flagged sessions only, within the escalation budget |
+| `reasoning` | seconds | Background, flagged sessions only, within the reasoning budget |
 
 **Rule: nothing waits for the slowest stage.** Interactively, a tool call appears
 when parsed and its outcome, identity and findings attach later as enrichments to
 a row that already exists. On a scheduled run the same rule means one slow
-escalation does not hold the whole run.
+reasoning request does not hold the whole run.
 
 Three consequences that would otherwise look arbitrary. None of them is a
 concession to the console — each holds in both modes:
@@ -259,7 +259,7 @@ concession to the console — each holds in both modes:
   to re-read. Incremental collection is what makes that affordable: full pass at
   cold start, then changed files only.
 
-**The escalation budget is the one genuine per-mode parameter**, and the driver
+**The reasoning budget is the one genuine per-mode parameter**, and the driver
 sets it. `reasoning` is the only stage that costs seconds, a network call and
 money, so how much of the flagged set may reach it is a consumer decision, not a
 property of the detector. Everything else about the two modes is scheduling.

{stacktrace_cli-0.2.2 → stacktrace_cli-0.3.0}/docs/specs/detection-upload.md

@@ -291,7 +291,7 @@ Detecting before registering keeps a failed run from creating an asset.
 |---|---|---|
 | `--agent-kind`, `--bom`, `--budget`, `--sample-budget`, `--cache/--no-cache`, `--project-map`, `--root` | as `stacktrace detect` | |
 | `--since` | `7d` | |
-| `--escalate/--no-escalate` | **`--no-escalate`** | Inverse of `stacktrace detect`. Stage 3 spends the developer's provider quota and crosses a boundary; unattended is the wrong place for that to be implicit |
+| `--reasoning` | **off** | Stage 3 spends the developer's provider quota and crosses a boundary; unattended is the wrong place for that to be implicit |
 | `--dry-run` | off | NDJSON via the same builder the real path uses, so the preview **is** the payload. ADR-0006 constraint 4 requires it |
 | `--quiet`, `--allow-offline-cache` | off | as `sync endpoint` |