sourcecode 2.0.0__tar.gz → 2.0.1__tar.gz

{sourcecode-2.0.0 → sourcecode-2.0.1}/CHANGELOG.md

@@ -1,49 +1,30 @@
 # Changelog
 
-## [2.0.0] — 2026-07-06
-
-**ASK Engine 2.0** — the product identity is now final. The engine is unchanged;
-this major marks the CLI/product rename and is fully backward compatible.
-
-### Changed — canonical command is now `ask`
-
-- **`ask` is the canonical CLI command.** `ask impact`, `ask migrate-check`,
-  `ask review-pr`, `ask mcp init`, `ask activate …` — one short verb that matches
-  the product name (ASK Engine).
-- **`sourcecode` becomes a deprecated compatibility alias.** It keeps working
-  (same single implementation, `prog_name` pinned to `ask`), prints a one-line
-  deprecation notice **only on an interactive terminal**, and forwards to `ask`.
-  Pipes and agents that still call `sourcecode` get byte-identical stdout **and**
-  clean (JSON-only) stderr — the machine contract is unchanged. The alias will be
-  removed in a future major.
-- **New welcome wordmark**: a large `ASK` block with an `E N G I N E` label
-  replaces the old `SOURCE`/`CODE` banner. Help and banners read `CLI: ask`.
-- **Config home moved to `~/.ask`** (canonical writes); the legacy `~/.sourcecode`
-  is still read as a fallback, so **no existing user loses their license or config**.
-  Cache dir (`.sourcecode-cache/`) and `SOURCECODE_*` env vars are unchanged.
-- **MCP**: `ask mcp init` registers the client entry under `ask`; a pre-existing
-  `sourcecode` entry is recognized and migrated (and both are removed on
-  `mcp remove`).
-- **Docs**: README, user guide, manual, tiers, demo and onboarding now say
-  **ASK Engine** and use `ask …` in every example. Package/install/config and
-  compatibility references are preserved and the compatibility strategy is
-  documented in `docs/PRODUCT_IDENTITY.md` (normative).
-
-### Compatibility
-
-- **PyPI/Homebrew distribution stays `sourcecode` this release**; installing it
-  provides both the `ask` and `sourcecode` commands. Renaming the distribution to
-  `ask-engine` is a separate, explicitly-breaking future change.
-- Python package/import name (`sourcecode`), MCP protocol identity, cache format,
-  and all serialized/JSON outputs are unchanged.
-
-### Also in this line (identity + precision, pre-2.0 increments)
-
-- **Impact/`review-pr`**: a changed repository/service now surfaces **every**
-  affected entry point (controller) instead of collapsing an N-controller blast
-  radius to one — bounded by `max_impacts`, no new semantic fact, hash-neutral.
-- **Product identity consolidation**: audited every `sourcecode` occurrence and
-  established `docs/PRODUCT_IDENTITY.md` as the normative product↔CLI mapping.
+## [2.0.1] — 2026-07-10
+
+### Added
+
+- **`migrate-check --compact` — bounded decision summary.** A new opt-in view of the
+  migration report that keeps every decision field (readiness scores, headline blocker,
+  blocking count, estimated effort, executive summary, Hibernate classification, aggregate
+  counts) and caps each large collection to its top items with a `+N more` count. On real
+  monoliths the report shrinks ~97% (BroadleafCommerce 1.2 MB → 32 KB, OpenMRS 908 KB →
+  23 KB) — an agent or reviewer gets the verdict without the leaf-level firehose. The full
+  report remains the default output.
+
+### Fixed
+
+- **`onboard` project summary no longer leaks raw README markup.** READMEs that open with
+  a logo block (`<img>` / `<p>` HTML) or use inline markdown links (`[label](url)`) had
+  produced summaries like `API: <img src="…"/>`. The summary is now rendered to clean prose
+  — HTML/badge blocks are skipped and inline links are unwrapped to their label.
+- **More complete blast radius in `impact` and `review-pr`.** Change-impact analysis now
+  surfaces every affected entry point for a changed repository/service, reducing missed
+  callers on interface- and DI-wired code.
+
+### Notes
+
+- No breaking changes. Default command outputs are unchanged except where explicitly noted.
 
 ## [1.73.0] — 2026-07-01
 

