Repository navigation
BT-E1: fix cross-module transport node deduplication - #102
Merged
Merged
Conversation
Move endpoint_use_count from per-module scope to global scope in add_service_call_edges so that callables in different modules calling the same service operation each get their own cloned transport triplet instead of wiring duplicate scalar edges to the shared original. https://claude.ai/code/session_015ogXTmQoQPA15XpEnkTCng
Delete 5 unused ToolInfo factory methods (new, in_package, standalone, workspace, composed), 4 builder methods (with_param, with_extra_target, with_declarative_dag, manual), and dead ExtraTarget/EntrypointParam constructors. Rewrite 2 tests to use struct literals. registry.rs reduced from 672 to 559 lines. Generated Makefile identical. All 10 Worker B tasks (B1-B10) now marked Done in tasks.md. https://claude.ai/code/session_015ogXTmQoQPA15XpEnkTCng
briansrls
added a commit
that referenced
this pull request
May 12, 2026
…2744 §1 (#2750) * docs(r3): T-WAD FULL R3 §1.8 ledger sync — +6 gates (#98–#103) per PR #2744 §1 **Authority**: PM scoping doc PR #2744 §1 (T-WAD FULL R3 elevation per operator directive 2026-05-12 + Director ratification msg_5cbdad24 + msg_f9fd669e + (b) ledger-sync disposition msg_2a68a4b5 — follow-up sync PR pattern). **Sync disposition rationale** (per Director msg_2a68a4b5): option (a) bundles too much into PR #2744 mid-review; (c) bakes parallel-authority into scope doc as "temporary" PROPOSED state which calcifies. (b) is operationally clean if sync PR queues for atomic-merge-sequencing alongside PR #2744 — gap window bounded to merge-clock seconds. **6 new §1.8 gate rows** (all T-Workflow-As-Data, NEW 2026-05-12): - **#98** `ci_yml_hand_authority_dissolved` (state-check) — hand-authority NOT file-deletion; (a) absent / (b) emission-artifact / (c) thin-shim per briansrls BLOCKING #PR2744 fix - **#99** `emission_target_open_enum_landed` (substrate-shape) — EmissionTarget sum-type per (c-refined) shape at PR #2749 §7 - **#100** `project_github_actions_landed` (substrate-shape) — projection function declaration in gunbc namespace; consumes extdeps.github.actions.Workflow as codomain + CIWorkflowDag (PR #2736 carrier) as input domain - **#101** `test_cost_dimension_landed` (substrate-shape) — Cost dimension on TEST NODES (distinct from existing compiler-internal cost gates #37/#39/#40/#70/#80 which are about SymbolicCost as the compiler's cost lens; this gate is about Cost-as-Dimension applied to test nodes so slow-test ratchet derives structurally) - **#102** `slow_test_exemptions_dissolved` (state-check) — scripts/slow-test- exemptions.txt deleted; sibling of #101 per kernel-modeling discipline split - **#103** `ci_uses_affected_set_selection` (state-check) — BinaryShim emitter consumes affected-set lens output from PR #2713; Layer 2 path-regex `if:` gates removed; cross-tier co-owned with clever-tern-670 Slice 7 **Count updates** (was 97 enumerated / 96 R3-load-bearing; now 103/102): - §1.5 total enumeration: 97 → 103 - §1.5 R3-load-bearing arithmetic: 96 → 102 (= 103 - 1 canvas-deferred {#11}) - §1.5 composition tally: T-Workflow-As-Data 4 → 10 (+6 NEW) - §1.5 prose: R3 close target 96 → 102 - §1.5 R4-carved-dissolved framing: target 96 → 102 - §1.7 status-taxonomy lead: 96 → 102 R3-load-bearing - §1.8 standing-program note: 96 → 102 load-bearing - §0 R3 close criteria: 97/96 → 103/102 - §1 plan-declared count: 97 → 103 - §1.6 acceptance criteria: 97/96 → 103/102 - §1.8 §1.8 single-canonical-view: 97 → 103 - §1.8 row #11 canvas-deferral arithmetic: 97 → 103 - §Q1 table: 97 → 103 + history pointer **Sequencing discipline** (per Director msg_2a68a4b5): 1. This sync PR sits ready-to-merge until PR #2744 lands 2. As soon as PR #2744 squash-merges, fire this sync PR squash-merge immediately 3. Gap window: bounded to merge-clock seconds (atomic-as-possible without bundle) 4. If reviewer delay accumulates here, fold into PR #2744 retroactively (option (a) escalation path) **Cost-dim distinction note** (per Director verification flag): existing gates #37/#39/#40/#70/#80 are about compiler-internal SymbolicCost (cost lens reading target programs). #101 is structurally distinct — Cost dimension on TEST NODES for slow-test ratchet derivation. Not a duplicate. **§1.9 acceptance-aggregator pilot row** (`t_ci_wad_full_r3_close`): remains in PR #2744 §9 with gate-name references per `feedback_no_snapshot_integers_in_briefs` discipline. No row added to this sync PR per Director msg_2a68a4b5 ("EITHER PR #2744 §9 OR sync PR — your call; either works"). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): cross-doc authority sync — add 6 NEW T-WAD gates to r3-structure.md §Acceptance Per codex BLOCKING review on PR #2750 (2026-05-12T07:34:59Z): scope doc lines 13 and 84 claim r3-structure.md was "updated in this PR" + reference 103-gate total per r3-structure.md §Acceptance, but the PR only changed r3-program-plan.md — r3-structure.md still had no #98–#103 rows. That violated INVARIANTS.md P2 / modeling-discipline.md Practice 5 (single-authority metadata) — the closure ledger became internally inconsistent at the canonical-source level. Fix: add the 6 NEW gate bullets to r3-structure.md §Acceptance T-Workflow-As-Data section (after `ci_workflow_modeled_as_dag`), mirroring r3-program-plan.md §1.8 rows #98–#103. Each bullet carries the full Pass-condition body (single-source authority for Pass conditions per the r3-program-plan.md convention). Now both docs land the same gate set atomically in this PR: - r3-program-plan.md §1.8 rows #98–#103 (commit ef9a140, prior) - r3-structure.md §Acceptance T-WAD bullets (this commit) — matching content The "Documentation Describes Live State" rule + single-authority discipline restored. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): briansrls BLOCKING fix — propagate 103/102 counts through full plan Per briansrls BLOCKING inline review on PR #2750 at line 84 (2026-05-12T07:50:26Z): "The new 103/102 canonical count is not propagated through the full plan, leaving later close criteria at 96/97 and creating competing R3 thresholds (INVARIANTS P2 single authority)." Three stale references found in re-grep + fixed: - Line 114 (§1.7 two-Pass-surfaces context): "**96** R3-load-bearing gates green" → "**102** R3-load-bearing gates green" (post-carve-promotion + T-WAD FULL R3 elevation) - Line 623 (§5.2 R3 close definition): "**96** load-bearing post-carve- promotion" → "**102** load-bearing post-carve-promotion + T-WAD FULL R3 elevation" - Line 1001 (§10 dependency-graph mirror): "lane TestClaim gates (97 total)" → "lane TestClaim gates (103 total; 102 R3-load-bearing post-T-WAD-FULL- R3-elevation 2026-05-12)" Initial sync (commit ef9a140) updated §0 + §1.5 + §1.6 + §1.7 + §1.8 + Q1 table; this commit completes propagation through §1.7 two-Pass-surfaces / §5.2 R3 close definition / §10 dependency-graph mirror. Single-authority discipline (INVARIANTS P2) now consistently asserts 103/102 across the full plan; no competing R3 thresholds remain. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): InlineGunbc DESIGN-ONLY alignment — cross-doc consistency with PR #2744 openai-pro BLOCKING fix Per openai-pro BLOCKING fix on PR #2744 (commit e43aba3): WI-1 / WI-2 briefs + scope doc §2 type sketch all align on InlineGunbc as DESIGN-ONLY (NOT in initial enum, lands when runtime consumer exists). The §1.8 gate bodies in r3-program-plan.md row #99 + r3-structure.md §Acceptance bullet for emission_target_open_enum_landed were stale relative to that alignment. Fix in this sync PR: - r3-program-plan.md §1.8 row #99: "(YamlStatic | BinaryShim | PythonShim | InlineGunbc | ...)" → "3 initial arms (...)" + InlineGunbc DESIGN-ONLY note with PR #2746 §5.4 + openai-pro BLOCKING cross-references - r3-structure.md §Acceptance T-WAD bullet for emission_target_open_enum_landed: same change pattern Single-authority across: - PR #2744 scope doc §0 / §1 gate row / §2 type sketch - PR #2744 WI-1 brief DESIGN-ONLY discipline - PR #2744 WI-2 brief Output / DO-DON'T / Acceptance gates - PR #2750 (this PR) §1.8 ledger row + §Acceptance archive - PR #2746 §5.4 canonical DESIGN-ONLY framing Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): T-WAD ledger sync — lane-definition gate lists pointer-only + scope-doc cross-ref qualifier (codex BLOCKING + non-blocking on PR #2750) Two findings from codex review #10042 on commit 0c08f77 (T-WAD ledger sync PR head): BLOCKING — "T-WAD ledger sync updated the Acceptance archive but skipped the lane-definition gate lists → update those T-Workflow-As-Data gate lists to include #98–#103 or make them pointer-only." The PR #2750 cascade landed the 6 NEW T-WAD FULL gates (#98–#103) in: - r3-structure.md §Acceptance T-Workflow-As-Data bullets (lines 172-177) - r3-program-plan.md §1.8 ledger rows - r3-program-plan.md count propagation (§0/§1.5/§1.6/§1.7/§5.2/§10/§Q1) But the cascade missed two lane-DEFINITION gate lists in r3-structure.md that ALSO enumerate T-WAD closure gates: - Line 41 (numbered lane list, T-WAD entry) - Line 222 (T-WAD row in §"Lane structure" table) Both listed only the original 4 pre-FULL gates (workflow_substrate_carriers_landed / timing_lens_carrier_landed / ci_workflow_modeled_as_dag / shared_external_attachment_pattern_documented). Reviewers reading either list would not see the 6 NEW gates — INVARIANTS P2 single-authority gap. Fix: convert both lane-definition lists to pointer-only references back to §Acceptance T-WAD as the canonical gate list. Rationale: §Acceptance is the authority anchor (per INVARIANTS P2 + sister r3-program-plan.md §1.8); duplication in lane-definition lists would re-introduce drift the cascade is closing. Also augmented both lane-definition entries with FULL R3-close elevation 2026-05-12 framing + multi-Mgr ownership (Substrate Mgr Slices 4-5/8 + Verification Mgr Slice 7 affected-set + Debt-Paydown Mgr Slice 6 sub-component). Non-blocking — "Line 172 cites docs/r3-t-workflow-as-data-full-r3-close-scope.md, but git ls-tree origin/main returned no blob → replace with existing receipt or land the scope doc." The scope doc exists on PR #2744's branch (in flight) but not on origin/main yet. Codex correctly notes the dangling cross-reference against current main. Fix: add explicit "(scope doc landing via in-flight PR #2744)" qualifier so future readers know the citation is forward-referencing a known in-flight PR rather than a typo or missing doc. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): T-WAD ledger sync — remove dangling file refs (briansrls BLOCKING + codex INVARIANTS P2/P5 escalation on PR #2750) briansrls inline BLOCKING at r3-structure.md:172 (2026-05-12T09:28:04Z) escalated the prior non-blocking scope-doc citation issue to BLOCKING: "The new gate cites docs/r3-t-workflow-as-data-full-r3-close-scope.md section 1, but git ls-tree origin/main produced no blob and the reconstructed PR-head test returned 1, so the cited T-WAD scope authority is absent (INVARIANTS P2/P5)." The earlier qualifier fix ("scope doc landing via in-flight PR #2744") acknowledged the dangling reference but didn't resolve the structural P2/P5 violation — the gate description still CITED an authority that doesn't exist on origin/main, which is the merge target. Audit: grepped both docs for refs to files that don't exist on origin/main: - docs/r3-structure.md:172 — `docs/r3-t-workflow-as-data-full-r3-close-scope.md` (PR #2744) - docs/r3-program-plan.md:326 — `docs/briefs/r3-t-wad-full-r3-cidag-scaffold-worker.md` (PR #2744) Fix: replace both file-path references with PR-number anchors. PR numbers are stable references; file paths become valid only post-merge. Gate descriptions are self-contained without the cross-references (the (a)/(b)/(c) enumeration + supporting framing already conveys the gate's substance). - r3-structure.md:172: "per `docs/r3-t-workflow-as-data-full-r3-close-scope.md` §1 — scope doc landing via in-flight PR #2744" → "in-flight scope authority at PR #2744 §1" - r3-program-plan.md:326: "WI-2 implementation: `docs/briefs/r3-t-wad-full-r3-cidag-scaffold-worker.md`" → "WI-2 implementation: in-flight via PR #2744 (brief lands with the scope-doc)" Both gates retain full substantive content; only the file-path crutches are removed. When PR #2744 merges and the files exist on main, future authors may re-add file refs cleanly — but the gate descriptions never needed them as load-bearing authority. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): T-WAD ledger sync — EmissionTarget → WorkflowRuntime rename cascade (warm-wolf-698 PR #2749 commit 575eb7e; SELF_HOSTING.md:609 name collision) Cascade sister-PR rename: PR #2744 branch carries the scope-doc + brief renames in commit 70a49ac; this commit carries the ledger / structure gate-ID renames. warm-wolf-698 surfaced a DECISIVE name-collision finding at PR #2749:666 / :672 (briansrls operator BLOCKING 2026-05-12T09:26:49Z): the canvas EmissionTarget sum-type collides with the canonical Shape-A carrier declared at `src/v3/SELF_HOSTING.md:609`: type EmissionTarget { language: LanguageSpec // what's valid (required) rendering: RenderingSpec? // how to format (optional) } This is the SELF_HOSTING.md emitter-composition authority — INVARIANTS P2 violation. warm-wolf-698 pushed rename to WorkflowRuntime in PR #2749 commit 575eb7e (48 occurrences). All OTHER ratified elements stand per feedback_pre_compaction_framings_self_supersede. This commit cascades the rename through PR #2750 branch: - docs/r3-program-plan.md §1.8 row #99: gate ID emission_target_open_enum_landed → workflow_runtime_open_enum_landed (also EmissionTarget references in row description) - docs/r3-program-plan.md §1.8 row #100: EmissionTarget references in project_github_actions signature - docs/r3-structure.md line 41 (T-WAD lane summary): EmissionTarget references + gate-ID rename in the multi-gate reference - docs/r3-structure.md §Acceptance T-Workflow-As-Data bullets: gate-ID emission_target_open_enum_landed → workflow_runtime_open_enum_landed EmissionTarget references in `project_github_actions_landed` description - docs/r3-structure.md §Lane structure T-WAD row: EmissionTarget references in scope expansion text Variant names unchanged (YamlStatic / BinaryShim / PythonShim). Gate descriptions retain full substantive content; only the type-name and gate-ID identifiers are renamed. Cascade trail across in-flight PRs: - PR #2749 (warm-wolf-698): 575eb7e — substrate canvas rename - PR #2751 (warm-wolf-698): expression-substrate canvas rename (in flight) - PR #2744 (mine): 70a49ac — scope-doc + WI-1 + WI-2 brief rename - PR #2750 (mine): THIS COMMIT — ledger + structure rename - PR #2745 (cool-carp-720): surfaced; WI-2 implementation needs realign - PR #2746 (MERGED): docs/design-ci-workflow-emitter-dispatch.md needs follow-on rename PR (post-cascade-clear) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 12, 2026
briansrls
added a commit
that referenced
this pull request
May 12, 2026
…file
- Delete scripts/slow-test-exemptions.txt (R3 row 102 state-check).
- Add scripts/test-node-wall-clock-ratchet.jsonl: 83 {"test","policy":"warn"}
rows migrated from the retired file (structural carrier for warn-only
ratchet policy; aligns with TestNodeCostDimension / gate #101).
- Rewire scripts/check-test-timeout.sh: jq-backed manifest lookup, drop
TEST_TIMEOUT_MAX_EXEMPTIONS row-count ratchet; require jq.
- Update ci.yml ratchet comments; refresh verification.dag comments for new path.
- Lane2d test rustdoc points at the JSONL manifest.
Merge: origin/main including #2761 (4d5305b).
Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls
added a commit
that referenced
this pull request
May 12, 2026
…chet) * fix(tests): share lane2d symbolic-cost fixtures in compile cache Unify (source, file) keys for countdown and literal/scalar-op pairs so cached_compile_to_dag amortizes cold bootstrap. Remove three Phase-0 slow-test exemptions and lower TEST_TIMEOUT_MAX_EXEMPTIONS to 80. T-WAD Slice 6: lane2_stage_2d cost-dimension test ratchet paydown. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(tests): restore lane2d slow-test exemptions after codex BLOCKING Shared cached_compile keys amortize duplicate work but do not prove sole-filter <=2s wall receipts or isolate libtest parallel contention (api-review/codex BLOCKING on #2764). Re-list the three lane2d tests and reset TEST_TIMEOUT_MAX_EXEMPTIONS default to 83. Document on the shared-key consts that cache sharing is not a Phase-0 exemption dissolution receipt. Co-authored-by: Cursor <cursoragent@cursor.com> * feat(ci): Phase B gate #102 — JSONL warn manifest replaces exemption file - Delete scripts/slow-test-exemptions.txt (R3 row 102 state-check). - Add scripts/test-node-wall-clock-ratchet.jsonl: 83 {"test","policy":"warn"} rows migrated from the retired file (structural carrier for warn-only ratchet policy; aligns with TestNodeCostDimension / gate #101). - Rewire scripts/check-test-timeout.sh: jq-backed manifest lookup, drop TEST_TIMEOUT_MAX_EXEMPTIONS row-count ratchet; require jq. - Update ci.yml ratchet comments; refresh verification.dag comments for new path. - Lane2d test rustdoc points at the JSONL manifest. Merge: origin/main including #2761 (4d5305b). Co-authored-by: Cursor <cursoragent@cursor.com> * docs(testing): Phase-0 ratchet + fail-closed policy after gate #102 - TESTING.md: document JSONL warn manifest, #101/#102 linkage, no TEST_TIMEOUT_MAX_EXEMPTIONS floor, same-PR rule for new warn rows. - check-test-timeout.sh header: explicit fail-closed policy block. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(ci): refresh bootstrap snapshots after verification.dag edits regen_bootstrap --verify failed: committed bootstrap embeds span byte ranges for src/v3/std/verification.dag; comment edits shifted line lengths. Regenerated with bootstrap-regen-fresh. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: T-WAD Slice 6: slow_test_exemptions_dissolved (test cost-dim cuts) * WIP: T-WAD Slice 6: slow_test_exemptions_dissolved (test cost-dim cuts) --------- Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls
added a commit
that referenced
this pull request
May 12, 2026
#10514 finding) claude review #10514 (APPROVE_WITH_COMMENTS) caught 4 stale "102 R3-load-bearing" references the initial sed sweep missed: - :88 "forward-looking R3 close target is 102" - :114 "**102** R3-load-bearing gates green" - :335 "R3-load-bearing §1.8 lane gates GREEN (102 load-bearing..." - :624 "R3-load-bearing §1.8 gates GREEN (**102** load-bearing..." All 4 updated to 103. INVARIANTS P2 single-authority within the same doc — gate-count must be consistent across all references. Remaining "102" references are legitimate gate IDs (#102 `slow_test_exemptions_dissolved` itself) — not stale counts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
4 tasks done
briansrls
added a commit
that referenced
this pull request
May 12, 2026
…ss dissolution gate per Director ratification msg_915aa2c1) (#2804) * docs(r3): §1.8 row #104 — lens_read_witness_shape_dissolved (Miss-class dissolution gate) Director ratification msg_915aa2c1 (b-with-refinements disposition) ratifies §1.8 row #104 addition with: - 2-part predicate (Part A terminal `git grep -nE "Lookup<" src/v3/lenses/ src/v3/std/ ; expected = 0` + Part B regression `git grep -nE "::Miss\b" src/v3/compiler/src/lens_*_generated.rs ; expected = 0`) - Bundled-migration shape (Substrate primary + Testgen companion, NOT one) - Status progression refinement (CONSUMER_LANDED requires BOTH brief authored ≥3 lens carriers AND ≥1 universal-coverage TestClaim landed) - Lane T-Lens-Behavioral-Parity (cross-lens read-channel discipline) Scope at HEAD (Director-grep msg_cefcbe05): 64 sites across cost.dag (25) + complexity.dag (25) + substrate.dag (3) + lookup.dag (11). Parallelism + effect_enumeration + timing_lens .dag layers already clean (0 sites). Authority chain: operator directive 2026-05-11 (audit §0) + audit §3.1/§3.4 + design-lens-framework.md:51,326,382-384 + design-emission-model.md:958,1206 + R4.D §4 (WISHLIST.md:147). Canvas-framing relayed to Substrate Mgr per Director ratification: Q-MissOrError + Q-WhyTestgenMissed + bundled-migration shape. Brief authoring in their Wave-2 queue. Gate-count canonicalization updated: 103→104 enumerated; 102→103 R3-load-bearing; composition total 87+16+1=104; all references swept. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): sweep remaining "102" → "103" load-bearing references (claude #10514 finding) claude review #10514 (APPROVE_WITH_COMMENTS) caught 4 stale "102 R3-load-bearing" references the initial sed sweep missed: - :88 "forward-looking R3 close target is 102" - :114 "**102** R3-load-bearing gates green" - :335 "R3-load-bearing §1.8 lane gates GREEN (102 load-bearing..." - :624 "R3-load-bearing §1.8 gates GREEN (**102** load-bearing..." All 4 updated to 103. INVARIANTS P2 single-authority within the same doc — gate-count must be consistent across all references. Remaining "102" references are legitimate gate IDs (#102 `slow_test_exemptions_dissolved` itself) — not stale counts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 13, 2026
briansrls
added a commit
that referenced
this pull request
May 14, 2026
Follows the same convention as sibling r3_free_consequences_second_batch_test::cross_target_optimization_cost_structurally_derived_receipt (TESTING.md / lane2d note: heavy libtests stay listed until gate #102). Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls
added a commit
that referenced
this pull request
May 14, 2026
…ens-Composition) (#3087) * WIP: R3 gate #38: coercion_cost_equals_complexity_by_construction (T-CostLens * chore: apply cargo fmt for gate #38 receipt Co-authored-by: Cursor <cursoragent@cursor.com> * fix: register gate #38 integration test in wall-clock warn manifest Follows the same convention as sibling r3_free_consequences_second_batch_test::cross_target_optimization_cost_structurally_derived_receipt (TESTING.md / lane2d note: heavy libtests stay listed until gate #102). Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
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
2 participants
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.
Move endpoint_use_count from per-module scope to global scope in
add_service_call_edges so that callables in different modules calling
the same service operation each get their own cloned transport triplet
instead of wiring duplicate scalar edges to the shared original.
https://claude.ai/code/session_015ogXTmQoQPA15XpEnkTCng