agent-wiki-cli 2.0.1__tar.gz → 2.0.2__tar.gz

{agent_wiki_cli-2.0.1/src/agent_wiki_cli.egg-info → agent_wiki_cli-2.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agent-wiki-cli
-Version: 2.0.1
+Version: 2.0.2
 Summary: CLI tool to maintain hybrid LLM Wikis for multi-language projects.
 Author-email: Denis Sivagin <denissvgn@gmail.com>
 License-Expression: MIT
@@ -745,6 +745,21 @@ generated from detected entry points with a call sequence, generated static
 generated data-flow section. Large generated call-sequence diagrams are capped
 to the first 30 interactions and include an omitted-interaction note so Mermaid
 output stays readable on large repositories.
+Sequence participants distinguish same-named functions in different modules
+and calls through different receivers. A delegated call such as
+`service.check_wiki()` stays distinct from a `check_wiki` wrapper; genuine
+self-calls retain their self-arrows.
+Calls on returned objects use compact labels such as `ReportBuilder(…).build`
+in both diagrams. Matching compact labels receive context or a number to keep
+their targets distinct. Full captured calls remain in the evidence tables;
+dashed arrows identify external or unresolved calls, including methods whose
+receiver type is unknown.
+Workflow pages require resolved body calls into at least three other project
+modules. Their sequences follow captured source order, without claiming runtime
+branching or evaluation order. Type annotations and docstrings do not create
+call steps. When an upgraded detector no longer recognizes a generated
+workflow, sync retires generated-only pages; it stops before removing a page
+with authored `Behavior` so you can archive that content explicitly.
 Dependency architecture pages are generated as `dependencies.md` and
 `load-order.md`; use `--skip-dependencies` for projects that do not want those
 pages or lint diagnostics. Generated `index.md` is a registry-backed landing
@@ -756,6 +771,10 @@ Passing `--openapi-file` implies `--api-contracts`; the supplied OpenAPI 3.0 or
 3.1 JSON/YAML document is authoritative for wire fields, while syntax-only
 source analysis contributes handler, module, entity, and flow links. The target
 application is never imported or executed.
+Dynamic route expressions remain visible as unknown API-contract evidence.
+Only concrete routes are attached to flow metadata, so unresolved paths do not
+prevent bootstrap or sync and are never replaced with invented URLs. Supply an
+OpenAPI export when authoritative concrete paths are needed.
 `--depth full` is the default and includes
 docstrings, imports, attributes, method signatures, generated relationship
 sections, bounded per-module dependency mini-map summaries, and diagram data
@@ -908,6 +927,11 @@ test files remain part of normal Python extraction.
 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`.
+Native knowledge records the selected producing extractor independently of this
+language label, including TypeScript-family plugins that emit JavaScript.
+After upgrading from artifacts with unknown JavaScript producer configuration,
+run `llm-wiki sync --rebuild-knowledge` to record a fresh basis, then check health
+with `llm-wiki doctor --strict`. Other health findings retain their usual meaning.
 Plain `.js` files include named top-level function declarations in the
 `functions` list even when they are local CommonJS helpers. Those functions are
 rendered on module pages; JavaScript function declarations do not create entity
@@ -954,6 +978,21 @@ keyword-only, and variadic-keyword declarations. Python model/type inventory
 also carries optional required/nullable/default/factory, alias, constraint,
 description/example, `Annotated`, validator/config, enum-member, literal, and
 type-alias metadata without importing Pydantic or application modules.
+Python call targets follow lexical bindings. Builtins remain file-less calls;
+local declarations, aliases, and imports resolve only when their targets are
+justified. Uncertain rebinding and closures remain unresolved instead of linking
+to unrelated same-named functions. Optional `call_bindings` entries parallel a
+callable's `calls` list, `python_bindings` describes module bindings, and
+`main_block_call_bindings` parallels guarded process-entry calls. Older
+inventories may omit these fields.
+TypedDict classes use `model_kind: "typeddict"`; their fields' `required` flags
+describe whether dictionary keys must be present. `total=False` applies to keys
+declared by that class, while inherited keys retain their original presence
+rules. Resolvable `Required`/`NotRequired` annotations override totality.
+An explicit `total` expression is retained in `class_keywords.total`; when its
+value cannot be determined statically, key presence is unknown unless overridden.
+Entity pages show a separate **Presence** column for TypedDict keys, independently
+of nullability and value defaults.
 The payload also gains an optional top-level
 `entrypoints` array (detected user-reachable entry points: `{id, category, file,
 symbol, label}`), a `data_flows` list for detected user flows, plus a top-level
@@ -1102,7 +1141,16 @@ 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.
 Python dependency reconciliation reads `pyproject.toml` and `requirements*.txt`
-manifests, including nested manifests scoped to their directory. TypeScript and
+manifests, including nested manifests scoped to their directory. Python imports
+use the selected source root, conventional `src` layouts, and declared packaging
+roots; a nested file's basename is not a repository-wide import alias.
+`python_import_scope` records source-relative project and search roots when
+packaging metadata is available. Literal setuptools `package-dir`/`find.where`
+and Poetry package `from` settings support custom layouts. Ambiguous candidates
+are disclosed without becoming unconditional dependency edges or import cycles.
+Legitimate local standard-library shadowing and explicit relative imports remain
+supported; runtime import-hook and `sys.path` changes are not executed.
+TypeScript and
 JavaScript reconciliation reads the nearest scoped `package.json` and resolves
 first-party imports through the nearest `tsconfig.json` `baseUrl`/`paths`
 aliases before reporting undeclared external packages. Generic internal import

{agent_wiki_cli-2.0.1 → agent_wiki_cli-2.0.2}/README.md

@@ -710,6 +710,21 @@ generated from detected entry points with a call sequence, generated static
 generated data-flow section. Large generated call-sequence diagrams are capped
 to the first 30 interactions and include an omitted-interaction note so Mermaid
 output stays readable on large repositories.
+Sequence participants distinguish same-named functions in different modules
+and calls through different receivers. A delegated call such as
+`service.check_wiki()` stays distinct from a `check_wiki` wrapper; genuine
+self-calls retain their self-arrows.
+Calls on returned objects use compact labels such as `ReportBuilder(…).build`
+in both diagrams. Matching compact labels receive context or a number to keep
+their targets distinct. Full captured calls remain in the evidence tables;
+dashed arrows identify external or unresolved calls, including methods whose
+receiver type is unknown.
+Workflow pages require resolved body calls into at least three other project
+modules. Their sequences follow captured source order, without claiming runtime
+branching or evaluation order. Type annotations and docstrings do not create
+call steps. When an upgraded detector no longer recognizes a generated
+workflow, sync retires generated-only pages; it stops before removing a page
+with authored `Behavior` so you can archive that content explicitly.
 Dependency architecture pages are generated as `dependencies.md` and
 `load-order.md`; use `--skip-dependencies` for projects that do not want those
 pages or lint diagnostics. Generated `index.md` is a registry-backed landing
@@ -721,6 +736,10 @@ Passing `--openapi-file` implies `--api-contracts`; the supplied OpenAPI 3.0 or
 3.1 JSON/YAML document is authoritative for wire fields, while syntax-only
 source analysis contributes handler, module, entity, and flow links. The target
 application is never imported or executed.
+Dynamic route expressions remain visible as unknown API-contract evidence.
+Only concrete routes are attached to flow metadata, so unresolved paths do not
+prevent bootstrap or sync and are never replaced with invented URLs. Supply an
+OpenAPI export when authoritative concrete paths are needed.
 `--depth full` is the default and includes
 docstrings, imports, attributes, method signatures, generated relationship
 sections, bounded per-module dependency mini-map summaries, and diagram data
@@ -873,6 +892,11 @@ test files remain part of normal Python extraction.
 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`.
+Native knowledge records the selected producing extractor independently of this
+language label, including TypeScript-family plugins that emit JavaScript.
+After upgrading from artifacts with unknown JavaScript producer configuration,
+run `llm-wiki sync --rebuild-knowledge` to record a fresh basis, then check health
+with `llm-wiki doctor --strict`. Other health findings retain their usual meaning.
 Plain `.js` files include named top-level function declarations in the
 `functions` list even when they are local CommonJS helpers. Those functions are
 rendered on module pages; JavaScript function declarations do not create entity
@@ -919,6 +943,21 @@ keyword-only, and variadic-keyword declarations. Python model/type inventory
 also carries optional required/nullable/default/factory, alias, constraint,
 description/example, `Annotated`, validator/config, enum-member, literal, and
 type-alias metadata without importing Pydantic or application modules.
+Python call targets follow lexical bindings. Builtins remain file-less calls;
+local declarations, aliases, and imports resolve only when their targets are
+justified. Uncertain rebinding and closures remain unresolved instead of linking
+to unrelated same-named functions. Optional `call_bindings` entries parallel a
+callable's `calls` list, `python_bindings` describes module bindings, and
+`main_block_call_bindings` parallels guarded process-entry calls. Older
+inventories may omit these fields.
+TypedDict classes use `model_kind: "typeddict"`; their fields' `required` flags
+describe whether dictionary keys must be present. `total=False` applies to keys
+declared by that class, while inherited keys retain their original presence
+rules. Resolvable `Required`/`NotRequired` annotations override totality.
+An explicit `total` expression is retained in `class_keywords.total`; when its
+value cannot be determined statically, key presence is unknown unless overridden.
+Entity pages show a separate **Presence** column for TypedDict keys, independently
+of nullability and value defaults.
 The payload also gains an optional top-level
 `entrypoints` array (detected user-reachable entry points: `{id, category, file,
 symbol, label}`), a `data_flows` list for detected user flows, plus a top-level
@@ -1067,7 +1106,16 @@ 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.
 Python dependency reconciliation reads `pyproject.toml` and `requirements*.txt`
-manifests, including nested manifests scoped to their directory. TypeScript and
+manifests, including nested manifests scoped to their directory. Python imports
+use the selected source root, conventional `src` layouts, and declared packaging
+roots; a nested file's basename is not a repository-wide import alias.
+`python_import_scope` records source-relative project and search roots when
+packaging metadata is available. Literal setuptools `package-dir`/`find.where`
+and Poetry package `from` settings support custom layouts. Ambiguous candidates
+are disclosed without becoming unconditional dependency edges or import cycles.
+Legitimate local standard-library shadowing and explicit relative imports remain
+supported; runtime import-hook and `sys.path` changes are not executed.
+TypeScript and
 JavaScript reconciliation reads the nearest scoped `package.json` and resolves
 first-party imports through the nearest `tsconfig.json` `baseUrl`/`paths`
 aliases before reporting undeclared external packages. Generic internal import

{agent_wiki_cli-2.0.1 → agent_wiki_cli-2.0.2}/pyproject.toml

@@ -5,7 +5,7 @@ backend-path = ["."]
 
 [project]
 name = "agent-wiki-cli"
-version = "2.0.1"
+version = "2.0.2"
 description = "CLI tool to maintain hybrid LLM Wikis for multi-language projects."
 readme = "README.md"
 license = "MIT"

{agent_wiki_cli-2.0.1 → agent_wiki_cli-2.0.2/src/agent_wiki_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agent-wiki-cli
-Version: 2.0.1
+Version: 2.0.2
 Summary: CLI tool to maintain hybrid LLM Wikis for multi-language projects.
 Author-email: Denis Sivagin <denissvgn@gmail.com>
 License-Expression: MIT
@@ -745,6 +745,21 @@ generated from detected entry points with a call sequence, generated static
 generated data-flow section. Large generated call-sequence diagrams are capped
 to the first 30 interactions and include an omitted-interaction note so Mermaid
 output stays readable on large repositories.
+Sequence participants distinguish same-named functions in different modules
+and calls through different receivers. A delegated call such as
+`service.check_wiki()` stays distinct from a `check_wiki` wrapper; genuine
+self-calls retain their self-arrows.
+Calls on returned objects use compact labels such as `ReportBuilder(…).build`
+in both diagrams. Matching compact labels receive context or a number to keep
+their targets distinct. Full captured calls remain in the evidence tables;
+dashed arrows identify external or unresolved calls, including methods whose
+receiver type is unknown.
+Workflow pages require resolved body calls into at least three other project
+modules. Their sequences follow captured source order, without claiming runtime
+branching or evaluation order. Type annotations and docstrings do not create
+call steps. When an upgraded detector no longer recognizes a generated
+workflow, sync retires generated-only pages; it stops before removing a page
+with authored `Behavior` so you can archive that content explicitly.
 Dependency architecture pages are generated as `dependencies.md` and
 `load-order.md`; use `--skip-dependencies` for projects that do not want those
 pages or lint diagnostics. Generated `index.md` is a registry-backed landing
@@ -756,6 +771,10 @@ Passing `--openapi-file` implies `--api-contracts`; the supplied OpenAPI 3.0 or
 3.1 JSON/YAML document is authoritative for wire fields, while syntax-only
 source analysis contributes handler, module, entity, and flow links. The target
 application is never imported or executed.
+Dynamic route expressions remain visible as unknown API-contract evidence.
+Only concrete routes are attached to flow metadata, so unresolved paths do not
+prevent bootstrap or sync and are never replaced with invented URLs. Supply an
+OpenAPI export when authoritative concrete paths are needed.
 `--depth full` is the default and includes
 docstrings, imports, attributes, method signatures, generated relationship
 sections, bounded per-module dependency mini-map summaries, and diagram data
@@ -908,6 +927,11 @@ test files remain part of normal Python extraction.
 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`.
+Native knowledge records the selected producing extractor independently of this
+language label, including TypeScript-family plugins that emit JavaScript.
+After upgrading from artifacts with unknown JavaScript producer configuration,
+run `llm-wiki sync --rebuild-knowledge` to record a fresh basis, then check health
+with `llm-wiki doctor --strict`. Other health findings retain their usual meaning.
 Plain `.js` files include named top-level function declarations in the
 `functions` list even when they are local CommonJS helpers. Those functions are
 rendered on module pages; JavaScript function declarations do not create entity
@@ -954,6 +978,21 @@ keyword-only, and variadic-keyword declarations. Python model/type inventory
 also carries optional required/nullable/default/factory, alias, constraint,
 description/example, `Annotated`, validator/config, enum-member, literal, and
 type-alias metadata without importing Pydantic or application modules.
+Python call targets follow lexical bindings. Builtins remain file-less calls;
+local declarations, aliases, and imports resolve only when their targets are
+justified. Uncertain rebinding and closures remain unresolved instead of linking
+to unrelated same-named functions. Optional `call_bindings` entries parallel a
+callable's `calls` list, `python_bindings` describes module bindings, and
+`main_block_call_bindings` parallels guarded process-entry calls. Older
+inventories may omit these fields.
+TypedDict classes use `model_kind: "typeddict"`; their fields' `required` flags
+describe whether dictionary keys must be present. `total=False` applies to keys
+declared by that class, while inherited keys retain their original presence
+rules. Resolvable `Required`/`NotRequired` annotations override totality.
+An explicit `total` expression is retained in `class_keywords.total`; when its
+value cannot be determined statically, key presence is unknown unless overridden.
+Entity pages show a separate **Presence** column for TypedDict keys, independently
+of nullability and value defaults.
 The payload also gains an optional top-level
 `entrypoints` array (detected user-reachable entry points: `{id, category, file,
 symbol, label}`), a `data_flows` list for detected user flows, plus a top-level
@@ -1102,7 +1141,16 @@ 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.
 Python dependency reconciliation reads `pyproject.toml` and `requirements*.txt`
-manifests, including nested manifests scoped to their directory. TypeScript and
+manifests, including nested manifests scoped to their directory. Python imports
+use the selected source root, conventional `src` layouts, and declared packaging
+roots; a nested file's basename is not a repository-wide import alias.
+`python_import_scope` records source-relative project and search roots when
+packaging metadata is available. Literal setuptools `package-dir`/`find.where`
+and Poetry package `from` settings support custom layouts. Ambiguous candidates
+are disclosed without becoming unconditional dependency edges or import cycles.
+Legitimate local standard-library shadowing and explicit relative imports remain
+supported; runtime import-hook and `sys.path` changes are not executed.
+TypeScript and
 JavaScript reconciliation reads the nearest scoped `package.json` and resolves
 first-party imports through the nearest `tsconfig.json` `baseUrl`/`paths`
 aliases before reporting undeclared external packages. Generic internal import

{agent_wiki_cli-2.0.1 → agent_wiki_cli-2.0.2}/src/agent_wiki_cli.egg-info/SOURCES.txt

@@ -59,6 +59,7 @@ src/llm_wiki_cli/extractors/common.py
 src/llm_wiki_cli/extractors/fastapi_contracts.py
 src/llm_wiki_cli/extractors/go_extractor.py
 src/llm_wiki_cli/extractors/haskell_extractor.py
+src/llm_wiki_cli/extractors/python_bindings.py
 src/llm_wiki_cli/extractors/python_contracts.py
 src/llm_wiki_cli/extractors/python_extractor.py
 src/llm_wiki_cli/extractors/rust_extractor.py
@@ -152,7 +153,10 @@ src/llm_wiki_cli/services/plugin_samples.py
 src/llm_wiki_cli/services/plugins.py
 src/llm_wiki_cli/services/progress.py
 src/llm_wiki_cli/services/protected_artifacts.py
+src/llm_wiki_cli/services/python_calls.py
+src/llm_wiki_cli/services/python_imports.py
 src/llm_wiki_cli/services/python_observations.py
+src/llm_wiki_cli/services/python_stdlib.py
 src/llm_wiki_cli/services/redaction.py
 src/llm_wiki_cli/services/relationships.py
 src/llm_wiki_cli/services/rendering_lifecycle.py
@@ -345,6 +349,7 @@ tests/test_knowledge_loader.py
 tests/test_knowledge_model.py
 tests/test_knowledge_observability.py
 tests/test_knowledge_performance.py
+tests/test_knowledge_producer_languages.py
 tests/test_knowledge_projection.py
 tests/test_knowledge_projection_e2e.py
 tests/test_knowledge_queries.py
@@ -381,7 +386,10 @@ tests/test_protocol_registry.py
 tests/test_provisioning_failures.py
 tests/test_public_docs_vocabulary.py
 tests/test_publishing_hub_attack_contracts.py
+tests/test_python_call_bindings.py
+tests/test_python_import_scopes.py
 tests/test_python_observation_cache.py
+tests/test_python_typed_dicts.py
 tests/test_quality_workflows.py
 tests/test_redaction.py
 tests/test_reference_skill_verifier.py
@@ -394,6 +402,7 @@ tests/test_release_supply_chain.py
 tests/test_release_workflows.py
 tests/test_rendering_lifecycle.py
 tests/test_resource_diagnostics.py
+tests/test_route_projection_regressions.py
 tests/test_runtime_output.py
 tests/test_rust_extract.py
 tests/test_schema.py
@@ -427,6 +436,7 @@ tests/test_upgrade.py
 tests/test_validated_knowledge_reuse.py
 tests/test_validation.py
 tests/test_verification_contracts.py
+tests/test_verified_bug_migrations.py
 tests/test_versioning.py
 tests/test_wiki_git_policy.py
 tests/test_wiki_helper_cache.py

{agent_wiki_cli-2.0.1 → agent_wiki_cli-2.0.2}/src/llm_wiki_cli/commands/migrate_cmd.py

@@ -80,6 +80,7 @@ from ..services.bootstrap_runtime import (
 )
 from ..services.extraction_service import (
     InventoryResult,
+    _workflow_name,
     get_call_graph,
     get_docker_inventory,
     get_inventory_result,
@@ -506,13 +507,13 @@ def _build_workflow_link_maps(
         return {}
 
     page_maps: dict[str, dict[str, str]] = {}
-    for wf_name, wf_data in get_call_graph(inventory).items():
+    for wf_name, source_paths in _workflow_link_sources(inventory, module_page_map).items():
         wf_path = workflow_dir / f"{wf_name}.md"
         if not wf_path.exists():
             continue
 
         stem_targets: dict[str, set[str]] = {}
-        for source_path in wf_data.get("modules_touched_paths", []):
+        for source_path in source_paths:
             page_stem = module_page_map.get(source_path)
             if not page_stem:
                 continue
@@ -531,6 +532,46 @@ def _build_workflow_link_maps(
     return page_maps
 
 
+def _workflow_link_sources(
+    inventory: dict, module_page_map: dict[str, str]
+) -> dict[str, set[str]]:
+    """Keep legacy type-reference link repair separate from workflow detection.
+
+    Older pages may have been generated from annotations without any body
+    calls. Those references still help repair links on existing pages; they
+    must not create new workflows or be rendered as an execution sequence.
+    """
+    workflows = get_call_graph(inventory)
+    paths = {
+        name: set(workflow.get("modules_touched_paths", []))
+        for name, workflow in workflows.items()
+    }
+    candidates: dict[str, dict[str, set[str]]] = {}
+    definitions: dict[str, set[str]] = {}
+    for source, data in inventory.items():
+        for function in data.get("functions", []):
+            name = _workflow_name(function["name"], Path(source).stem)
+            definitions.setdefault(name, set()).add(source)
+    for (_, target), references in _build_relationships(inventory, module_page_map).items():
+        for reference in references:
+            function = reference.get("function")
+            if not function:
+                continue
+            source = reference["module_path"]
+            name = _workflow_name(function, reference["module"])
+            entries = candidates.setdefault(name, {})
+            entries.setdefault(source, {source}).add(target)
+    for name, entries in candidates.items():
+        if name in workflows:
+            source = workflows[name].get("entry_module_path")
+            paths[name].update(entries.get(source, set()))
+        elif len(entries) == 1 and len(definitions.get(name, set())) == 1:
+            # A same-named callable in another module is not sufficient proof
+            # to rewrite an ambiguous legacy link.
+            paths[name] = next(iter(entries.values()))
+    return paths
+
+
 def _unique(values: list[TargetPage]) -> TargetPage | None:
     return values[0] if len(values) == 1 else None