New features

ac-cli/src/main/resources/agenticcode.properties

@@ -4,4 +4,4 @@
 server.url=http://localhost:8787
 # Stamped by manage-ac.sh (stamp_cli_version) from ac-code-server's agenticcode.version
 # at build time. "dev" means this jar wasn't built via manage-ac.sh.
-version=243
+version=245

ac-code-server/src/main/resources/application.properties

@@ -3,7 +3,7 @@ quarkus.http.port=8787
 # AgenticCode's own release counter (not the Maven project version) — bump this by hand for each
 # release. Single source of truth for the startup log line, GET /api/version, and the OpenAPI
 # info version (referenced below via property expression, not duplicated).
-agenticcode.version=243
+agenticcode.version=245
 # OpenAPI / Swagger UI (item 48) — the generated spec is the contract the web-UI TS client
 # is generated against. Served at /q/openapi (yaml/json); Swagger UI at /q/swagger-ui in dev.
 mp.openapi.extensions.smallrye.info.title=AgenticCode API

x-docs/roadmap.md

@@ -397,16 +397,20 @@ its probe was not ambiguous, so the answer had been correct all along (see the r
   per-file node — so "unchanged" is answerable for files that contribute no module. Until then the
   floor is harmless but real, and it makes `changedOnly`'s numbers look wrong to anyone who counts.
 
-- [ ] **133. The item-128 reference index costs 3-5x deep-refresh time; decide whether that trade is right**
+- [ ] **133. The item-128 reference index costs 3-5x deep-refresh time** (POSTPONED 2026-08-20 — the cost is accepted;
+  deep refresh at this speed is fine. Revisit only if the loop becomes painful.)
 
   **Measured 2026-08-19** (same machine, same corpus, before → after item 128): `ac` 19s → **106s**,
   `app` 37s → **106s**, `pur` 29s → **125s**, `upms` 1230s → **1496s**.
 
   The index is genuinely useful (`PartnerController`: 65 sites, incl. two files a rename pass had
-  missed), but nobody has decided that its cost is worth paying on *every* refresh. Worth measuring
-  which emission dominates — imports (~26.6k on `pur`) vs declared type positions (~13.4k) vs
-  annotation usages — and considering a narrower default (imports + annotations only, with declared
-  types behind a flag), or emitting mentions only in the deep tier rather than in the Tier-1 scan.
+  missed). **Decision 2026-08-20: the trade is accepted** — a 2-minute Java refresh and a 25-minute
+  `upms` refresh are tolerable for what the index gives back, and item 129's `?paths=` /
+  `?changedOnly=` cover the fast inner loop. Kept open, not closed, because the analysis below is
+  still the right starting point if the cost ever does become painful: measure which emission
+  dominates — imports (~26.6k on `pur`) vs declared type positions (~13.4k) vs annotation usages —
+  then consider a narrower default (imports + annotations only, declared types behind a flag), or
+  emitting mentions only in the deep tier rather than in the Tier-1 scan.
 
 ## Web UI — code understanding & navigation