Conversation
Align CODE_MAP and the drift guard with docs/ledger/decisions/crates-io-publish-set.md Amendment 2026-06-07, which removed ergo-sdk-types before first publish.
Greptile SummaryThis PR repairs three weeks of red CI on
Confidence Score: 5/5Safe to merge — all four files make targeted, mechanical corrections with no production logic changes. Every change is a precise correction to a stale reference or formatting violation. The CODE_MAP and enforcement script are updated consistently (table row, prose, and count check all agree on five crates). The dispatch.rs diff is a pure formatter wrap with identical semantics. The badge URL resolves to the workflow file that actually exists in the repo. Nothing here touches runtime logic, data handling, or security boundaries. No files require special attention.
|
| Filename | Overview |
|---|---|
| README.md | Adds a CI badge pointing to the runtime-surface.yml workflow on main; the workflow file exists and the URL is well-formed. |
| crates/prod/CODE_MAP.md | Removes ergo-sdk-types from the crate inventory table and dependency-chain prose, updates heading and inline count check from six→five; all three touch-points are consistent. |
| crates/prod/clients/cli/src/cli/dispatch.rs | Pure cargo fmt line-wrap of one overlong if let expression; no logic change. |
| tools/verify_code_map_drift.sh | Removes crates/prod/clients/sdk-types from the prod_crates enforcement array and updates the expected count check from 6→5; other checks are untouched and still pass. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[CI red since 2026-06-13] --> B{Root causes}
B --> C[CODE_MAP still listed ergo-sdk-types as crate 6]
B --> D[dispatch.rs line too long for rustfmt]
B --> E[No badge — silent red main]
C --> F[Update CODE_MAP.md: six → five crates\nRemove ergo-sdk-types row & prose]
C --> G[Update verify_code_map_drift.sh:\nRemove sdk-types array entry\nCount check 6 → 5]
D --> H[cargo fmt wraps overlong if-let in dispatch.rs]
E --> I[Add runtime-surface.yml badge to README]
F --> J[CI green]
G --> J
H --> J
I --> K[Red main now visible immediately]
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
A[CI red since 2026-06-13] --> B{Root causes}
B --> C[CODE_MAP still listed ergo-sdk-types as crate 6]
B --> D[dispatch.rs line too long for rustfmt]
B --> E[No badge — silent red main]
C --> F[Update CODE_MAP.md: six → five crates\nRemove ergo-sdk-types row & prose]
C --> G[Update verify_code_map_drift.sh:\nRemove sdk-types array entry\nCount check 6 → 5]
D --> H[cargo fmt wraps overlong if-let in dispatch.rs]
E --> I[Add runtime-surface.yml badge to README]
F --> J[CI green]
G --> J
H --> J
I --> K[Red main now visible immediately]
Reviews (1): Last reviewed commit: "docs(readme): add runtime surface ci bad..." | Re-trigger Greptile
🤖 Augment PR SummarySummary: Fixes CI regressions by bringing prod CODE_MAP documentation and its drift-enforcement script back in sync with the current set of prod crates. 🤖 Was this summary useful? React with 👍 or 👎 |
What
Repairs main's CI, red since 2026-06-13 (three weeks). Three commits, four files, 13/12 lines:
crates/prod/CODE_MAP.md§1 andtools/verify_code_map_drift.shstill referencedergo-sdk-types, removed from the workspace before first publish (recorded:docs/ledger/decisions/crates-io-publish-set.md, amendment 2026-06-07). Both now reflect the five actual prod crates. The enforcement script edit removes one stale array entry and corrects the expected count; every other check is untouched.cli/dispatch.rs(from the alpha.2--versionhotfix) wrapped bycargo fmt; fmt-output only.Verification
cargo fmt --checkcleancargo test --workspace: 918 passed, 0 failed, 1 ignoredAudited per AGENT_CONTRACT v1.2 — scope proven exhaustively, no enforcement weakened. This PR run is itself the pre-merge proof: first green workflow since June 13 should appear on these checks.