stacktrace-cli 0.6.0__tar.gz → 0.7.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/PKG-INFO +3 -3
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/README.md +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0006-trust-boundary-and-detection-upload.md +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0018-remote-sync-config-and-facade-consumption.md +2 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0027-a-finding-may-name-what-it-could-not-place.md +1 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0039-send-usage-telemetry-by-default-with-an-opt-out.md +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0067-a-webhook-is-an-independent-queue-subscriber.md +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0068-webhooks-retry-the-retained-backlog.md +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0071-render-the-allowlisted-payload-per-destination.md +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0073-name-what-fired-and-which-component.md +1 -1
- stacktrace_cli-0.7.0/docs/adrs/0082-monitor-checks-every-installed-component-by-default.md +72 -0
- stacktrace_cli-0.7.0/docs/adrs/0083-each-block-reason-is-its-own-rule.md +127 -0
- stacktrace_cli-0.7.0/docs/adrs/0084-a-recursive-deletes-evidence-is-the-rm-that-ran.md +85 -0
- stacktrace_cli-0.7.0/docs/adrs/0085-show-when-and-which-finding-slack-delivered.md +88 -0
- stacktrace_cli-0.7.0/docs/adrs/0086-a-refusal-names-who-answered-the-call.md +110 -0
- stacktrace_cli-0.7.0/docs/adrs/0087-deploy-compiled-policy-with-a-privileged-scheduled-job.md +180 -0
- stacktrace_cli-0.7.0/docs/adrs/0088-slack-alerts-leave-out-confidence.md +44 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/INDEX.md +9 -1
- stacktrace_cli-0.7.0/docs/plans/015-managed-policy-deployment.md +47 -0
- stacktrace_cli-0.7.0/docs/releases/v0.6.1.md +108 -0
- stacktrace_cli-0.7.0/docs/releases/v0.7.0.md +87 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/daemon-uploads.md +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/detection-policies.md +57 -22
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/detection-upload.md +11 -7
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/detector.md +35 -6
- stacktrace_cli-0.7.0/docs/specs/managed-policy-deployment.md +540 -0
- stacktrace_cli-0.7.0/docs/specs/monitor-inventory.md +207 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/monitor.md +107 -6
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/notification-delivery.md +21 -18
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/remote-sync.md +5 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/pyproject.toml +2 -2
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/__init__.py +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/cli.py +5 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/correlate/acquire.py +60 -67
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/correlate/composition.py +4 -4
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/correlate/orchestrate.py +30 -38
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/identity.py +17 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/presentation.py +6 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/store.py +60 -15
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/webhook.py +36 -5
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/blocked.py +12 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/deterministic.py +388 -182
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/finding.py +3 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/render.py +5 -5
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/rules.py +47 -8
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/run.py +2 -2
- stacktrace_cli-0.7.0/src/stacktrace_cli/monitor/inventory.py +495 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/render.py +49 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/server.py +40 -4
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/site/app.js +377 -81
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/site/index.html +27 -9
- stacktrace_cli-0.7.0/src/stacktrace_cli/monitor/site/inventory.js +558 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/site/styles.css +142 -29
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/state.py +45 -2
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/watch.py +156 -65
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/cli.py +87 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/client.py +21 -4
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/payload.py +10 -5
- stacktrace_cli-0.7.0/src/stacktrace_cli/remote/policy_service.py +1497 -0
- stacktrace_cli-0.7.0/src/stacktrace_cli/remote/policy_worker.py +64 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/redact.py +100 -2
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/sync.py +11 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/telemetry/events.py +12 -30
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/webhook/cli.py +35 -4
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/conftest.py +19 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_cli.py +52 -13
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_runtime.py +12 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_store.py +117 -7
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_the_drained_payload_is_the_cold_one.py +103 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_webhook.py +101 -9
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/monitor/feed_harness.mjs +1070 -40
- stacktrace_cli-0.7.0/tests/monitor/inventory_harness.mjs +481 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/monitor/test_feed_model.py +453 -13
- stacktrace_cli-0.7.0/tests/monitor/test_inventory.py +866 -0
- stacktrace_cli-0.7.0/tests/monitor/test_inventory_page.py +264 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/monitor/test_render.py +49 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/monitor/test_server.py +11 -2
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/monitor/test_site_assets.py +55 -25
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/monitor/test_state.py +37 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/monitor/test_watch.py +441 -39
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_client.py +98 -3
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_detect_redaction.py +131 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_facade_contract.py +172 -1
- stacktrace_cli-0.7.0/tests/remote/test_policy_service.py +1975 -0
- stacktrace_cli-0.7.0/tests/remote/test_policy_service_cli.py +202 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_seam.py +5 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/telemetry/test_events.py +24 -34
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/telemetry/test_hooks.py +21 -10
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_acquire.py +94 -41
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_analysis.py +4 -4
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_call_status_conventions.py +41 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_correlate_orchestrate.py +49 -3
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detection_components.py +4 -4
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detection_event_time.py +2 -2
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detection_subject.py +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_blocked.py +27 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_cache.py +6 -6
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_end_to_end.py +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_finding.py +33 -7
- stacktrace_cli-0.7.0/tests/test_detector_names_the_service.py +252 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_new_deterministic.py +359 -47
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_priors.py +2 -2
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_render.py +4 -4
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_verdict.py +2 -2
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_vulnerable_dep_invoked.py +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_why_it_stopped.py +70 -14
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_evidence_is_dated_not_numbered.py +6 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_fingerprint_covers_what_the_analyzer_reads.py +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_monitor_cli.py +1 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_seam_boundary.py +3 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_shell_separators_match_the_shell.py +29 -5
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_the_detector_spec_lists_the_shipped_catalogue.py +6 -1
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_title_disclosure_invariant.py +4 -4
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_untrusted_content_never_travels.py +159 -12
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/webhook/test_cli.py +82 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/uv.lock +5 -5
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/.agents/skills/release-stacktrace/SKILL.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/.claude/settings.json +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/.claude/skills/pr-review-loop/SKILL.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/.claude/skills/release-stacktrace/SKILL.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/.codex/hooks.json +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/.github/managed-autofix.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/.github/workflows/autofix.yml +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/.github/workflows/ci.yml +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/.github/workflows/claude.yml +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/.github/workflows/publish-pypi.yml +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/.gitignore +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/AGENTS.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/CLAUDE.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0001-session-telemetry-as-input.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0002-session-collection-in-openaidr.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0003-runtime-edges.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0004-three-stage-detector.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0005-detection-family-and-report-assembly.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0007-proprietary-package-on-open-dependencies.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0008-console-in-separate-demo-package.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0010-detection-severity-and-confidence-ladders.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0011-verdict-cache.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0012-observation-evidence-kinds-and-transport.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0013-rule-catalogue-triage-and-per-rule-context.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0014-declared-project-mapping.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0015-narrow-the-security-catalogue.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0016-stall-grouping-is-session-wide.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0017-a-declined-repeat-is-a-stall.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0019-delegated-commands-are-openaca-objects.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0020-openaca-consumption-boundary.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0021-two-command-kinds.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0022-detection-scope-is-a-catalogue-column.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0023-sync-detect-collects-and-does-not-escalate.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0024-the-upload-carries-observations.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0025-a-denied-call-is-activity-never-an-invocation.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0026-the-console-becomes-a-product-surface.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0028-the-console-shows-what-it-placed.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0029-stage-three-returns-to-opt-in.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0030-a-detection-is-dated-by-the-turns-it-cites.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0031-one-host-daemon-observes-native-session-logs.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0032-refresh-daemon-compositions-outside-detection.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0033-a-third-party-analyzer-only-by-a-flag-that-names-it.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0034-the-drift-grade-is-read-off-a-run-not-a-call.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0035-naming-an-analyzer-selects-stored-answers.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0036-deliver-eligible-findings-to-slack-from-the-daemon.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0037-reuse-openaidr-append-cursors-in-the-daemon.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0038-poll-normalized-sessions-for-supplemental-changes.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0041-defer-native-windows-support.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0042-read-the-build-commit-from-the-install-record.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0043-name-the-session-agent-and-host-and-count-errors-by-class.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0044-send-the-build-as-version-prints-it.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0045-scan-every-session-and-outlive-them.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0046-the-finding-store-is-an-append-only-queue.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0047-capture-activity-during-correlation-or-lose-it.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0048-the-daemon-keeps-a-leveled-content-free-activity-log.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0056-stop-a-resident-daemon-by-record-and-signal.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0057-grow-the-queue-schema-additively-and-share-only-the-document.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0058-one-word-for-a-finding-columns-for-a-counter-and-a-push-that-does-not-wait.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0059-the-daemon-does-not-decide-whether-it-should-be-running.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0060-two-upload-postures-not-one-command-with-two-sources.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0061-the-drain-sends-findings-only.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0062-hold-the-transition-lock-across-remote-side-effects.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0063-underbuilt-debt-does-not-hold-the-scan-watermark.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0064-a-redacted-value-has-one-path-span.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0065-asset-external-id-resolves-by-a-ladder.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0066-host-owned-daemon-supervision.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0069-webhooks-deliver-what-retention-holds.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0070-package-the-cloud-agent-environment-bootstrap.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0072-host-supervisors-own-daemon-restarts.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0074-a-window-selects-findings-by-when-they-happened.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0076-two-phase-detection-pipeline.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0077-the-bom-job-wakes-once-at-startup-staggered.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0078-a-seeded-display-prefix-replaces-the-hostname-label.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0079-the-monitor-page-renders-findings-not-pipeline-health.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0080-enabling-reasoning-does-not-requeue-the-past.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/0081-reasoning-activation-returns-to-explicit-opt-in.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/HOOK-PROMPT.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/adrs/TEMPLATE.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/cutover-openaca-remote.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/002-session-input.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/003-correlation.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/004-detector.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/005-remote-sync.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/006-cli-composition.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/007-detection-upload.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/008-monitor.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/009-reasoning-jev.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/010-session-daemon.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/011-daemon-store.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/012-daemon-scanning.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/013-daemon-uploads.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/plans/014-asset-identity.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.0.1.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.1.0.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.2.0.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.2.1.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.2.2.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.2.3.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.3.0.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.3.1.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.4.0.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.4.1.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.5.0.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.5.1.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.5.2.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.5.3.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/releases/v0.6.0.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/research/001-intent-drift-metric.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/aidr.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/cli-composition.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/correlation.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/daemon-scanning.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/daemon-store.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/event-time.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/reasoning-jev.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/docs/specs/session-input.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/scripts/git-hooks/pre-push +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/scripts/install-hooks.sh +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/__main__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/analysis.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/build.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/cloud/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/cloud/setup.sh +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/correlate/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/correlate/join.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/correlate/observed.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/correlate/project_map.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/correlate/record.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/correlate/render.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/activity_log.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/bom.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/cli.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/client.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/composition.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/config.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/db.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/fleet.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/jobs.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/lifecycle.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/observer.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/paths.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/protocol.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/runtime.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/scan.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/server.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/daemon/service.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/analyzer.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/cache.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/history.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/jev.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/priors.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/prompts/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/prompts/jev-v1/stacktrace-deceptive-completion.json +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/prompts/jev-v2/stacktrace-deceptive-completion.json +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/prompts/v1/exclusions.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/prompts/v1/framing.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/prompts/v1/stacktrace-deceptive-completion.md +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/reasoning.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/secrets.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/verdict.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/detector/windows.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/reasoning.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/site/fonts/OFL.txt +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/site/fonts/dm-mono-400-latin.woff2 +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/site/fonts/dm-mono-500-latin.woff2 +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/site/fonts/dm-sans-latin.woff2 +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/monitor/verdicts.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/options.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/private_state.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/config.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/detect_payload.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/identity.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/policy.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/spool.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/sync_detect.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/remote/upload_contract.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/sessions/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/sessions/access.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/sessions/index.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/sessions/outcome.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/sessions/protocols.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/sessions/render.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/telemetry/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/telemetry/cli.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/telemetry/posthog.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/telemetry/state.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/webhook/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/src/stacktrace_cli/webhook/config.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/agent_bom_fixture.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_activity_log.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_client.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_composition.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_config.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_db.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_detection_needs_no_subscriber.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_fleet.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_identity.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_jobs.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_lifecycle.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_observer.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_queue_reader.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_scan.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_service.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_socket.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_the_stored_row_is_sufficient.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/daemon/test_wire_frames_are_bounded.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/detector_session_fixture.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/monitor/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/monitor/test_reasoning_gates.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/monitor/test_verdicts.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/helpers.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_cli.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_config.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_detect_activity.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_detect_cli.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_detect_client.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_detect_contract_is_exhaustive.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_detect_gate_matches_the_cloud.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_detect_layers_compose.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_detect_payload_reaches_the_cloud_model.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_detect_spool.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_detect_upload_contract.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_detect_wire_payload.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_identity.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_no_local_path_survives_redaction.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_payload.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_policy.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_redact_payload.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_spool.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_sync.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_sync_detect.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/remote/test_upload_contract.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/telemetry/__init__.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/telemetry/test_activity_log.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/telemetry/test_cli.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/telemetry/test_release_gate.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/telemetry/test_state.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/telemetry/test_uploader.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_adr_cross_references_are_reciprocal.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_agent_instance_id.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_bom_shape.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_build_commit.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_cli.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_composition.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_correlate_render.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_correlated_session.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_analyzer_contract.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_analyzer_live.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_deterministic.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_history.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_jev.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_prompts.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_reasoning.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_run.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_secrets.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_detector_windows.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_help_sections.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_join.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_no_live_document_states_the_old_stage_three_default.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_no_test_undoes_every_patch_at_once.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_observed.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_openaca_contract.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_openaidr_contract.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_option_arity_matches_the_binary.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_project_map.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_readme_examples_are_real_output.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_release_gate_coverage.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_release_readiness.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_session_identity_is_the_pair.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_sessions_access.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_sessions_end_to_end.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_sessions_protocol_typing.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_sessions_protocols.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_sessions_render.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_stored_verdicts_are_never_gated_on_reasoning.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_the_jev_spec_states_the_shipped_thresholds.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_the_locality_claim_is_qualified_everywhere.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_verification_subcommands_match_the_binary.py +0 -0
- {stacktrace_cli-0.6.0 → stacktrace_cli-0.7.0}/tests/test_what_jev_is_told_is_what_was_disclosed.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: stacktrace-cli
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.7.0
|
|
4
4
|
Summary: CLI for Stacktrace — Detection and Response platform for AI Agents.
|
|
5
5
|
Project-URL: Homepage, https://stacktrace.ai
|
|
6
6
|
Author-email: "Stacktrace AI, Inc" <founders@stacktrace.ai>
|
|
@@ -20,7 +20,7 @@ Classifier: Topic :: Security
|
|
|
20
20
|
Requires-Python: >=3.11
|
|
21
21
|
Requires-Dist: click>=8.1
|
|
22
22
|
Requires-Dist: httpx<1.0.dev0,>=0.28.1
|
|
23
|
-
Requires-Dist: openaca==0.
|
|
23
|
+
Requires-Dist: openaca==0.8.0
|
|
24
24
|
Requires-Dist: openaidr==0.3.2
|
|
25
25
|
Requires-Dist: posthog<8,>=7.0
|
|
26
26
|
Description-Content-Type: text/markdown
|
|
@@ -51,7 +51,7 @@ Requires Python 3.11 or newer.
|
|
|
51
51
|
|
|
52
52
|
```console
|
|
53
53
|
$ stacktrace --version
|
|
54
|
-
stacktrace 0.
|
|
54
|
+
stacktrace 0.7.0 (openaca 0.8.0)
|
|
55
55
|
```
|
|
56
56
|
|
|
57
57
|
## Quick start
|
|
@@ -0,0 +1,72 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: 0082
|
|
3
|
+
title: Monitor's static tabs check every installed component by default
|
|
4
|
+
status: accepted
|
|
5
|
+
date: 2026-09-30
|
|
6
|
+
supersedes: null
|
|
7
|
+
superseded-by: null
|
|
8
|
+
amends: null
|
|
9
|
+
amended-by: null
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## Context
|
|
13
|
+
|
|
14
|
+
`correlate/orchestrate.py`'s `advisories_for` deliberately narrows advisory
|
|
15
|
+
lookups to the union of what a session actually invoked. Its own docstring
|
|
16
|
+
names this as a decision, not an accident of the optimization it also
|
|
17
|
+
describes: asking during acquisition would send every component on the
|
|
18
|
+
machine to osv.dev once per composition built, so it is asked after
|
|
19
|
+
correlation instead — "osv.dev learns only about components this machine
|
|
20
|
+
actually used."
|
|
21
|
+
|
|
22
|
+
`docs/specs/monitor-inventory.md` adds two tabs, Inventory and Vulnerabilities,
|
|
23
|
+
whose whole purpose is the opposite question: not what the agents did, but
|
|
24
|
+
what they *can* load and what is known to be wrong with it. Answering that
|
|
25
|
+
means checking every installed component, invoked or not, which reverses the
|
|
26
|
+
invoked-only default for this one surface. A future reader who finds
|
|
27
|
+
`advisories_for`'s comment and then finds `monitor` disclosing the full
|
|
28
|
+
install list would reasonably read that as a regression rather than a second,
|
|
29
|
+
deliberately different, disclosure boundary — the two call sites don't share
|
|
30
|
+
a docstring, and the reason the newer one is broader isn't visible from
|
|
31
|
+
either alone.
|
|
32
|
+
|
|
33
|
+
## Decision
|
|
34
|
+
|
|
35
|
+
`stacktrace monitor`'s Inventory and Vulnerabilities tabs send the package names
|
|
36
|
+
of every *installed* component to osv.dev by default, independent of the
|
|
37
|
+
invoked-only lookup that Live and `detect` keep using. This is not a new
|
|
38
|
+
disclosure boundary: it is the same set `stacktrace scan endpoint` and Fleet's
|
|
39
|
+
composition upload already send, so the static tabs are catching up to a
|
|
40
|
+
boundary this package has already crossed elsewhere, not opening a new one.
|
|
41
|
+
`monitor --help` and its startup line say so, because widening what leaves
|
|
42
|
+
the machine is not something to do quietly. `detect` and the Live tab are
|
|
43
|
+
unchanged and continue to ask only about what a session invoked.
|
|
44
|
+
|
|
45
|
+
## Alternatives considered
|
|
46
|
+
|
|
47
|
+
- **Invoked-only, matching Live** — rejected: it would leave every component
|
|
48
|
+
a session never happened to call unchecked, which defeats the tabs' stated
|
|
49
|
+
purpose (what the agent *can* load) in favor of what Live already shows
|
|
50
|
+
(what it did load).
|
|
51
|
+
- **Gate the wider scan behind a flag** — rejected: the tabs are
|
|
52
|
+
materially incomplete without it, so the flag would be mandatory in
|
|
53
|
+
practice for anyone actually using the feature — a step with no real
|
|
54
|
+
choice behind it.
|
|
55
|
+
|
|
56
|
+
## Consequences
|
|
57
|
+
|
|
58
|
+
Every installed component that has a package name (an npm or PyPI MCP server,
|
|
59
|
+
a package) is named to osv.dev once per `monitor` run, not only the ones a
|
|
60
|
+
session reached. Skills and plugins with no package are never sent. This is a
|
|
61
|
+
strictly larger disclosure than Live's, in the same process. The cost is
|
|
62
|
+
proportional to install count rather than invocation count; this is accepted
|
|
63
|
+
because `scan endpoint` already pays it per sync. `detect`'s narrower,
|
|
64
|
+
invoked-only default is untouched and remains the answer for anyone who wants
|
|
65
|
+
the tighter boundary.
|
|
66
|
+
|
|
67
|
+
## When to revisit
|
|
68
|
+
|
|
69
|
+
If install-count growth measurably slows the tabs' first paint (the spec's
|
|
70
|
+
"summarise before listing" goal assumes the summary doesn't lag), or if
|
|
71
|
+
someone asks for the invoked-only boundary on these tabs too — add a flag
|
|
72
|
+
rather than reverting the default silently.
|
|
@@ -0,0 +1,127 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: 0083
|
|
3
|
+
title: Each block reason is its own rule
|
|
4
|
+
status: accepted
|
|
5
|
+
date: 2026-09-30
|
|
6
|
+
supersedes: null
|
|
7
|
+
superseded-by: null
|
|
8
|
+
amends: 0039
|
|
9
|
+
amended-by: null
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## Context
|
|
13
|
+
|
|
14
|
+
`stacktrace-agent-blocked` emitted one finding per block reason in
|
|
15
|
+
`detector/blocked.py` — `quota_exhausted`, `policy_blocked`,
|
|
16
|
+
`provider_throttled`, `upstream_refused` — and carried the reason only as the
|
|
17
|
+
anchor evidence's `kind`. Title, label, severity and remedy were all chosen per
|
|
18
|
+
reason, so the finding a reader got locally was specific.
|
|
19
|
+
|
|
20
|
+
Everything that keys on the rule id alone was not:
|
|
21
|
+
|
|
22
|
+
- **Fleet.** Its catalogue is seeded per rule id and never uploaded (Cloud
|
|
23
|
+
ADR-0027, ADR-0029), so every block in the console read "The agent was
|
|
24
|
+
blocked while working" with one remediation. Findings roll up by rule, so a
|
|
25
|
+
spend limit, a safety block, a throttle and a service refusal were one row.
|
|
26
|
+
Slack takes its title from the same catalogue.
|
|
27
|
+
- **Local notifications.** Prose is selected by rule id only (ADR-0031), so
|
|
28
|
+
every block notified as "The agent encountered a block while working".
|
|
29
|
+
- **Special cases.** `daemon/presentation.py` and the daemon's delivery
|
|
30
|
+
properties each read `evidence[0].kind` for this one rule, and telemetry grew
|
|
31
|
+
a `reason` property scoped to it (ADR-0039) with its own pairing table.
|
|
32
|
+
|
|
33
|
+
The four are not one finding with four wordings. Each has a different person
|
|
34
|
+
who acts and a different action: the account owner raises a limit or waits; the
|
|
35
|
+
person running the session starts a fresh one or leaves auto mode; nobody, at
|
|
36
|
+
first, for a throttle that clears by itself; whoever owns the service's
|
|
37
|
+
credentials grants a permission. They were already graded differently. ADR-0017
|
|
38
|
+
declined a second rule id for a declined stall because "the question a reader
|
|
39
|
+
asks is identical in both cases". Here it is not.
|
|
40
|
+
|
|
41
|
+
## Decision
|
|
42
|
+
|
|
43
|
+
**Each block reason is its own rule.** `stacktrace-blocked-quota`,
|
|
44
|
+
`stacktrace-blocked-policy`, `stacktrace-blocked-throttled` and
|
|
45
|
+
`stacktrace-blocked-upstream` are reliability rules, and each `Reason` names
|
|
46
|
+
its `rule_id`. Detection is unchanged: one pass reads the session, groups by
|
|
47
|
+
reason, and files each group under that reason's rule. The reason code stays
|
|
48
|
+
the evidence `kind`.
|
|
49
|
+
|
|
50
|
+
**Each is `session`-scoped.** It fires at most once per session, which is the
|
|
51
|
+
cardinality ADR-0022 gives `session`. `agent-blocked` was `call` only because
|
|
52
|
+
it fired once per reason; the new ids have no stored identity to keep stable.
|
|
53
|
+
|
|
54
|
+
**`stacktrace-agent-blocked` is retired, not erased.** It leaves `RULE_IDS`, so
|
|
55
|
+
nothing can emit it, and stays in `rules.RETIRED_SCOPES` with its `call` scope,
|
|
56
|
+
because a finding the daemon stored before an upgrade still names it and the
|
|
57
|
+
Fleet drain asks for its scope on every row it sends. Raising there would fail
|
|
58
|
+
the drain on every tick for as long as the row was queued. The local findings
|
|
59
|
+
view reads such a row by its retained reason code, and telemetry still admits
|
|
60
|
+
the id.
|
|
61
|
+
|
|
62
|
+
**A block already notified does not ring again under its new rule.** The
|
|
63
|
+
daemon's transcript fingerprints live in memory, so the restart an upgrade
|
|
64
|
+
brings re-reads every live session, and each block it rang as `agent-blocked`
|
|
65
|
+
comes back with a new event id. `rules.SUCCEEDS` names the rule each new one
|
|
66
|
+
took over from, and the store rebuilds the old id from the same anchor:
|
|
67
|
+
`agent-blocked` was call-scoped on the first blocked call, which its successor
|
|
68
|
+
still cites first. The new finding is still stored and uploaded.
|
|
69
|
+
|
|
70
|
+
**Telemetry drops `reason`.** This amends ADR-0039's `finding_delivered` row,
|
|
71
|
+
"optional reason code": the rule now says which reason it was, and a second
|
|
72
|
+
property saying it again could only ever disagree.
|
|
73
|
+
|
|
74
|
+
**Fleet learns the reasons by seeding four catalogue rows**, and keeps the
|
|
75
|
+
`agent-blocked` row for findings already ingested and CLIs not yet upgraded.
|
|
76
|
+
|
|
77
|
+
## Alternatives considered
|
|
78
|
+
|
|
79
|
+
- **Teach Fleet the reason code instead.** A reason column on detections,
|
|
80
|
+
grouping and filtering by `(rule_id, reason)`, a per-reason title table.
|
|
81
|
+
Rejected: it adds a second key to ingest, schema, roll-up, filters, counts,
|
|
82
|
+
the console and Slack, and every consumer written later has to learn the same
|
|
83
|
+
special case. Splitting the id makes the reason a fact every rule-keyed
|
|
84
|
+
consumer already reads.
|
|
85
|
+
- **Upload the per-reason title and remediation on the finding.** Rejected by
|
|
86
|
+
`docs/specs/detection-upload.md`: catalogue text is Cloud-derived so that two
|
|
87
|
+
copies cannot drift (ADR-0024).
|
|
88
|
+
- **Keep `call` scope.** Rejected: it contradicts ADR-0022's cardinality rule,
|
|
89
|
+
and since the ids are new there is no identity in Fleet or the daemon ledger
|
|
90
|
+
to preserve.
|
|
91
|
+
- **Keep `reason` in telemetry on the new rules.** Would keep a
|
|
92
|
+
group-by-reason insight working across versions. Rejected: it duplicates
|
|
93
|
+
`rule`, and keeping it honest needs a per-rule value check — the "a reason on
|
|
94
|
+
the wrong rule is a lie" argument ADR-0039's pairing table already made.
|
|
95
|
+
- **Rewrite stored `agent-blocked` rows to the new ids at upload.** Rejected: it
|
|
96
|
+
changes what was recorded, puts evidence parsing on the upload path, and Fleet
|
|
97
|
+
already holds rows under the old id that it would not match.
|
|
98
|
+
- **Name the rules after the codes** (`stacktrace-quota-exhausted`, …).
|
|
99
|
+
Rejected: a shared `blocked-` prefix keeps them together in sorted lists and
|
|
100
|
+
lets a prefix filter recover "every block" without a family column.
|
|
101
|
+
|
|
102
|
+
## Consequences
|
|
103
|
+
|
|
104
|
+
The catalogue grows from 10 rules to 13 (8 security, 5 reliability). This is
|
|
105
|
+
not new coverage — the same pass finds the same blocks — so ADR-0015's case
|
|
106
|
+
for a narrow catalogue is not reopened.
|
|
107
|
+
|
|
108
|
+
Adding a block reason now means adding a rule: a `rules.py` entry with scope
|
|
109
|
+
and stage, a `Reason.rule_id`, and a Fleet seed migration. That is the cost, and
|
|
110
|
+
it is also the point: Fleet has to learn a new reason either way, and this
|
|
111
|
+
makes forgetting visible as a bare rule id in the console (ADR-0029).
|
|
112
|
+
|
|
113
|
+
During the transition, Fleet can hold both an `agent-blocked` row and a
|
|
114
|
+
`blocked-*` row for the same block: the restarted daemon re-reads recent
|
|
115
|
+
sessions and uploads each block again under its new rule, and an old and a new
|
|
116
|
+
CLI can both analyse one session. The two rows do not merge. Laptops on older versions keep sending `agent-blocked`, with `reason`
|
|
117
|
+
on `finding_delivered`, until they upgrade. A PostHog breakdown by `reason`
|
|
118
|
+
covers only those versions; newer ones answer by `rule`.
|
|
119
|
+
|
|
120
|
+
Notifications now name the reason, with the title `blocked.py` writes for it.
|
|
121
|
+
|
|
122
|
+
## When to revisit
|
|
123
|
+
|
|
124
|
+
If block reasons grow past a handful and the per-rule catalogue churn becomes
|
|
125
|
+
the larger cost, or if a consumer needs "every block" as a unit a prefix cannot
|
|
126
|
+
give — a family below `reliability`, say — then a catalogue column for it is
|
|
127
|
+
the next step, not a return to one rule.
|
|
@@ -0,0 +1,85 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: 0084
|
|
3
|
+
title: A recursive delete's evidence names what it deleted
|
|
4
|
+
status: accepted
|
|
5
|
+
date: 2026-09-30
|
|
6
|
+
supersedes: null
|
|
7
|
+
superseded-by: null
|
|
8
|
+
amends: 0006, 0073
|
|
9
|
+
amended-by: null
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## Context
|
|
13
|
+
|
|
14
|
+
`stacktrace-destructive-action` reached Fleet's Slack as *Subject: Bash (tool)
|
|
15
|
+
(built-in) · Evidence: recursive_delete*. On the machine this was written
|
|
16
|
+
against it fired four times in sixteen minutes, and every one was an agent
|
|
17
|
+
deleting its own test output in a sibling project after a `cd` out of the
|
|
18
|
+
session's starting directory. None of the four could be dismissed from the
|
|
19
|
+
alert, because nothing in it said what was deleted.
|
|
20
|
+
|
|
21
|
+
That is the condition ADR-0006 wrote for its own revision: a detection type
|
|
22
|
+
genuinely unactionable without an evidence excerpt. ADR-0027 met it once, for
|
|
23
|
+
one field.
|
|
24
|
+
|
|
25
|
+
## Decision
|
|
26
|
+
|
|
27
|
+
**A `stacktrace-destructive-action` citation's `kind` is `rm -rf` and the
|
|
28
|
+
paths it deleted outside the workspace.**
|
|
29
|
+
This narrows ADR-0006 constraint 3 for that one field on that one rule, and
|
|
30
|
+
for that rule replaces ADR-0073's premise that a kind is a classifier: the
|
|
31
|
+
daemon webhook, which maps `evidence_kinds`, carries the command too.
|
|
32
|
+
|
|
33
|
+
1. **No new field.** Fleet already stores `kind` and shows it as the alert's
|
|
34
|
+
*Evidence*, so the device and Fleet keep one schema.
|
|
35
|
+
2. **`rm -rf` and the escaped paths, and nothing else.** Each path as it
|
|
36
|
+
resolved, listed once and whole. A path that does not fit under 500
|
|
37
|
+
characters is counted (`… and 3 more`), never cut. Wrappers, flags,
|
|
38
|
+
operands that stayed inside the workspace and the rest of the tool call are
|
|
39
|
+
left out.
|
|
40
|
+
3. **The existing redactor applies, word by word.** `kind` is cleaned one shell
|
|
41
|
+
word at a time, so each path is redacted on its own: relative to `$HOME` or
|
|
42
|
+
a working directory where it sits under one, its last component otherwise.
|
|
43
|
+
Credential tokens are dropped. An absolute path still never leaves.
|
|
44
|
+
4. **The display is best-effort, and this is its whole scope.** When the rule
|
|
45
|
+
fires is the resolver's existing behaviour. Its one change here carries
|
|
46
|
+
`sudo -R`'s root into a nested shell and prefixes it onto an absolute
|
|
47
|
+
operand, so the scratch exemption cannot hide `/tmp/x` under a chroot. A
|
|
48
|
+
relative operand under `sudo -R` resolves as on the host: a known gap, kept
|
|
49
|
+
because translating `cd` and `-D` through a chroot took four review rounds
|
|
50
|
+
and each fix found a narrower case. The evidence
|
|
51
|
+
reproduces no shell syntax, so a case it shows imperfectly is a cosmetic
|
|
52
|
+
gap, not a parser to extend. The upload contract still checks the redacted
|
|
53
|
+
`kind` for rooted paths and credentials, so a display flaw is refused at
|
|
54
|
+
the send, never leaked.
|
|
55
|
+
|
|
56
|
+
## Alternatives considered
|
|
57
|
+
|
|
58
|
+
- **New evidence fields** (`deleted_paths`, `delete_commands`). Built and
|
|
59
|
+
dropped. They changed the schema between the device and Fleet, needed a
|
|
60
|
+
Fleet migration, and Fleet refuses keys it does not declare, so a CLI that
|
|
61
|
+
shipped first would have lost every run holding one.
|
|
62
|
+
- **The command as the subject.** Rejected. Fleet groups findings by subject,
|
|
63
|
+
so every distinct command would become its own row instead of one *Bash*.
|
|
64
|
+
- **`detail`.** Rejected. Fleet's Slack alert does not show it.
|
|
65
|
+
- **The command as typed, operands resolved in place.** Built first, then
|
|
66
|
+
dropped. Reproducing wrappers, flags, `env -S`, quoting and several `rm`s in
|
|
67
|
+
one call was a shell parser of its own: every review finding on it after
|
|
68
|
+
the first was about that reproduction, and none about what was deleted.
|
|
69
|
+
|
|
70
|
+
## Consequences
|
|
71
|
+
|
|
72
|
+
Folder names, relative to the home directory, reach Fleet and every Slack
|
|
73
|
+
workspace it posts to. That exposure is accepted for this rule because a delete
|
|
74
|
+
cannot be triaged without it. A path outside `$HOME` and the working
|
|
75
|
+
directories shows only its last component (ADR-0064), so `rm -rf /etc/important`
|
|
76
|
+
reads `rm -rf important`; its `high` severity is what says it was a system
|
|
77
|
+
delete. Fleet's alert cuts a kind at 200 characters and strips `*` and `~`.
|
|
78
|
+
`tests/test_untrusted_content_never_travels.py` states the exemption beside the
|
|
79
|
+
invariant it narrows.
|
|
80
|
+
|
|
81
|
+
## When to revisit
|
|
82
|
+
|
|
83
|
+
If a second rule asks to carry an excerpt, it needs its own ADR. If a customer
|
|
84
|
+
objects to folder names in Fleet, the answer is an org-level switch, not a
|
|
85
|
+
wider redactor.
|
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: 0085
|
|
3
|
+
title: Show when and which finding Slack delivered
|
|
4
|
+
status: proposed
|
|
5
|
+
date: 2026-09-26
|
|
6
|
+
supersedes: null
|
|
7
|
+
superseded-by: null
|
|
8
|
+
amends: 0067, 0068, 0073
|
|
9
|
+
amended-by: null
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## Context
|
|
13
|
+
|
|
14
|
+
The first Slack webhook configured on a host delivers every eligible finding
|
|
15
|
+
still inside local retention (ADR-0068). A host with a retained backlog can
|
|
16
|
+
therefore receive many messages at once. The Slack rendering did not show the
|
|
17
|
+
finding's stable event ID or when Stacktrace recorded its notifiable revision,
|
|
18
|
+
so a reader could not distinguish old backlog from new findings or name the
|
|
19
|
+
exact finding when investigating it.
|
|
20
|
+
|
|
21
|
+
The timestamp Slack adds to a posted message is delivery time. It cannot answer
|
|
22
|
+
that question: a retained finding posted today looks new even when Stacktrace
|
|
23
|
+
recorded it days earlier. ADR-0030's occurrence range answers a different
|
|
24
|
+
question -- when the cited session turns occurred -- and may span multiple
|
|
25
|
+
turns.
|
|
26
|
+
|
|
27
|
+
Configuration also stated only that retained history would be sent. It gave no
|
|
28
|
+
size before the write authorized delivery and woke the daemon.
|
|
29
|
+
|
|
30
|
+
## Decision
|
|
31
|
+
|
|
32
|
+
`detected_at` joins the webhook's allowlisted projection for every format. It is
|
|
33
|
+
the queue row's `created_at`: the instant Stacktrace recorded the first revision
|
|
34
|
+
that crossed the notification gate. It is neither the cited-turn occurrence
|
|
35
|
+
range nor the later webhook delivery time. The payload remains version 1 because
|
|
36
|
+
the field is additive.
|
|
37
|
+
|
|
38
|
+
The Slack rendering shows `detected_at` with Slack's native date syntax, so each
|
|
39
|
+
viewer sees it in their own locale and timezone, and includes the stable event
|
|
40
|
+
ID under the label `finding ID`. The same event ID remains in
|
|
41
|
+
`X-Stacktrace-Event-ID` for receiver idempotency. A timestamp that cannot be
|
|
42
|
+
parsed as an offset-aware ISO 8601 value is omitted from the Slack presentation
|
|
43
|
+
rather than holding the delivery cursor forever; the finding ID still renders.
|
|
44
|
+
|
|
45
|
+
Before writing configuration, `stacktrace webhook configure` reads the webhook
|
|
46
|
+
subscriber's durable high-water mark and reports the exact number of retained,
|
|
47
|
+
notifiable revisions currently above it. It does not count unknowns, ineligible
|
|
48
|
+
findings, later revisions of an already-notified finding, or rows the subscriber
|
|
49
|
+
already passed. A missing database reports zero. An unreadable database reports
|
|
50
|
+
that the preview is unavailable but does not prevent configuration.
|
|
51
|
+
|
|
52
|
+
The count is an informational snapshot. It is not a confirmation prompt, a
|
|
53
|
+
configuration-time cutoff or a new acknowledgement: concurrent recording and
|
|
54
|
+
delivery may change the backlog immediately afterward, and ADR-0068's retained
|
|
55
|
+
history semantics remain in force.
|
|
56
|
+
|
|
57
|
+
## Alternatives considered
|
|
58
|
+
|
|
59
|
+
- **Rely on Slack's message timestamp**: rejected because it is the delivery
|
|
60
|
+
time and makes an old retained finding look newly generated.
|
|
61
|
+
- **Render `occurred_start` or `occurred_end`**: rejected because those date the
|
|
62
|
+
cited session evidence, not the finding's creation, and a finding can cite a
|
|
63
|
+
range rather than one instant.
|
|
64
|
+
- **Keep the event ID only in the HTTP header**: rejected because headers help
|
|
65
|
+
automated receivers deduplicate but are invisible to the person investigating
|
|
66
|
+
a Slack alert.
|
|
67
|
+
- **Ask for confirmation or default to new findings only when backlog exists**:
|
|
68
|
+
rejected because that silently changes ADR-0068's reliable retained-history
|
|
69
|
+
contract. The count supplies informed context without creating a second
|
|
70
|
+
delivery policy.
|
|
71
|
+
|
|
72
|
+
## Consequences
|
|
73
|
+
|
|
74
|
+
Backlog deliveries identify themselves as older findings, and operators can
|
|
75
|
+
copy one stable ID into a discussion or lookup. Generic webhook consumers gain
|
|
76
|
+
one additive field. Slack receives one more timestamp and the already-disclosed
|
|
77
|
+
event ID in its message body.
|
|
78
|
+
|
|
79
|
+
The configure count can be stale as soon as it is printed, and an unreadable
|
|
80
|
+
database cannot provide it. Both conditions are stated rather than disguised as
|
|
81
|
+
an exact authorization boundary.
|
|
82
|
+
|
|
83
|
+
## When to revisit
|
|
84
|
+
|
|
85
|
+
Revisit the label if the product introduces a separately persisted finding
|
|
86
|
+
generation instant distinct from queue insertion. Revisit the preview if
|
|
87
|
+
configuration gains an explicit backlog policy; until then it must remain a
|
|
88
|
+
snapshot of the one retained-history policy, not a policy of its own.
|
|
@@ -0,0 +1,110 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: 0086
|
|
3
|
+
title: A refusal, retry or sent credential names who the call reached
|
|
4
|
+
status: accepted
|
|
5
|
+
date: 2026-10-01
|
|
6
|
+
supersedes: null
|
|
7
|
+
superseded-by: null
|
|
8
|
+
amends: 0006, 0027
|
|
9
|
+
amended-by: null
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## Context
|
|
13
|
+
|
|
14
|
+
A Fleet Slack alert for `stacktrace-blocked-upstream` read *Subject: Bash
|
|
15
|
+
(tool) (built-in)*, *Evidence: upstream_refused*. The person reading it could
|
|
16
|
+
not tell who refused. A `stacktrace-tool-retry-storm` alert had the same gap:
|
|
17
|
+
it never said what the agent kept calling, so a service browning out looked
|
|
18
|
+
the same as an agent sending a bad request. A `stacktrace-credential-egress`
|
|
19
|
+
alert said a token was in a call's arguments, at a character offset no reader
|
|
20
|
+
can use, and not where it was sent.
|
|
21
|
+
|
|
22
|
+
Each citation's `detail` was built from `tool_name_for(call)`. For a shell call
|
|
23
|
+
that is `Bash`, and for every MCP call it is the fixed `an MCP connector`. Both
|
|
24
|
+
were deliberate. ADR-0006 constraint 3 keeps names the other side chose out of
|
|
25
|
+
a finding, and ADR-0027 lets an unplaced server's alias sit only in
|
|
26
|
+
`Participant.name`. The result is that the alert names the agent's own tool and
|
|
27
|
+
never the thing that refused.
|
|
28
|
+
|
|
29
|
+
## Decision
|
|
30
|
+
|
|
31
|
+
The `detail` of a citation on `stacktrace-blocked-throttled`,
|
|
32
|
+
`stacktrace-blocked-upstream`, `stacktrace-tool-retry-storm` and
|
|
33
|
+
`stacktrace-credential-egress` names who the call reached
|
|
34
|
+
(`deterministic._outside_target`). For a sent credential it reads `sent to
|
|
35
|
+
<target>`, and the character offset is no longer named:
|
|
36
|
+
|
|
37
|
+
- **MCP call:** `linear MCP · search_issues`, the server alias and the tool.
|
|
38
|
+
Each part is named only when it is shaped like an identifier (letters,
|
|
39
|
+
digits, `_ . : -`, at most 64), so it is never a sentence or a path. A
|
|
40
|
+
server that fails the shape names nothing. A tool that fails it leaves
|
|
41
|
+
`linear MCP`. This holds for a placed or an unplaced server.
|
|
42
|
+
- **WebFetch:** the host of its `url`.
|
|
43
|
+
- **Shell call:** a vendor CLI from a closed list names its service
|
|
44
|
+
(`GitHub (gh)`). Any other segment that reaches the network must carry
|
|
45
|
+
exactly one `http(s)://` URL, and its host is named. A command that reaches
|
|
46
|
+
two places, or a network segment with no URL, names nothing.
|
|
47
|
+
|
|
48
|
+
Only the host of a URL is named. Scheme, userinfo, port, path and query never
|
|
49
|
+
are. A target that matches a credential shape is dropped. When nothing is
|
|
50
|
+
named, the detail reads as before (`Bash`, `an MCP connector`).
|
|
51
|
+
|
|
52
|
+
A block the client raised, a spend limit or a safety check, keeps the tool
|
|
53
|
+
name. The call never reached the service, so naming the service would blame
|
|
54
|
+
it.
|
|
55
|
+
|
|
56
|
+
This amends ADR-0006 constraint 3 and ADR-0027 for these four rules' citation
|
|
57
|
+
`detail` only. Every other field and rule is unchanged, and the retry storm's
|
|
58
|
+
remediation keeps `tool_name_for`. `tests/test_untrusted_content_never_travels.py`
|
|
59
|
+
states the bound as `_PERMITTED_AS_A_TARGET` and `_TARGET_RULES`.
|
|
60
|
+
|
|
61
|
+
## Alternatives considered
|
|
62
|
+
|
|
63
|
+
- **Name only a vendor CLI's service, never a host or an MCP tool.** Rejected.
|
|
64
|
+
It was the first version of this change. It left every MCP refusal and every
|
|
65
|
+
`curl` refusal naming nothing, and those are the cases a reader most needs.
|
|
66
|
+
- **Read the service from the error text.** Rejected. The service writes its
|
|
67
|
+
own error body and can put any name there. `blocked.py` already refuses to
|
|
68
|
+
copy captures out of it. The target here comes from the call the agent made.
|
|
69
|
+
- **Name the first target when a command reaches several.** Rejected. The
|
|
70
|
+
record does not say which segment failed, and naming the wrong one sends the
|
|
71
|
+
reader to the wrong service.
|
|
72
|
+
- **Name the full URL.** Rejected. Paths and queries carry tokens, account ids
|
|
73
|
+
and customer data. The upload contract already refuses a URL with a path or
|
|
74
|
+
query.
|
|
75
|
+
- **Carry the target as a new Subject or wire field.** Rejected for this
|
|
76
|
+
change. `Participant` has a closed set of kinds, and Fleet checks
|
|
77
|
+
`subject_kind` with a constraint. A new kind changes the upload contract,
|
|
78
|
+
Fleet's schema and its console. The detail already travels and is already
|
|
79
|
+
stored.
|
|
80
|
+
|
|
81
|
+
## Consequences
|
|
82
|
+
|
|
83
|
+
A refusal names `linear MCP · search_issues`, `api.ledgerline.io` or
|
|
84
|
+
`GitHub (gh)`. Fleet shows this once its Slack message prints evidence detail
|
|
85
|
+
(Fleet ADR-0072). Local surfaces that print detail show it at once.
|
|
86
|
+
|
|
87
|
+
An MCP server can now put a word of its choosing into a finding through its
|
|
88
|
+
tool name. The identifier shape bounds it to one token, the upload redactor
|
|
89
|
+
and contract gate still walk it, and Fleet secret-scans it again before Slack.
|
|
90
|
+
A host can now leave the machine for these four rules. That includes internal
|
|
91
|
+
hostnames.
|
|
92
|
+
|
|
93
|
+
A command whose URL sits in a variable (`curl "$URL"`), or that runs through a
|
|
94
|
+
wrapper `command_segments` does not unwrap (`npx vercel`, `sudo gh`), names
|
|
95
|
+
nothing. Each fails towards the old wording, never towards a wrong name.
|
|
96
|
+
|
|
97
|
+
Two known limits are accepted rather than parsed around, because handling
|
|
98
|
+
each means reading per-program flags:
|
|
99
|
+
|
|
100
|
+
- A URL argument is taken to be where the request went. A command whose only
|
|
101
|
+
literal URL is a proxy or a referer (`curl -x http://proxy:3128 "$URL"`)
|
|
102
|
+
names that host.
|
|
103
|
+
- A vendor CLI keeps its service name when pointed at another endpoint
|
|
104
|
+
(`aws --endpoint-url …`, `gh --hostname …`).
|
|
105
|
+
|
|
106
|
+
## When to revisit
|
|
107
|
+
|
|
108
|
+
Revisit if a deployment cannot send hostnames or MCP tool names to Fleet, if
|
|
109
|
+
the identifier shape lets through a tool name that carries data, or if the
|
|
110
|
+
target needs to become a structured field of its own.
|