Skip to content

affected-set: record the fenced REAL-fix follow-on (behind resolver-B #6155) - #6170

Merged
briansrls merged 1 commit into
mainfrom
session/deep-hawk-756-affected-followon
Jul 2, 2026
Merged

briansrls merged 1 commit into
mainfrom
session/deep-hawk-756-affected-followon

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

What

Durably captures the affected-set REAL fix as a discoverable, dispatchable item in docs/plans/affected-set-precompute-pruning.md, so it survives lane wind-down instead of living only in a closed-PR comment + a dangling branch.

Context

PR #6105 (Provenance ingest at CI floor runtime) was closed as not-landable. A floor-repair scout measured its overlay path by execution on the pa_ingest single-witness fixture:

Arm entry_resolve typecheck_module witness_evals total_resolve_ms
PRESENT (overlay, witness skipped) 6 28 0 3885
RUN-ALL (skip disabled) 1 27 1 2042

Pruning as built is work-neutral theater — it increases resolve+typecheck and only saves the witness EVAL, because the node-frontier skip fires after the witness-entry closure is resolved and floor_runner resolves its closure twice. The #6127 width-1 shard trap in miniature.

The recorded follow-on

Doc-only; no code/.dag/gate surface. Revert-trivial.

🤖 Generated with Claude Code

…solver-B #6155)

#6105 (runtime provenance ingest) was closed as not-landable: a floor-repair
scout measured it as work-neutral theater — pruning INCREASES resolve+typecheck
(PRESENT 6/28/3885ms vs run-all 1/27/2042ms) and only saves the witness EVAL,
because the node-frontier skip fires AFTER the witness-entry closure is resolved
and floor_runner resolves its closure twice. Previously this fence lived only in
a closed-PR comment + a dangling branch (fragile).

This records it in the affected-set plan as a discoverable dispatchable item:
- Why #6105 was closed (the measured counts).
- Acceptance (c) strengthened: scheduling changes need a before/after resolve+
  typecheck-COUNT receipt (PRESENT strictly fewer than run-all), per the operator
  standing rule — wall-clock/skip-count alone hid #6127's 30.9x regression.
- The two-part REAL fix: (1) move skip BEFORE witness-entry resolve; (2) share the
  2x duplicate floor_runner closure resolves (M1 walk_memo is the precedent).
- Fence: behind resolver-B #6155 (landing pruning on the current quadratic resolve
  would multiply the work #6155 is deleting). Branch session/quick-carp-343
  preserved as harvest.

Doc-only.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@briansrls
briansrls merged commit e922ada into main Jul 2, 2026
1 of 2 checks passed
@briansrls
briansrls deleted the session/deep-hawk-756-affected-followon branch July 2, 2026 22:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant