Repository navigation
simplify(proximity): remove discarded risk metadata - #4549
Merged
Merged
Conversation
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Collect encounter addresses and named relationships without graph-impact or freshness-score work. Preserve contribution identity and the published threshold admission mapping. Describe related activity without claiming an exact overlap. Refs #4416
ScriptedAlchemy
force-pushed
the
simplify/proximity-constant-risk
branch
from
October 25, 2026 16:11
958731a to
e75a760
Compare
Fleet logs show five complete 48,000-function generations take 53–65 seconds each. The default medium deadline kills the final refresh near 300 seconds despite steady successful publication. Declare the measured aggregate workload through the existing Cargo-to-Bazel size metadata, preserving every refresh, memory bound, and assertion. Verified: regenerated the maintained BUILD files and generator --check reports all 60 outputs current. Runtime verification remains with the new CI run. Evidence: https://github.com/ScriptedAlchemy/tracedecay/actions/runs/40237000628/job/121323060188
A real NativeLink restart with an eight-second outage reproduces exit 34 using the default five retries (3.50s critical path). Ten retries reconnect and complete the same remote action (18.99s critical path). Keep the existing timeout, backoff cap, remote-only compilation, and test failure semantics.
# Conflicts: # .github/workflows/ci.yml
The packaged Cursor and Codex journey reused one session ID across two providers. Canonical Git evidence correctly refused that lineage, leaving background convergence blocked before the advisory request timed out. Give each host its own session and reuse the Codex identity in its rollout and Stop event. Preserve the existing terminal-cycle and deadline checks.
ScriptedAlchemy
enabled auto-merge (squash)
October 27, 2026 02:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Direct encounter reads computed graph impact and freshness scores that their callers discarded. Keep exact encounters and named relationships without that scoring work.
What changed
Scope
Refs #4416. Parent is master.
The persisted numeric setting remains. Its replacement and a metered real-producer no-impact proof remain open. No speedup is claimed.
Blast Radius
Encounter identity, permission, generation, and expiry checks remain. Existing durable feedback stores contain projected findings rather than the removed transient payload.
Verification