agent-wiki-cli 3.1.0__tar.gz → 3.3.0__tar.gz

{agent_wiki_cli-3.1.0/src/agent_wiki_cli.egg-info → agent_wiki_cli-3.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agent-wiki-cli
-Version: 3.1.0
+Version: 3.3.0
 Summary: CLI tool to maintain hybrid LLM Wikis for multi-language projects.
 Author-email: Denis Sivagin <denissvgn@gmail.com>
 License-Expression: MIT
@@ -25,14 +25,16 @@ Requires-Dist: pytest>=7.0; extra == "dev"
 Requires-Dist: pytest-cov>=4.0; extra == "dev"
 Requires-Dist: jsonschema>=4.18; extra == "dev"
 Requires-Dist: markdown-it-py<5,>=4.0; extra == "dev"
-Requires-Dist: setuptools==83.0.0; extra == "dev"
+Requires-Dist: setuptools==84.1.0; extra == "dev"
 Requires-Dist: tomli>=2; extra == "dev"
 Provides-Extra: typescript
 Provides-Extra: go
 Provides-Extra: rust
 Provides-Extra: mcp
 Requires-Dist: mcp<2,>=1.27; python_version >= "3.10" and extra == "mcp"
+Requires-Dist: pydantic<3,>=2.11; python_version >= "3.10" and extra == "mcp"
 Requires-Dist: pydantic-settings<2.15,>=2.5.2; python_version >= "3.10" and extra == "mcp"
+Requires-Dist: uvicorn<1,>=0.31.1; (python_version >= "3.10" and sys_platform != "emscripten") and extra == "mcp"
 Dynamic: license-file
 
 # LLM Wiki CLI

{agent_wiki_cli-3.1.0 → agent_wiki_cli-3.3.0}/docs/automation.md

@@ -128,6 +128,11 @@ a different runtime identity and can prevent portable release-health comparison.
 On a source checkout, prepare and activate the ignored local toolchain before
 refreshing:
 
+Routine Node/npm preparation supports Linux x86_64, Linux ARM64 and macOS ARM64
+with platform-specific checksum-verified artifacts. Other language toolchains
+retain their own declared host limits; an ARM64 capture does not establish
+x86_64 execution or portable comparison.
+
 ```bash
 bash .github/scripts/setup-llm-wiki-ci-toolchains.sh --mode routine \
   --install-root .git/llm-wiki-ci-toolchains \
@@ -229,10 +234,20 @@ For an early diagnostic check before version preparation is complete, append
 `--stage contracts` to `run`. A partial invocation remains `blocked` for release
 readiness even when its checks succeed. Full execution runs the maintained
 host-applicable checks, independent builds and installed-artifact verification
-serially. It reports `failed`, `blocked`, or
-`local-ready-hosted-required`; the last result still requires normal hosted
+serially. It reports `failed`, `blocked`, `target-capture-required`,
+`target-runtime-unknown`, or `local-ready-hosted-required`; the last result still requires normal hosted
 qualification and all required target environments.
 
+Planning includes `readiness.target_runtime`, derived from the maintained proof
+owner and its composite runtime declarations. It reads committed wiki producer
+metadata without another application inventory. A known runtime mismatch needs
+the authorized target-host capture and review; unresolved declarations remain
+unknown. Local stage success cannot conceal either requirement. Advisory policy
+does not become a new mandatory gate. The generic installed
+[target prerequisite diagnostic](target-runtime-prerequisites.md) can also be
+used by other projects with their own declarations. Matching declared metadata
+is separate from package identity and fresh target-native proof.
+
 Local macOS success cannot establish Windows or Linux semantics, an unsupported
 helper or OCI architecture, an authenticated policy proof, or publication
 attestations. A missing capability remains pending. Continue through reviewed
@@ -240,6 +255,29 @@ main changes, current native CI and the existing qualification and publication
 procedure using its verified artifacts. Local rehearsal distributions and
 receipts cannot replace that evidence.
 
+### Reviewed broad release captures
+
+The ordinary convergence observer keeps its normal sync limits. A generator
+upgrade that exceeds those limits needs a complete preview and a separately
+authorized broad write. **Reviewed release wiki capture** provides that manual
+route without changing the observer or publishing repository changes.
+
+Dispatch `reviewed-wiki-capture.yml` from main with `operation=preview` and the
+exact current main SHA as `candidate-sha`. Review the full `preview.stdout` and
+its source, wiki, installed package, runtime and prepared-helper binding in
+`preview.json`. Preview does not produce an owning-sync receipt or a snapshot.
+After explicitly approving that complete plan, dispatch `operation=apply` with
+the same candidate and `approved-preview-sha256` from the reviewed result.
+Apply recomputes the complete preview and refuses a changed binding before
+invoking the broad writer. It never automatically retries a failed normal sync
+with force.
+
+The workflow retains the drift decision and complete successful writer output
+for review. A drift result can fail the run while retaining a valid snapshot;
+that snapshot is not policy approval or release qualification. Review and
+validate the whole capture before a separate wiki pull request. Neither
+operation commits, pushes, tags or publishes anything.
+
 ### Qualification after merging
 
 Repository release automation is disabled by default in

{agent_wiki_cli-3.1.0 → agent_wiki_cli-3.3.0}/docs/cli-reference.md

@@ -266,6 +266,13 @@ observations. A changed file refreshes its observations; deletions remove them.
 Cross-file class classification is recalculated after cached and fresh files
 are combined.
 
+A cache hit does not mean that all analysis was avoided. Read the fresh-file
+counters and extractor phases as well as the hit count. Invocations that capture
+Python implementation observations still perform fresh Python extraction;
+ordinary inventory reuse and committed sync-analysis reuse have different work
+and qualification scopes. Source content, rather than size or modification time
+alone, determines whether a per-file entry matches.
+
 After a successful sync records its generation inputs, an unchanged run can
 reuse the validated knowledge snapshot without rebuilding the graph or
 rewriting artifacts. Source/configuration, Markdown, assets, implementation,
@@ -287,12 +294,23 @@ The command reports `Sync analysis reuse: hit` or `miss` with a reason, and
 progress includes a `sync_analysis_reuse` phase. Missing, corrupted, oversized
 or redirected cache files fall back to ordinary analysis. Source changes,
 generated-section changes, unavailable helpers and incompatible inputs prevent
-reuse. Governed, maintenance-adopted and plugin-configured projects use ordinary
-analysis. `--no-cache`, `--rebuild-cache` and `--rebuild-knowledge` disable this
+reuse. An eligible ordinary maintenance owner is part of the input binding;
+cached observations never acknowledge review or replace current owner checks.
+Governed and plugin-configured projects use ordinary analysis.
+`--no-cache`, `--rebuild-cache` and `--rebuild-knowledge` disable this
 shortcut. An established unchanged snapshot is preserved without adding cache
 metadata solely to warm a cache. Standalone strict lint and CI still validate
 their own invocation inputs.
 
+Keep inventory caches in a trusted project-owned location. Restoring a
+sync-analysis file alone cannot authorize reuse without the matching native
+commitment. The integrity Action already restores exact prepared-helper caches
+and saves newly prepared ones only after successful default-branch pushes.
+Additional transport of application analysis data needs its own source-root,
+producer/runtime, settings and trust boundaries. Assess archive size, transfer,
+validation and required fresh work together; local warm timings do not establish
+a hosted net saving.
+
 `sync`, `lint`, and `ci-check` accept `--progress auto|always|never` and
 `--progress-format text|json`. Progress events are flushed to stderr. `auto`
 shows phases in an interactive terminal and heartbeats for long phases in
@@ -467,6 +485,21 @@ completeness. Generated import tables label these gaps with their reason and
 source line.
 Go `_test.go` files are omitted unless `--include-tests go` is supplied; Python
 test files remain part of normal Python extraction.
+Python deep extraction can capture a bounded static subset of nested helpers.
+A unique, unconditional, undecorated helper with no lexical free variables can
+resolve direct calls after its definition when its binding is neither reassigned
+nor escaped. These functions use qualified symbols such as
+`run.<locals>.clean` in the existing `nested_functions` list; optional
+`python_lexical_functions` witnesses identify the enclosing declaration and
+exact call locations. Their contract is `llm-wiki-python-lexical-functions/v1`.
+The original lexical call-binding records remain intact. Readers without these
+witnesses retain unresolved answers; malformed or unsupported witnesses cannot
+establish a target. Caller/callee queries and bounded flows use the same proven
+source target. Closure captures, callbacks, decorators, namespace mutation and
+ambiguous or reassigned bindings remain outside this subset. Extraction uses
+syntax and symbol tables without executing project imports; resolved static
+edges do not establish runtime behavior or complete flow coverage.
+
 JavaScript `.js` and `.jsx` files are handled by the TypeScript extractor
 family and use `language: "javascript"` in inventory output. Prepare the same
 helper with `llm-wiki prepare-extractors --language typescript`.
@@ -680,6 +713,42 @@ retain their normal blocking policy.
 Legacy wikis with no declared knowledge projection continue in surface-only
 mode. See [Native knowledge reads][native-knowledge-strict]
 for the complete policy.
+
+CI text, Markdown and Action summaries show structural integrity separately
+from the embedded non-strict advisory health result. A passing integrity check
+can accompany degraded health. Native drift is explicitly `disabled` or
+`report-only`; that diagnostic mode does not change the blocking integrity
+checks. Ordinary CI and doctor reports disclose release policy as unavailable:
+only the separate release-policy verifier can establish its outcome from
+authenticated evidence matching the candidate, scope and captured inputs.
+
+Full Markdown reports start with captured health guidance and a bounded diagnostic
+preview. The complete diagnostic index reconciles category/kind totals and links
+to every emitted row. Routine external-call boundaries appear separately from
+unresolved or unfamiliar call findings and explicit step/depth truncation. Preview
+returned/omitted counts describe emitted records; they do not establish that the
+underlying source analysis was complete. Canonical lint/CI JSON retains the
+original findings, severities and hints. CI text and compact Action summaries use
+the same category/kind distinctions without changing their existing failure rules.
+
+Python coverage diagnostics distinguish static compatibility redirects from
+implementation gaps. A single unconditional, import-bound
+`sys.modules[__name__]` redirect can produce an informational
+`module_source_routes` record naming its selected, extracted destination.
+The source path and captured hash remain visible; the route creates no duplicate
+implementation or durable governance alias and does not prove runtime import
+behavior. Destination wiki coverage is checked separately. Re-exports keep
+their own module entries. Conditional or dynamic redirects, ambiguous package
+bindings, cycles, excluded targets and missing extraction remain uncovered or
+unresolved rather than acquiring an inferred owner.
+
+Comment/docstring-only package initializers produce informational
+`module_source_presence` records with their captured hashes when they have no
+module entry. Initializers with declarations, exports or executable setup retain
+the normal coverage checks. Classification reads at most 1 MiB per selected file
+and follows at most 16 redirect hops; unavailable or bounded-out proof stays
+unresolved. It never executes project imports or changes source selection.
+
 `--profile` suppresses the human-readable lint text and prints one JSON object
 to stdout containing the normal lint report, diagnostics, and phase timings.
 The JSON contract is preserved for extractor failures as well; lint still exits
@@ -799,6 +868,13 @@ dependencies as warning diagnostics. These warnings are visible in human output
 and profile JSON but do not make `lint`, `lint --strict`, or `ci-check` fail by
 themselves. Stale architecture pages with no current source modules remain hard
 issues.
+Skipped unused-dependency checks name the actual manifest paths and source scope.
+Where supported by the captured scope and package ownership guard, they distinguish
+excluded bundled helper implementations, missing source witnesses, source present
+without extraction, and unsupported inputs. Unknown ownership or coverage stays
+unknown. Skipping provides no unused-package verdict and does not diagnose helper
+preparation. Review the exact named paths read-only; helper-specific verification
+or preparation remains a separate operation with its existing toolchain needs.
 Python dependency reconciliation reads `pyproject.toml` and `requirements*.txt`
 manifests, including nested manifests scoped to their directory. Python imports
 use the selected source root, conventional `src` layouts, and declared packaging
@@ -945,6 +1021,22 @@ llm-wiki doctor --wiki-dir docs/llm_wiki --src-dir . --strict
 The report composes the existing availability, live freshness, snapshot parity,
 governance and review, drift, and verification-receipt checks. It does not
 define a separate source analyzer. Human output is a compact screen summary.
+It states the health classification mode; `--strict` does not by itself prove
+release admission. The doctor Action separately displays its configured failure
+threshold, which remains independent of the report's classification mode.
+
+Governance adoption and running verification checkers are explicit operations;
+expected optional absence is disclosed without inventing review or semantic approval.
+A valid governance ledger does not establish current human-review coverage,
+and zero expired findings does not mean every section was reviewed. Inspect
+the scoped review records. A valid machine receipt covers its recorded scope
+and checks only. A stale receipt retains its historical result while current
+validity fails; stale, failed and invalid receipts remain unhealthy. Missing
+previously committed governance authority remains invalid and requires the
+exact ledger to be restored. Reports never adopt governance, acknowledge a
+review or execute verification checkers. See [`knowledge`](#knowledge) for
+explicit adoption, review and verification operations.
+
 For legacy knowledge, automatic JSON output uses `llm-wiki-doctor/v1` and contains the same
 six named sections, complete freshness counts when evaluation succeeds, and
 the required evaluated or snapshot-only disclosure.
@@ -977,6 +1069,18 @@ Snapshot hashes identify declared input sets and do not themselves prove freshne
 The v3 option cannot be combined with `--capabilities`, which retains its
 separate v2 contract.
 
+With native analysis metadata, fresh report diagnostics and live evidence
+explanations identify which contract, implementation, configuration or runtime
+commitments differ. Human health summaries use the same captured comparisons.
+Runtime-only drift calls for reviewing the execution runtime and target-host
+capture, rather than restoring unchanged configuration. Missing, unbound or
+unsupported comparisons remain explicitly unavailable.
+
+Historical primary reason codes and compact projection hints remain compatible.
+A configuration-related legacy reason code can group several analysis-basis
+differences; use the precise diagnostic and recorded/live commitments to choose
+the repair. Reporting does not perform preparation, sync or capture.
+
 To keep the health read from executing project plugin code, `doctor` never
 loads source plugins. Evidence that only a source plugin can produce may
 therefore be unavailable or basis-incompatible; strict mode can classify the
@@ -1073,11 +1177,46 @@ supplied files or a supplied diff, use the bounded
 `query_documentation` tool with the `impact` operation. Exact concept,
 related-concept, surface, and typed queries use the committed snapshot;
 supplied file or unified-diff impact queries use targeted extraction. Symbol,
-entrypoint, and dependency queries
+entrypoint, flow-segment, and dependency queries
 perform a full inventory only when `allow_full_inventory=true` is supplied.
 The context budget and focus bound emitted output after a full deep inventory;
 they do not make that scan computationally cheap.
 
+Inspect transitions omitted from a bounded flow with an exact callable owner:
+
+```bash
+printf '%s\n' '{"operation":"flow-segment","value":"src/orders.py:submit","allow_full_inventory":true}' | llm-wiki query --request - --src-dir . --wiki-dir docs/llm_wiki
+```
+
+The same request works through Python `query_documentation` and MCP
+`query_documentation` (inside its `request` argument). The additive
+`llm-wiki-flow-segment/v1` result uses `file:symbol`, including class or nested
+qualification when present. Missing or duplicate owners remain unselected.
+It returns at most 12 trace rows and keeps the existing depth limit of 6;
+`limit` can request fewer rows. Legacy flow and data-flow results retain their
+existing shapes, ordering and limits.
+
+Follow an available top-level `follow_up.request` to inspect the next rows.
+An available `steps[].follow_up.request` narrows a depth frontier to a new
+root in the same graph; its depths and counts start from that root. Supply the
+returned request unchanged, with the same roots, source selection and prepared
+helpers. Its `basis` binds captured source bytes, source generation/selection,
+producer commitments, graph order and traversal options. Changed bindings are
+rejected; restart instead of appending results from a different basis. An
+unavailable follow-up includes its reason, including missing capture bindings
+or a row that exceeds the delivery byte budget.
+
+`coverage` separates observed reachable rows, depth-eligible rows, returned
+rows, omissions before/after the page, and depth omissions. `work` separately
+counts the complete inventory/graph binding and graph traversal/counting work.
+Every CLI/MCP dispatcher request repeats full source inventory; a smaller
+segment does not make that inventory cheaper. For repeated Python queries,
+reuse `api.flow_segment("src/orders.py:submit", service=service)` on a built
+documentation query service. That route performs no new extraction or file I/O
+and answers the service's captured view; build a fresh service after source
+changes. Static order, a complete page or a matching binding never proves
+runtime execution, runtime completeness or live freshness.
+
 Explain one exact concept using the existing evidence service:
 
 ```bash

{agent_wiki_cli-3.1.0 → agent_wiki_cli-3.3.0}/pyproject.toml

@@ -1,11 +1,11 @@
 [build-system]
-requires = ["setuptools==83.0.0"]
+requires = ["setuptools==84.1.0"]
 build-backend = "release_build_backend"
 backend-path = ["."]
 
 [project]
 name = "agent-wiki-cli"
-version = "3.1.0"
+version = "3.3.0"
 description = "CLI tool to maintain hybrid LLM Wikis for multi-language projects."
 readme = "README.md"
 license = "MIT"
@@ -35,7 +35,7 @@ dev = [
     "pytest-cov>=4.0",
     "jsonschema>=4.18",
     "markdown-it-py>=4.0,<5",
-    "setuptools==83.0.0",
+    "setuptools==84.1.0",
     # Analyze Python 3.10 fallback imports from newer development interpreters.
     "tomli>=2",
 ]
@@ -49,7 +49,10 @@ rust = []
 # MCP server support uses the official Python MCP SDK, which requires Python 3.10+.
 mcp = [
     "mcp>=1.27,<2; python_version >= '3.10'",
+    # Directly used strict types and HTTP server; align with the supported SDK.
+    "pydantic>=2.11,<3; python_version >= '3.10'",
     "pydantic-settings>=2.5.2,<2.15; python_version >= '3.10'",
+    "uvicorn>=0.31.1,<1; python_version >= '3.10' and sys_platform != 'emscripten'",
 ]
 
 [project.urls]

{agent_wiki_cli-3.1.0 → agent_wiki_cli-3.3.0/src/agent_wiki_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agent-wiki-cli
-Version: 3.1.0
+Version: 3.3.0
 Summary: CLI tool to maintain hybrid LLM Wikis for multi-language projects.
 Author-email: Denis Sivagin <denissvgn@gmail.com>
 License-Expression: MIT
@@ -25,14 +25,16 @@ Requires-Dist: pytest>=7.0; extra == "dev"
 Requires-Dist: pytest-cov>=4.0; extra == "dev"
 Requires-Dist: jsonschema>=4.18; extra == "dev"
 Requires-Dist: markdown-it-py<5,>=4.0; extra == "dev"
-Requires-Dist: setuptools==83.0.0; extra == "dev"
+Requires-Dist: setuptools==84.1.0; extra == "dev"
 Requires-Dist: tomli>=2; extra == "dev"
 Provides-Extra: typescript
 Provides-Extra: go
 Provides-Extra: rust
 Provides-Extra: mcp
 Requires-Dist: mcp<2,>=1.27; python_version >= "3.10" and extra == "mcp"
+Requires-Dist: pydantic<3,>=2.11; python_version >= "3.10" and extra == "mcp"
 Requires-Dist: pydantic-settings<2.15,>=2.5.2; python_version >= "3.10" and extra == "mcp"
+Requires-Dist: uvicorn<1,>=0.31.1; (python_version >= "3.10" and sys_platform != "emscripten") and extra == "mcp"
 Dynamic: license-file
 
 # LLM Wiki CLI

{agent_wiki_cli-3.1.0 → agent_wiki_cli-3.3.0}/src/agent_wiki_cli.egg-info/SOURCES.txt

@@ -119,6 +119,7 @@ src/llm_wiki_cli/services/__init__.py
 src/llm_wiki_cli/services/analysis_capture.py
 src/llm_wiki_cli/services/analysis_compatibility.py
 src/llm_wiki_cli/services/analysis_contracts.json
+src/llm_wiki_cli/services/analysis_targets.py
 src/llm_wiki_cli/services/api_contracts.py
 src/llm_wiki_cli/services/api_diff.py
 src/llm_wiki_cli/services/bootstrap_runtime.py
@@ -163,6 +164,7 @@ src/llm_wiki_cli/services/extraction_jobs.py
 src/llm_wiki_cli/services/extraction_service.py
 src/llm_wiki_cli/services/extractor_helpers.py
 src/llm_wiki_cli/services/filesystem_guard.py
+src/llm_wiki_cli/services/flow_followup.py
 src/llm_wiki_cli/services/flow_overview.py
 src/llm_wiki_cli/services/freshness_wording.py
 src/llm_wiki_cli/services/go_calls.py
@@ -222,6 +224,7 @@ src/llm_wiki_cli/services/manifest_storage.py
 src/llm_wiki_cli/services/markdown_sections.py
 src/llm_wiki_cli/services/mcp_server.py
 src/llm_wiki_cli/services/metrics.py
+src/llm_wiki_cli/services/module_coverage.py
 src/llm_wiki_cli/services/module_maps.py
 src/llm_wiki_cli/services/native_inspection.py
 src/llm_wiki_cli/services/normalization_diagnostics.py
@@ -359,9 +362,11 @@ src/llm_wiki_cli/skills/wiki-sync/SKILL.md
 src/llm_wiki_cli/skills/wiki-sync/reference.md
 tests/test_action_runtimes.py
 tests/test_agent_instruction_decisions.py
+tests/test_analysis_basis_diagnostics.py
 tests/test_analysis_compatibility.py
 tests/test_analysis_input_preflight.py
 tests/test_analysis_qualification.py
+tests/test_analysis_targets.py
 tests/test_api.py
 tests/test_api_contracts.py
 tests/test_api_diff.py
@@ -375,6 +380,7 @@ tests/test_bootstrap.py
 tests/test_bootstrap_api_contracts.py
 tests/test_bootstrap_service.py
 tests/test_bump.py
+tests/test_cache_persistence_boundaries.py
 tests/test_calibration_cli.py
 tests/test_calibration_isolation.py
 tests/test_capability_diagnostics.py
@@ -420,6 +426,7 @@ tests/test_dependency_downloads.py
 tests/test_dependency_setup_probe.py
 tests/test_dependency_setup_workflow.py
 tests/test_dependency_version_details.py
+tests/test_derived_freshness_boundaries.py
 tests/test_developer_value_after_change.py
 tests/test_developer_value_before_change.py
 tests/test_developer_value_combined_compatibility.py
@@ -446,6 +453,7 @@ tests/test_developer_value_triage_acceptance.py
 tests/test_developer_value_triage_oracle.py
 tests/test_developer_value_triage_workflow_gate.py
 tests/test_developer_value_workflow_oracles.py
+tests/test_diagnostic_presentation.py
 tests/test_diagrams.py
 tests/test_docker_bootstrap.py
 tests/test_docker_extract.py
@@ -492,6 +500,7 @@ tests/test_extractor_inventory_contracts.py
 tests/test_filesystem_guard.py
 tests/test_filesystem_guard_windows.py
 tests/test_filesystem_guard_windows_model.py
+tests/test_flow_followups.py
 tests/test_flow_overview.py
 tests/test_flow_overview_receiving.py
 tests/test_freshness_wording.py
@@ -506,6 +515,7 @@ tests/test_graph_section_end_to_end.py
 tests/test_guarded_read_metadata.py
 tests/test_guide_landing_preservation.py
 tests/test_haskell_extract.py
+tests/test_health_decision_disclosures.py
 tests/test_health_details.py
 tests/test_helper_packaging_parity.py
 tests/test_helper_preparation.py
@@ -541,6 +551,7 @@ tests/test_knowledge_generation.py
 tests/test_knowledge_governance.py
 tests/test_knowledge_graph.py
 tests/test_knowledge_hardening.py
+tests/test_knowledge_health_integration.py
 tests/test_knowledge_health_refresh.py
 tests/test_knowledge_index.py
 tests/test_knowledge_links.py
@@ -625,6 +636,7 @@ tests/test_policy_source_freeze.py
 tests/test_preflight.py
 tests/test_preflight_contracts.py
 tests/test_preflight_runner.py
+tests/test_preflight_targets.py
 tests/test_progress.py
 tests/test_protected_artifacts.py
 tests/test_protocol_registry.py
@@ -638,12 +650,15 @@ tests/test_pytest_portability.py
 tests/test_python_binding_adversaries.py
 tests/test_python_binding_state_growth.py
 tests/test_python_call_bindings.py
+tests/test_python_class_imports.py
 tests/test_python_constructor_bindings.py
 tests/test_python_constructor_control_flow.py
 tests/test_python_constructor_resolution.py
 tests/test_python_go_path_diagnostics.py
 tests/test_python_implementation.py
 tests/test_python_import_scopes.py
+tests/test_python_lexical_calls.py
+tests/test_python_module_coverage.py
 tests/test_python_observation_cache.py
 tests/test_python_source_inventory.py
 tests/test_python_typed_dicts.py
@@ -666,6 +681,7 @@ tests/test_release_supply_chain.py
 tests/test_release_workflows.py
 tests/test_rendering_lifecycle.py
 tests/test_resource_diagnostics.py
+tests/test_reviewed_wiki_capture.py
 tests/test_route_projection_regressions.py
 tests/test_runtime_output.py
 tests/test_rust_extract.py
@@ -689,6 +705,7 @@ tests/test_skill_contracts_all.py
 tests/test_skill_ownership_boundaries.py
 tests/test_skill_policy_routes.py
 tests/test_skills.py
+tests/test_skipped_dependency_scopes.py
 tests/test_source_selection.py
 tests/test_source_snapshot.py
 tests/test_static_quality_architecture.py

{agent_wiki_cli-3.1.0 → agent_wiki_cli-3.3.0}/src/agent_wiki_cli.egg-info/requires.txt

@@ -8,7 +8,7 @@ pytest>=7.0
 pytest-cov>=4.0
 jsonschema>=4.18
 markdown-it-py<5,>=4.0
-setuptools==83.0.0
+setuptools==84.1.0
 tomli>=2
 
 [go]
@@ -17,8 +17,12 @@ tomli>=2
 
 [mcp:python_version >= "3.10"]
 mcp<2,>=1.27
+pydantic<3,>=2.11
 pydantic-settings<2.15,>=2.5.2
 
+[mcp:python_version >= "3.10" and sys_platform != "emscripten"]
+uvicorn<1,>=0.31.1
+
 [rust]
 
 [tokens]

{agent_wiki_cli-3.1.0 → agent_wiki_cli-3.3.0}/src/llm_wiki_cli/api.py

@@ -43,6 +43,7 @@ from .api_types import (
     EvidenceExplanationResult,
     ExtractSourceResult,
     FlowForEntrypointResult,
+    FlowSegmentResult,
     KnowledgeMode,
     KnowledgeCoverageResult,
     NativeInspectionResult,
@@ -718,6 +719,8 @@ _NATIVE_QUERY_ERROR_FIELDS = frozenset(
         "request",
         "operation",
         "value",
+        "basis",
+        "offset",
         "locator_or_exact_route",
         "limit",
         "paths",
@@ -882,6 +885,8 @@ def _raise_native_query_api_error(exc: Exception) -> NoReturn:
         else:
             message = {
                 "limit": "limit must be a positive integer; values above 100 are capped.",
+                "basis": "The flow binding is invalid or changed; restart with the same source selection, producer and traversal options.",
+                "offset": "Supply a valid offset from a bound flow-segment follow-up.",
                 "kinds": "Supply an iterable with at most 100 values and supported relationship kinds.",
                 "origins": "Supply an iterable with at most 100 values and supported origins.",
                 "resolutions": "Supply an iterable with at most 100 values and supported resolutions.",
@@ -2110,6 +2115,31 @@ def _effective_query_limit(
     return value if service is not None else _normalize_query_limit(value)
 
 
+@_api_boundary
+def flow_segment(
+    value: str,
+    *,
+    basis: str | None = None,
+    offset: int = 0,
+    service: DocumentationGraphQueryService | None = None,
+    src_dir: str = ".",
+    wiki_dir: str = DEFAULT_WIKI_DIR,
+    limit: int = 20,
+    allow_external_src: bool = False,
+    source_selection: str | Path | None = None,
+) -> FlowSegmentResult:
+    """Return a bounded exact-callable trace; reuse a service for no new extraction."""
+    from .services.flow_followup import validate_request
+
+    _normalize_query_input(lambda: validate_request(value, basis, offset))
+    bounded_limit = _effective_query_limit(service, limit)
+    return cast(FlowSegmentResult, _run_query(lambda: _query_service(
+        service, src_dir=src_dir, wiki_dir=wiki_dir, limit=bounded_limit,
+        allow_external_src=allow_external_src, read_only=True,
+        source_selection=source_selection,
+    ).flow_segment(value, basis=basis, offset=offset)))
+
+
 @_api_boundary
 def flow_for_entrypoint(
     id_or_symbol: object,
@@ -2558,6 +2588,7 @@ _DOCUMENTATION_QUERY_FIELDS = {
     ),
     "symbol": frozenset({"operation", "value", "limit", "allow_full_inventory"}),
     "entrypoint": frozenset({"operation", "value", "limit", "allow_full_inventory"}),
+    "flow-segment": frozenset({"operation", "value", "limit", "allow_full_inventory", "basis", "offset"}),
     "dependency": frozenset({"operation", "value", "limit", "allow_full_inventory"}),
     "impact": frozenset(
         {
@@ -2707,7 +2738,12 @@ def _validate_documentation_query_request(
     limit = _normalize_query_limit(request.get("limit", 20))
     # Operation-specific transport fields are input validation, not part of
     # loading the query service. Reject them before any workspace access.
-    if operation == "explain":
+    if operation == "flow-segment":
+        from .services.flow_followup import validate_request
+
+        _normalize_query_input(lambda: validate_request(request.get("value"), request.get("basis"), request.get("offset", 0)))
+        _require_full_inventory_opt_in(request)
+    elif operation == "explain":
         if type(request.get("live", False)) is not bool:
             raise InvalidRequestError("live must be a boolean.", code="invalid-request", details={"field": "live"})
         if type(request.get("allow_full_inventory", False)) is not bool:
@@ -3137,7 +3173,7 @@ def query_documentation(
             field="value",
         )
 
-    if operation in {"symbol", "entrypoint", "dependency"}:
+    if operation in {"symbol", "entrypoint", "dependency", "flow-segment"}:
         _require_full_inventory_opt_in(request)
         service = build_documentation_query_service(
             src_dir,
@@ -3238,6 +3274,8 @@ def query_documentation(
                 "callees": callee_result["bounds"]["callees"],
             }
         )
+    elif operation == "flow-segment":
+        payload = service.flow_segment(value, basis=request.get("basis"), offset=request.get("offset", 0))
     elif operation == "entrypoint":
         flow = service.flow_for_entrypoint(value)
         data_flow = service.data_flow_for_entrypoint(value)
@@ -3736,6 +3774,7 @@ __all__ = [
     "ExtractionError",
     "ExtractSourceResult",
     "FlowForEntrypointResult",
+    "FlowSegmentResult",
     "LlmWikiApiError",
     "InvalidRequestError",
     "KnowledgeMode",
@@ -3790,6 +3829,7 @@ __all__ = [
     "export_documentation_run",
     "extract_source",
     "flow_for_entrypoint",
+    "flow_segment",
     "fingerprint_documentation_wiki_input",
     "get_concept",
     "get_calibration_run_status",

{agent_wiki_cli-3.1.0 → agent_wiki_cli-3.3.0}/src/llm_wiki_cli/api_types.py

@@ -357,6 +357,19 @@ class DataFlowForEntrypointResult(_BoundedQueryResult):
     data_flow: dict[str, Any] | None
 
 
+class FlowSegmentResult(_BoundedQueryResult, total=False):
+    """Additive source-bound static segment; absent coverage means unavailable."""
+
+    segment_schema: str
+    owner: dict[str, Any] | None
+    basis: str | None
+    steps: list[dict[str, Any]]
+    coverage: dict[str, Any]
+    work: dict[str, Any]
+    follow_up: dict[str, Any]
+    limitations: list[str]
+
+
 class _StaticCallQueryOptions(TypedDict, total=False):
     """Additive captured-source coverage for static call queries."""
 
@@ -479,6 +492,12 @@ class DocumentationQueryResult(_DocumentationQueryRequired, total=False):
     coverage: dict[str, Any]
     flow: dict[str, Any] | None
     data_flow: dict[str, Any] | None
+    segment_schema: str
+    owner: dict[str, Any] | None
+    basis: str | None
+    steps: list[dict[str, Any]]
+    work: dict[str, Any]
+    follow_up: dict[str, Any]
     path: str | None
     inbound: list[str]
     outbound: list[str]
@@ -767,6 +786,7 @@ __all__ = [
     "EvidenceExplanationResult",
     "ExtractSourceResult",
     "FlowForEntrypointResult",
+    "FlowSegmentResult",
     "MarkdownContextResult",
     "KnowledgeMode",
     "KnowledgeCoverageCounts",

{agent_wiki_cli-3.1.0 → agent_wiki_cli-3.3.0}/src/llm_wiki_cli/cli.py

@@ -352,6 +352,7 @@ def _add_doctor_command(subparsers):
     doctor_contract = doctor_parser.add_mutually_exclusive_group()
     doctor_contract.add_argument("--capabilities", action="store_true", help="Opt into doctor v2 with provider prerequisites and corrective commands")
     doctor_contract.add_argument("--analysis-inputs", action="store_true", help="Check installed provider input classification without scanning project source")
+    doctor_contract.add_argument("--target-runtime", metavar="JSON", help="Compare committed wiki runtime prerequisites with project-owned target declarations, without scanning source or executing targets")
     doctor_parser.add_argument("--comparison-policy", choices=("auto", "exact-v1", "analysis-v1"), default="auto")
     doctor_contract.add_argument("--report-schema", choices=("auto", "v1", "v3", "v4"), default="auto", help="Health report schema; v3 includes captured coverage and producer details")
     doctor_parser.add_argument(