{sourcecode-2.0.0 → sourcecode-2.0.1}/CONTRIBUTING.md

@@ -30,8 +30,8 @@ This installs `sourcecode` in editable mode with all development dependencies (`
 ### Run the CLI locally
 
 ```bash
-ask . --agent
-ask . prepare-context explain
+sourcecode . --agent
+sourcecode . prepare-context explain
 ```
 
 ### Run tests
@@ -150,7 +150,7 @@ Keep commits atomic. One logical change per commit.
 ## Reporting bugs
 
 Open an issue with:
-- `ask --version` output
+- `sourcecode --version` output
 - Command you ran
 - Expected behavior
 - Actual behavior / error output

{sourcecode-2.0.0 → sourcecode-2.0.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sourcecode
-Version: 2.0.0
+Version: 2.0.1
 Summary: Persistent structural context and ultra-fast repeated analysis for AI coding agents
 License-File: LICENSE
 Keywords: agents,ai,codebase,context,developer-tools,llm
@@ -40,14 +40,12 @@ Description-Content-Type: text/markdown
 
 **Persistent structural context and ultra-fast repeated analysis for AI coding agents.**
 
-![Version](https://img.shields.io/badge/version-2.0.0-blue)
+![Version](https://img.shields.io/badge/version-2.0.1-blue)
 ![Python](https://img.shields.io/badge/python-3.9%2B-green)
 
-> **ASK Engine** is the product. The CLI command is **`ask`**. The legacy
-> **`sourcecode`** command still works as a deprecated compatibility alias (it prints
-> a one-line notice and forwards to `ask`) and remains the Python/PyPI package name
-> for now. The authoritative version is whatever `ask version` reports. See
-> [docs/PRODUCT_IDENTITY.md](docs/PRODUCT_IDENTITY.md).
+> **ASK Engine** is the product. The CLI you install and run is **`sourcecode`** (the
+> executable and Python package). The authoritative version is whatever
+> `sourcecode version` reports.
 
 ---
 
@@ -83,19 +81,19 @@ Cache keyed on content hashes — invalidated only when source changes. On repea
 
 ## What changes at 0.3s vs 2.7s
 
-At 2.7s per call, you use ASK Engine to occasionally inspect a repo.
+At 2.7s per call, you use sourcecode to occasionally inspect a repo.
 
-At 0.3s per call, you use ASK Engine as **constant infrastructure** inside agent loops:
+At 0.3s per call, you use sourcecode as **constant infrastructure** inside agent loops:
 
 ```
 agent loop iteration:
-  1. ask . --compact          # 0.3s — instant structural context
-  2. ask impact PaymentService . --depth 1   # 0.4s — blast radius check
+  1. sourcecode . --compact          # 0.3s — instant structural context
+  2. sourcecode impact PaymentService . --depth 1   # 0.4s — blast radius check
   3. agent makes targeted change
   4. repeat
 ```
 
-Sub-second context retrieval changes the cost model for agent workflows. You can call ASK Engine before every edit, before every PR review, before every test run — without batching or caching calls manually.
+Sub-second context retrieval changes the cost model for agent workflows. You can call sourcecode before every edit, before every PR review, before every test run — without batching or caching calls manually.
 
 ---
 
@@ -116,20 +114,11 @@ pip install sourcecode
 pipx install sourcecode
 ```
 
-> **Package vs. command.** The install package is still named `sourcecode` this
-> release (renaming the PyPI/Homebrew distribution is a separate, breaking change).
-> Installing it gives you the canonical **`ask`** command plus the deprecated
-> **`sourcecode`** alias. A future release will publish `ask-engine` and drop the
-> alias.
-
 ### Verify
 
 ```bash
-ask version
-# ask 2.0.0
-
-# the deprecated alias still works (prints a one-line notice to stderr):
 sourcecode version
+# sourcecode 2.0.1
 ```
 
 ---
@@ -138,45 +127,45 @@ sourcecode version
 
 ```bash
 # High-signal summary — warm cache: ~0.3s, cold: 2–10s depending on repo size
-ask --compact
+sourcecode --compact
 
 # Add git hotspots and uncommitted file count
-ask --compact --git-context
+sourcecode --compact --git-context
 
 # Structured output for AI agents — bounded, noise-free, ready to inject
-ask --agent
+sourcecode --agent
 
 # Blast radius: what breaks if this class changes?
-ask impact OrderService /path/to/repo
+sourcecode impact OrderService /path/to/repo
 
 # Spring Boot 2→3 migration readiness: javax→jakarta blockers, removed APIs
-ask migrate-check /path/to/repo
+sourcecode migrate-check /path/to/repo
 
 # Spring semantic audit: TX anomalies + security surface (free)
-ask spring-audit /path/to/repo
+sourcecode spring-audit /path/to/repo
 
 # Impact chain: systemic blast radius with TX/SEC enrichment (free)
-ask impact-chain OrderService /path/to/repo
+sourcecode impact-chain OrderService /path/to/repo
 
 # Event topology: publisher → event → consumer graph (free)
-ask impact-chain OrderPlacedEvent /path/to/repo --type events
+sourcecode impact-chain OrderPlacedEvent /path/to/repo --type events
 
 # REST endpoint surface
-ask endpoints /path/to/repo
+sourcecode endpoints /path/to/repo
 
 # Request-body validation per endpoint: constraints + custom validators (free)
 # Recovers constraints from the OpenAPI spec, or directly from Java DTO
 # bean-validation annotations when no spec is present.
-ask validation /path/to/repo
+sourcecode validation /path/to/repo
 
 # Onboard to an unfamiliar codebase
-ask onboard /path/to/repo
+sourcecode onboard /path/to/repo
 
 # PR review: risk, test gaps, changed modules
-ask review-pr /path/to/repo --since main
+sourcecode review-pr /path/to/repo --since main
 
 # Bug triage: risk-ranked files by symptom
-ask fix-bug /path/to/repo --symptom "NullPointerException in checkout"
+sourcecode fix-bug /path/to/repo --symptom "NullPointerException in checkout"
 ```
 
 ---
@@ -194,21 +183,21 @@ ASK Engine maintains a persistent cache at `.sourcecode-cache/` inside each repo
 
 ```bash
 # Inspect cache state
-ask cache status
+sourcecode cache status
 
 # Warm the cache ahead of an agent session
-ask cache warm
+sourcecode cache warm
 
 # Clear cache
-ask cache clear
+sourcecode cache clear
 
 # Check RIS freshness relative to current git HEAD
-ask cache freshness
+sourcecode cache freshness
 ```
 
 **`--no-cache`** bypasses both layers and forces a fresh scan. Use in CI or when you need to verify a fresh result.
 
-**Visibility:** Cache hits are silent. Use `ask cache status` to see cache size, hit keys, and last-warmed timestamp.
+**Visibility:** Cache hits are silent. Use `sourcecode cache status` to see cache size, hit keys, and last-warmed timestamp.
 
 ---
 
@@ -218,66 +207,66 @@ ask cache freshness
 
 ```bash
 # Inject as first message to agent (bounded, deterministic)
-ask /repo --compact              # ~2,500–4,000 tokens
-ask /repo --agent               # ~4,500–5,500 tokens — more detail
-ask onboard /repo               # task-structured: entry points, key files, gaps
+sourcecode /repo --compact              # ~2,500–4,000 tokens
+sourcecode /repo --agent               # ~4,500–5,500 tokens — more detail
+sourcecode onboard /repo               # task-structured: entry points, key files, gaps
 ```
 
 ### Before every change — blast radius + TX/SEC check
 
 ```bash
 # Always target the INTERFACE in Spring projects, not the implementation:
-ask impact OrderService /repo           # ✓ 30 callers, 11 endpoints
-ask impact OrderServiceImpl /repo       # ✗ 0 callers (Spring DI blindness)
+sourcecode impact OrderService /repo           # ✓ 30 callers, 11 endpoints
+sourcecode impact OrderServiceImpl /repo       # ✗ 0 callers (Spring DI blindness)
 
 # Impact chain: blast radius enriched with TX boundary and security surfaces
-ask impact-chain OrderService /repo
+sourcecode impact-chain OrderService /repo
 
 # Event topology: who publishes/consumes this event, and in what TX phase?
-ask impact-chain OrderPlacedEvent /repo --type events
+sourcecode impact-chain OrderPlacedEvent /repo --type events
 
 # Spring audit: catch TX anomalies before they hit production
-ask spring-audit /repo --scope tx
+sourcecode spring-audit /repo --scope tx
 ```
 
 ### Continuous agent loop — delta context
 
 ```bash
 # Only changed files + their transitive importers — minimal token cost:
-ask prepare-context delta /repo --since HEAD~1
-ask . --changed-only --git-context
+sourcecode prepare-context delta /repo --since HEAD~1
+sourcecode . --changed-only --git-context
 ```
 
 ### PR review — structured risk signal
 
 ```bash
 # JSON for programmatic use:
-ask review-pr /repo --since main --output review.json
+sourcecode review-pr /repo --since main --output review.json
 jq '.ci_decision' review.json    # "analysis_success" | "git_ref_error"
 
 # Markdown for GitHub comment:
-ask review-pr /repo --since main --format github-comment
+sourcecode review-pr /repo --since main --format github-comment
 ```
 
 ### Bug triage — symptom-driven
 
 ```bash
 # Specific symptoms produce the best signal:
-ask fix-bug /repo --symptom "OIDC token refresh fails after realm update"
-ask fix-bug /repo --symptom "NullPointerException in OrderService during checkout"
+sourcecode fix-bug /repo --symptom "OIDC token refresh fails after realm update"
+sourcecode fix-bug /repo --symptom "NullPointerException in OrderService during checkout"
 
 # Generic symptoms produce noisy output — be specific.
-ask fix-bug /repo --symptom "payment timeout" --output triage.json
+sourcecode fix-bug /repo --symptom "payment timeout" --output triage.json
 ```
 
 ### In CI — cached, deterministic, fast
 
 ```bash
 # Content-hash cached — safe to run on every commit; cold only when code changes
-ask /repo --compact --output context.json
+sourcecode /repo --compact --output context.json
 
 # PR gate
-ask review-pr /repo --since $BASE_REF --output review.json
+sourcecode review-pr /repo --since $BASE_REF --output review.json
 DECISION=$(jq -r '.ci_decision' review.json)
 if [ "$DECISION" != "analysis_success" ]; then echo "Review failed: $DECISION"; fi
 ```
@@ -335,7 +324,7 @@ when the work gets bigger or automated.
 files only, by design. ASK Engine monetises enterprise Java monoliths.
 
 ```bash
-ask activate <key>      # activate a license key
+sourcecode activate <key>      # activate a license key
 ```
 
 Full breakdown: [docs/PRODUCT_TIERS.md](docs/PRODUCT_TIERS.md).
@@ -356,9 +345,9 @@ Core flags. Feed directly to AI agents as first-message context.
 ### `impact` — blast-radius analysis  [free ≤500 Java files · Pro above]
 
 ```bash
-ask impact ClassName /path/to/repo
-ask impact org.example.OrderService /path/to/repo   # FQN also accepted
-ask impact OrderService . --depth 2                 # limit BFS depth
+sourcecode impact ClassName /path/to/repo
+sourcecode impact org.example.OrderService /path/to/repo   # FQN also accepted
+sourcecode impact OrderService . --depth 2                 # limit BFS depth
 ```
 
 | Field | Description |
@@ -383,9 +372,9 @@ ask impact OrderService . --depth 2                 # limit BFS depth
 ### `endpoints` — REST API surface
 
 ```bash
-ask endpoints /path/to/repo
-ask endpoints /path/to/repo --output endpoints.json
-ask endpoints /path/to/repo --by-controller
+sourcecode endpoints /path/to/repo
+sourcecode endpoints /path/to/repo --output endpoints.json
+sourcecode endpoints /path/to/repo --by-controller
 ```
 
 Extracts all Spring MVC (`@GetMapping`, `@PostMapping`, `@RequestMapping`, etc.) and JAX-RS (`@GET`, `@POST`, `@Path`) endpoint methods. Returns HTTP method, path, controller class, and handler method. Each endpoint also carries its `return_type`. `--by-controller` groups the surface per controller (`{by_controller, controller_count, total}`) for an API-surface view.
@@ -414,10 +403,10 @@ Matching endpoints then report `policy: "custom"` with `annotation`, `resourceNa
 ### `export` — architecture views for downstream tooling
 
 ```bash
-ask export /path/to/repo --by-directory      # code map, path:line refs
-ask export /path/to/repo --module-graph       # module→module dependencies
-ask export /path/to/repo --integrations       # outbound HTTP/LDAP/JMS clients
-ask export /path/to/repo --c4                  # unified architecture + manifest
+sourcecode export /path/to/repo --by-directory      # code map, path:line refs
+sourcecode export /path/to/repo --module-graph       # module→module dependencies
+sourcecode export /path/to/repo --integrations       # outbound HTTP/LDAP/JMS clients
+sourcecode export /path/to/repo --c4                  # unified architecture + manifest
 ```
 
 Emits **structured, tool-agnostic** codebase views as plain JSON/YAML — the kind of input an architecture-doc generator, diagram renderer, or code-search agent can consume directly instead of walking the tree file by file. Section labels map to the open [C4 model](https://c4model.com) (an open architecture notation, not a product); the schema is vendor-neutral.
@@ -434,15 +423,15 @@ The section flags compose (pass several for one multi-section document); `--c4`
 ### `spring-audit` — Spring semantic audit [free]
 
 ```bash
-ask spring-audit /path/to/repo
-ask spring-audit /path/to/repo --scope tx           # TX anomalies only
-ask spring-audit /path/to/repo --scope security     # security surface only
-ask spring-audit /path/to/repo --min-severity high
+sourcecode spring-audit /path/to/repo
+sourcecode spring-audit /path/to/repo --scope tx           # TX anomalies only
+sourcecode spring-audit /path/to/repo --scope security     # security surface only
+sourcecode spring-audit /path/to/repo --min-severity high
 
 # CI/CD gate: exit 1 on any finding
-ask spring-audit . --ci
-ask spring-audit . --ci --min-severity high         # exit 1 only on high/critical
-ask spring-audit . --ci --format github-comment     # Markdown output + exit 1
+sourcecode spring-audit . --ci
+sourcecode spring-audit . --ci --min-severity high         # exit 1 only on high/critical
+sourcecode spring-audit . --ci --format github-comment     # Markdown output + exit 1
 ```
 
 Detects structural Spring anomalies that survive code review and tests, but cause production failures:
@@ -465,9 +454,9 @@ Endpoints guarded by a project-specific authorization annotation are treated as
 ### `impact-chain` — systemic blast radius with TX/SEC enrichment [free]
 
 ```bash
-ask impact-chain OrderService /path/to/repo
-ask impact-chain com.example.OrderService#placeOrder /path/to/repo
-ask impact-chain PaymentService . --depth 6
+sourcecode impact-chain OrderService /path/to/repo
+sourcecode impact-chain com.example.OrderService#placeOrder /path/to/repo
+sourcecode impact-chain PaymentService . --depth 6
 ```
 
 Unlike `impact` (which traces the caller graph), `impact-chain` builds on the SpringSemanticModel to enrich every step of the blast cone with transaction and security context:
@@ -494,7 +483,7 @@ Unlike `impact` (which traces the caller graph), `impact-chain` builds on the Sp
 **Event topology** — query the publisher/consumer graph for a Spring event class:
 
 ```bash
-ask impact-chain OrderPlacedEvent /path/to/repo --type events
+sourcecode impact-chain OrderPlacedEvent /path/to/repo --type events
 ```
 
 | Field | Description |
@@ -514,8 +503,8 @@ ask impact-chain OrderPlacedEvent /path/to/repo --type events
 ### `cold-start` — RIS bootstrap context
 
 ```bash
-ask cold-start /path/to/repo
-ask cold-start /path/to/repo --compact   # ~10K token subset
+sourcecode cold-start /path/to/repo
+sourcecode cold-start /path/to/repo --compact   # ~10K token subset
 ```
 
 Returns the Repository Intelligence Snapshot (RIS) instantly — zero re-analysis. The RIS is built by a prior warm cache pass and includes stacks, entry points, endpoint surface, and Spring semantic signals. Status field: `cold_start_ready` | `cold_start_stale` | `no_ris`.
@@ -525,12 +514,12 @@ Use `--compact` to get a ~10K token subset safe for direct LLM injection. Full s
 ### `repo-ir` — symbol-level IR
 
 ```bash
-ask repo-ir /path/to/repo --summary-only                  # ~20K tokens
-ask repo-ir /path/to/repo --since HEAD~1                   # symbol-level diff
-ask repo-ir /path/to/repo --files src/.../OrderService.java
-ask repo-ir /path/to/repo --max-nodes 200 --max-edges 500  # limit graph size
-ask repo-ir /path/to/repo --output ir.json.gz --gzip       # compressed output (~70-80% smaller)
-ask repo-ir /path/to/repo --include-tests                   # include test files
+sourcecode repo-ir /path/to/repo --summary-only                  # ~20K tokens
+sourcecode repo-ir /path/to/repo --since HEAD~1                   # symbol-level diff
+sourcecode repo-ir /path/to/repo --files src/.../OrderService.java
+sourcecode repo-ir /path/to/repo --max-nodes 200 --max-edges 500  # limit graph size
+sourcecode repo-ir /path/to/repo --output ir.json.gz --gzip       # compressed output (~70-80% smaller)
+sourcecode repo-ir /path/to/repo --include-tests                   # include test files
 ```
 
 Builds a deterministic symbol graph: classes, methods, import/injection edges, Spring roles, subsystems.
@@ -551,9 +540,9 @@ Builds a deterministic symbol graph: classes, methods, import/injection edges, S
 ### `explain` — architectural summary for a class
 
 ```bash
-ask explain UserService
-ask explain OrderController /path/to/repo
-ask explain UserService --format json
+sourcecode explain UserService
+sourcecode explain OrderController /path/to/repo
+sourcecode explain UserService --format json
 ```
 
 Human-readable architectural summary derived entirely from static analysis: Spring stereotype, public methods, incoming callers, outgoing dependencies, events published/consumed, `@Transactional` boundaries, security constraints, and related REST endpoints. JAVA/SPRING ONLY.
@@ -561,8 +550,8 @@ Human-readable architectural summary derived entirely from static analysis: Spri
 ### `pr-impact` — PR blast-radius report
 
 ```bash
-ask pr-impact --files changed_files.txt
-ask pr-impact /path/to/repo --files diff.txt --format json
+sourcecode pr-impact --files changed_files.txt
+sourcecode pr-impact /path/to/repo --files diff.txt --format json
 ```
 
 Takes a file listing changed Java files (one path per line) and produces a consolidated report: modified classes, affected REST endpoints reachable through the call chain, direct callers of each changed class, event publishers/consumers triggered, `@Transactional` methods in changed classes, and a consolidated risk level (`CRITICAL` / `HIGH` / `MEDIUM` / `LOW`). JAVA/SPRING ONLY.
@@ -570,13 +559,13 @@ Takes a file listing changed Java files (one path per line) and produces a conso
 ```bash
 # Typical CI usage: pipe git diff to a file, then run
 git diff --name-only main | grep '\.java$' > changed.txt
-ask pr-impact . --files changed.txt --format json
+sourcecode pr-impact . --files changed.txt --format json
 ```
 
 ### `onboard` — codebase orientation
 
 ```bash
-ask onboard /path/to/repo
+sourcecode onboard /path/to/repo
 ```
 
 Entry points, architecture summary, key files, confidence level, and gaps. Designed to be injected as agent context at the start of a session.
@@ -584,8 +573,8 @@ Entry points, architecture summary, key files, confidence level, and gaps. Desig
 ### `review-pr` — PR review context  [free ≤500 Java files · Pro above]
 
 ```bash
-ask review-pr /path/to/repo --since main
-ask review-pr /path/to/repo --since HEAD~3
+sourcecode review-pr /path/to/repo --since main
+sourcecode review-pr /path/to/repo --since HEAD~3
 ```
 
 Changed files, risk ranking, test coverage gaps, affected modules, and blast radius of changed classes. Returns a `ci_decision` field for CI/CD integration.
@@ -593,7 +582,7 @@ Changed files, risk ranking, test coverage gaps, affected modules, and blast rad
 ### `fix-bug` — Bug triage context  [free ≤500 Java files · Pro above]
 
 ```bash
-ask fix-bug /path/to/repo --symptom "NullPointerException in checkout"
+sourcecode fix-bug /path/to/repo --symptom "NullPointerException in checkout"
 ```
 
 Risk-ranked file list correlated to the symptom: keyword extraction, path matching, content matching, git commit correlation.
@@ -601,7 +590,7 @@ Risk-ranked file list correlated to the symptom: keyword extraction, path matchi
 ### `modernize` — Modernization planning  [free ≤500 Java files · Pro above]
 
 ```bash
-ask modernize /path/to/repo
+sourcecode modernize /path/to/repo
 ```
 
 High-coupling nodes (high fan-in = risky to change), dead zone candidates (isolated symbols), subsystem tangles.
@@ -609,12 +598,20 @@ High-coupling nodes (high fan-in = risky to change), dead zone candidates (isola
 ### `migrate-check` — Spring Boot 2→3 migration readiness
 
 ```bash
-ask migrate-check /path/to/repo
-ask migrate-check . --min-severity high
-ask migrate-check . --format text
-ask migrate-check . --output migration.json
+sourcecode migrate-check /path/to/repo
+sourcecode migrate-check . --compact          # bounded decision summary (score, blocker, effort, top items)
+sourcecode migrate-check . --min-severity high
+sourcecode migrate-check . --format text
+sourcecode migrate-check . --output migration.json
 ```
 
+`--compact` returns the decision-grade envelope — readiness scores, headline blocker,
+blocking count, estimated effort, executive summary, Hibernate classification and
+aggregate counts — with each large collection capped to its top items (`+N more`). On
+large monoliths this is ~97% smaller than the full report (e.g. 1.2 MB → 32 KB), so an
+agent or reviewer gets the verdict without the full leaf-level firehose. The complete
+report remains the default.
+
 Detects migration blockers across Java source files, Spring XML config files, and Maven/Gradle build files. 27 rules organized by target:
 
 **Jakarta namespace (MIG-001..009) — javax→jakarta**
@@ -789,19 +786,19 @@ evidence. `migrate-check` enforces:
 
 ```bash
 # inspect only the Hibernate rewrite targets
-ask migrate-check . --format json | jq '.hibernate.rewrite_targets[]'
+sourcecode migrate-check . --format json | jq '.hibernate.rewrite_targets[]'
 
 # product blockers only (excludes test/fixtures + hygiene)
-ask migrate-check . --format json | jq '.blocking_count, .non_blocking, .hygiene_findings'
+sourcecode migrate-check . --format json | jq '.blocking_count, .non_blocking, .hygiene_findings'
 ```
 
 ### `rename-class` — Java class rename
 
 ```bash
-ask rename-class . --from ServiceA --to ServiceB
-ask rename-class /path/to/repo --from OrderManager --to OrderService
-ask rename-class . --from OldName --to NewName --dry-run
-ask rename-class . --from OldName --to NewName --no-tests   # src/main only
+sourcecode rename-class . --from ServiceA --to ServiceB
+sourcecode rename-class /path/to/repo --from OrderManager --to OrderService
+sourcecode rename-class . --from OldName --to NewName --dry-run
+sourcecode rename-class . --from OldName --to NewName --no-tests   # src/main only
 ```
 
 Renames a Java class safely throughout the repository: declaration, constructor, all import statements, type references (fields, params, return types), `extends`/`implements`, generics, casts, and Spring `@Qualifier` names. Renames the physical `.java` file. Emits a structured change audit trail (`file`, `before_lines`, `after_lines`, `intent`, `diff`).
@@ -811,10 +808,10 @@ Use `--dry-run` to preview changes without writing to disk.
 ### `chunk-file` — split large Java files for agent consumption
 
 ```bash
-ask chunk-file BigService.java
-ask chunk-file BigService.java --max-lines 300
-ask chunk-file BigService.java --chunk 5          # read chunk 5 only
-ask chunk-file BigService.java --metadata-only    # boundaries only, no content
+sourcecode chunk-file BigService.java
+sourcecode chunk-file BigService.java --max-lines 300
+sourcecode chunk-file BigService.java --chunk 5          # read chunk 5 only
+sourcecode chunk-file BigService.java --metadata-only    # boundaries only, no content
 ```
 
 Splits a large Java file at method/class boundaries so AI agents can read files with 10K–25K+ lines in context-sized pieces. Each chunk includes `chunk_id`, `start_line`, `end_line`, `chunk_type`, symbol name, a `context_header` (package + class + imports summary), and `content`. A `size_warning` flag marks methods that exceed `--max-lines` and cannot be split further.
@@ -824,7 +821,7 @@ Splits a large Java file at method/class boundaries so AI agents can read files
 Low-level access to all tasks with full options:
 
 ```bash
-ask prepare-context TASK [PATH] [OPTIONS]
+sourcecode prepare-context TASK [PATH] [OPTIONS]
 ```
 
 | Task | What it surfaces |
@@ -883,9 +880,9 @@ All outputs include:
 Anonymous, **on by default (opt-out)**. Collects: version, OS, commands, flags, duration, repo size range, errors. No source code, paths, secrets, or output content. A one-time notice is shown on first interactive run.
 
 ```bash
-ask telemetry status
-ask telemetry enable
-ask telemetry disable
+sourcecode telemetry status
+sourcecode telemetry enable
+sourcecode telemetry disable
 ```
 
 Disable any time: `export SOURCECODE_TELEMETRY=0` (or `DO_NOT_TRACK=1`)
@@ -895,7 +892,7 @@ Disable any time: `export SOURCECODE_TELEMETRY=0` (or `DO_NOT_TRACK=1`)
 ## Configuration
 
 ```bash
-ask config    # show version, config file path, telemetry status
+sourcecode config    # show version, config file path, telemetry status
 ```
 
 ### `sourcecode.config.json` (repo root)