agent-wiki-cli 2.4.0__tar.gz → 2.5.0__tar.gz

{agent_wiki_cli-2.4.0/src/agent_wiki_cli.egg-info → agent_wiki_cli-2.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agent-wiki-cli
-Version: 2.4.0
+Version: 2.5.0
 Summary: CLI tool to maintain hybrid LLM Wikis for multi-language projects.
 Author-email: Denis Sivagin <denissvgn@gmail.com>
 License-Expression: MIT
@@ -127,8 +127,8 @@ for [Obsidian](docs/cli-reference.md#obsidian) or a
 | Go | `go/ast` | prepared helper binary |
 | Rust | `syn` | prepared helper binary |
 | Haskell | GHC parser, syntax-only inventory | prepared helper binary |
-| Docker / Compose | built-in parsers | none |
-| Runtime/config YAML | targeted built-in parsers | none |
+| Docker / Compose | Dockerfile parser / bounded YAML parser | included with the package |
+| Infrastructure / runtime YAML | structured format summaries | included with the package |
 | OpenAPI 3.0/3.1 JSON / YAML | `json` / PyYAML safe loader | included with the package |
 
 Discovery honors `.gitignore`. Use a
@@ -143,7 +143,9 @@ initialization. Every agent can use explicit sync, lint, and reviewed prompts;
 LLM Wiki does not install Git hooks.
 
 [Agent setup](docs/wiki-guide.md#agent-support) explains instruction files and
-skill export. The [MCP server](docs/cli-reference.md#mcp) provides read-only wiki
+skill export. [Workflow installation and upgrades](docs/native-agent-workflow.md#install-the-workflow-in-another-project)
+cover setup in another project, all agent targets, and the `--no-skills` inline fallback.
+The [MCP server](docs/cli-reference.md#mcp) provides read-only wiki
 access, and [bundled skills](docs/cli-reference.md#skills) guide documentation
 and analysis workflows.
 

{agent_wiki_cli-2.4.0 → agent_wiki_cli-2.5.0}/README.md

@@ -90,8 +90,8 @@ for [Obsidian](docs/cli-reference.md#obsidian) or a
 | Go | `go/ast` | prepared helper binary |
 | Rust | `syn` | prepared helper binary |
 | Haskell | GHC parser, syntax-only inventory | prepared helper binary |
-| Docker / Compose | built-in parsers | none |
-| Runtime/config YAML | targeted built-in parsers | none |
+| Docker / Compose | Dockerfile parser / bounded YAML parser | included with the package |
+| Infrastructure / runtime YAML | structured format summaries | included with the package |
 | OpenAPI 3.0/3.1 JSON / YAML | `json` / PyYAML safe loader | included with the package |
 
 Discovery honors `.gitignore`. Use a
@@ -106,7 +106,9 @@ initialization. Every agent can use explicit sync, lint, and reviewed prompts;
 LLM Wiki does not install Git hooks.
 
 [Agent setup](docs/wiki-guide.md#agent-support) explains instruction files and
-skill export. The [MCP server](docs/cli-reference.md#mcp) provides read-only wiki
+skill export. [Workflow installation and upgrades](docs/native-agent-workflow.md#install-the-workflow-in-another-project)
+cover setup in another project, all agent targets, and the `--no-skills` inline fallback.
+The [MCP server](docs/cli-reference.md#mcp) provides read-only wiki
 access, and [bundled skills](docs/cli-reference.md#skills) guide documentation
 and analysis workflows.
 

{agent_wiki_cli-2.4.0 → agent_wiki_cli-2.5.0}/docs/cli-reference.md

@@ -126,9 +126,13 @@ dependency architecture, and manifest files. User-flow pages under `flows/` are
 generated from detected entry points with a call sequence, generated static
 `## Data flow` section, boundary-effects table, and editable `## Behavior`; use
 `--skip-flows` to omit them or `--skip-data-flow` to keep flow pages without the
-generated data-flow section. Large generated call-sequence diagrams are capped
-to the first 30 interactions and include an omitted-interaction note so Mermaid
+generated data-flow section. Large generated call-sequence diagrams select up to
+30 representative captured interactions and include an omitted-interaction note so Mermaid
 output stays readable on large repositories.
+Selection favors resolved internal continuations and distinct target coordinates,
+with captured boundary examples. Repeated sites remain in the underlying trace;
+the diagram reports display omissions separately from traversal limits and is
+not runtime execution order.
 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
@@ -222,6 +226,26 @@ and lifecycle changes invalidate reuse. Governed or plugin-driven generation
 uses the full path. `--rebuild-knowledge` explicitly runs the full knowledge
 builder; `--no-cache` controls source extraction independently.
 
+Eligible ordinary syncs also retain `llm-wiki-sync-analysis.json` beside the
+inventory cache. Its exact content is bound to the last complete knowledge
+commit. When source bytes, selection, generation settings, schema, implementation,
+and prepared helper identities match, a later Markdown edit can reuse static
+inventory, page maps and source graph observations. The source-derived typed
+graph is reused only when its inventory, producer, options and concept
+coordinates still match. Markdown sections, links, assets and final commitments
+are evaluated again; page ownership and required writes retain their ordinary
+checks.
+
+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
+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.
+
 `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
@@ -1019,6 +1043,21 @@ selection, tokenizer and output paths distinct. `--view-budget-tokens` chooses
 its separate presentation budget; no fixed token saving or small-budget fit is
 promised. Include the selected view once in the coding host.
 
+Use `--view compact-v2` for readable JSON containing complete selected facts,
+citations, requirements, coverage, gaps and limitations. It requires the same
+explicit view budget and canonical receipt destination. Python and session
+calls select it with `schema_version: "llm-wiki-task-view-request/v2"` in
+`view_options`. Validation and expansion require the original canonical text,
+request and view options. The body is self-contained and may be larger than
+compact-v1's encoded body. Canonical delivery remains the default.
+
+MCP `read_compact_context_session` with these v2 options retains identity,
+conditional base, state, validation scope and limitations in its smaller default
+envelope. Set `include_metadata: true` for full work/reuse telemetry; v1 retains
+its full envelope. Python session replies retain full metadata. Count host
+framing, setup and any required receipt/metadata follow-ups in addition to the
+view budget; no complete-host token cap is implied by `--view-budget-tokens`.
+
 Choose `knowledge_mode: "off"` only when no native evidence is required; this
 route works without a wiki. Native v2 requirements need explicitly adopted
 sharded or packed knowledge. Keep `required` mode and the native requirements
@@ -1037,6 +1076,29 @@ See [workflow recipes and limits](native-agent-workflow.md).
 
 ## Codebase source integration
 
+`llm-wiki doctor --analysis-inputs --format json` checks the installed provider's
+Python/helper classification and registered implementation files without
+scanning application source, executing code or preparing helpers. Python callers
+use `api.get_analysis_input_status(limit=20)`. The report lists bounded relative
+paths, reason, omitted counts and the registry-review route; exit 0 means the
+census/files are ready and exit 2 means unavailable. This mode is exclusive with
+`--capabilities` and explicit `--report-schema` selection. It does not establish
+runtime/helper readiness, semantic correctness or producer authority.
+
+The default and `--format text` show a readable summary with the same status,
+path and omission counts, corrective route and qualifications. Use `--format
+json` for the structured report and its schema; output format does not change
+the readiness exit policy or read scope.
+
+Provider source additions require deliberate review of
+`services/analysis_contracts.json`: classify presentation/consumer files in the
+census and observation changes in their correct producer input lists. Missing
+or unclassified inputs retain unavailable analysis. Inventory results expose
+`analysis_input_status`; affected canonical task v2 results include it in `work`
+and sync-cache misses emit the bounded diagnostic. Compact callers can inspect
+the host-owned canonical receipt. Healthy task output retains its existing
+shape; diagnostics provide information without changing source/review claims.
+
 For research or indexing systems that need codebase evidence without adopting
 the maintained wiki format, prefer the read-only source-adapter commands:
 
@@ -1919,6 +1981,15 @@ of UTF-8 content, with 1–100 returned results. Exceeding a corpus limit fails
 explicitly; narrow `--kind` or choose a smaller wiki. Search is read-only and
 does not require embeddings or a model service.
 
+Lexical-v2 uses approximate English word families for discovery while preserving
+literal page and symbol identity checks. Strong matches in diagnostic guide
+sections can also surface explicitly linked module/entity pages already in the
+captured corpus. These one-hop leads report `linked_evidence` with the guide's
+hash, section locator and target path. A link-derived candidate without its own
+text match has no fabricated matched-section location; its provenance identifies
+linked discovery. Links do not trigger network reads, source indexing or recursive
+traversal. Inspect exact source before treating any candidate as an explanation.
+
 The query must contain a non-whitespace character. Nonblank queries retain
 their original whitespace, including in substring mode. `--limit` accepts a
 positive integer, defaults to 20, and caps the returned results at 100 even when
@@ -1989,6 +2060,14 @@ Inspect the affected source and semantic prose; use explicit
 [ordinary review tracking](maintenance.md) when durable review is needed.
 An empty queue does not establish ordinary-review completion.
 
+On a coherent unadopted native wiki, captured source-backed semantic sections
+appear as informational coverage gaps, including after sync makes structural
+freshness current. Each item's `coverage_gaps` identifies the exact untracked
+section; `coverage_gap_bounds` reports omitted details. These candidates need
+source/prose inspection and remain untracked even after a prose correction.
+Durable pending and acknowledgment history require explicit ordinary-review
+adoption.
+
 ## `maintenance`
 
 Ordinary review tracking is optional and independent of human governance and

{agent_wiki_cli-2.4.0 → agent_wiki_cli-2.5.0}/docs/native-agent-workflow.md

@@ -1,5 +1,19 @@
 # Native coding workflow
 
+Initialized projects receive a default development procedure through their
+managed agent instructions: define acceptance criteria, gather scoped evidence,
+inspect source, make bounded changes, verify independently, refresh affected
+knowledge, and preserve a qualified handoff. The managed
+`wiki-reference/references/development-workflow.md` topic owns that procedure;
+expanded instructions retain it when skills are disabled or unavailable.
+Package installation ships the reference; `llm-wiki init` establishes the
+project instructions, and `llm-wiki upgrade` refreshes them after a package update.
+
+The native interfaces below are explicit choices within that procedure.
+Initializing a project does not activate a workflow profile, session, storage
+adoption, or Git action. Small mechanical work can use proportionate inspection
+and checks while retaining applicable maintenance obligations.
+
 Use a provider whose CLI and Python API expose the task request, storage and
 optional delivery interfaces you select. Check `llm-wiki task-context --help`
 and `llm-wiki knowledge migrate --help` in each environment; a version number
@@ -17,6 +31,115 @@ An explicit task request gathers qualified source and wiki evidence. The provide
 reads and reports; your coding host decides what to include, edit, execute and
 publish. Existing context calls retain their defaults.
 
+## Install the workflow in another project
+
+Run the following commands from the target project's root, using its own
+Python 3.10+ virtual environment at `.venv/`. Package installation supplies the
+CLI and bundled workflow; initialization writes the project-specific agent
+instructions and wiki scaffold.
+
+For a released package that includes the default development workflow:
+
+```bash
+.venv/bin/pip install agent-wiki-cli
+.venv/bin/llm-wiki init --agent generic
+```
+
+To use a source checkout, including changes that have not been published,
+install that checkout instead. Replace the quoted path with its absolute
+location; keep running commands from the target project:
+
+```bash
+.venv/bin/pip install "/absolute/path/python-wiki-llm"
+.venv/bin/llm-wiki init --agent generic
+```
+
+Choose the agent's instruction format with `--agent`:
+
+| Agent target | Project instruction file | Managed reference directory |
+|---|---|---|
+| `generic` | `AGENTS.md` | `.llm-wiki/skills/wiki-reference/` |
+| `claude` | `CLAUDE.md` | `.claude/skills/wiki-reference/` |
+| `cursor` | `.cursorrules` | `.llm-wiki/skills/wiki-reference/` |
+| `copilot` | `.github/copilot-instructions.md` | `.llm-wiki/skills/wiki-reference/` |
+| `aider` | `.aider.conf.yml` | `.llm-wiki/skills/wiki-reference/` |
+| `opencode` | `.opencode/instructions.md` | `.llm-wiki/skills/wiki-reference/` |
+
+Use `generic` for Codex or another agent that reads `AGENTS.md`. Initialization
+preserves existing user instructions outside the managed block and installs
+`references/development-workflow.md` within the managed reference directory.
+Start a new agent session, or reload its project instructions, so it reads the
+workflow. The default procedure is available without separately installing the
+optional `native-coding` skill.
+
+The default wiki scaffold is `docs/llm_wiki/`. To choose another location, pass
+`--wiki-dir .wiki` to initialization and keep that same path in subsequent
+commands. Initialization creates the scaffold; bootstrap populates the wiki
+from the project's sources:
+
+```bash
+.venv/bin/llm-wiki bootstrap --src-dir . --wiki-dir docs/llm_wiki
+```
+
+Use the actual source root and configured source selection. For languages that
+need extractor helpers, install the relevant toolchain and explicitly prepare
+the helpers with `init --prepare-extractors` or
+`llm-wiki prepare-extractors --src-dir .`; see
+[helper setup](cli-reference.md#prepare-extractors). Source-only task evidence
+can be used before bootstrap, following the [source-only route](#source-only-task-without-a-wiki).
+
+### Use the inline fallback
+
+For an agent or project that needs instructions in a single file, skip the
+managed reference installation:
+
+```bash
+.venv/bin/llm-wiki init --agent generic --no-skills
+```
+
+This writes expanded, self-contained instructions, including the development
+procedure, into the selected agent instruction file. It records the preference
+for later initialization and upgrades. An existing reference directory is
+preserved, and read-only context interfaces remain available. Initialization
+and upgrade also use expanded instructions when the managed reference is
+unavailable or cannot be verified current.
+
+### Upgrade an initialized project
+
+Update the package in the target project's environment, then refresh its
+managed instructions from that project's root:
+
+```bash
+.venv/bin/pip install --upgrade agent-wiki-cli
+.venv/bin/llm-wiki upgrade
+```
+
+For a source checkout, replace the package update command with
+`.venv/bin/pip install --upgrade "/absolute/path/python-wiki-llm"`. Package
+updates alone do not refresh project instructions. For a custom wiki location,
+use `.venv/bin/llm-wiki upgrade --wiki-dir .wiki`.
+
+Upgrade retains the configured agent, source-selection preference and skills
+preference unless explicitly overridden. It refreshes the managed instruction
+block, reference topics and missing scaffold structure while preserving user
+instructions outside the managed block and existing wiki prose. When references
+are enabled, expected managed topic files are replaced even if edited locally;
+keep project-specific rules outside that tree or back up edits before upgrading.
+Conflicting or unsafe entries are preserved and reported. See the
+[managed skills lifecycle](cli-reference.md#skills) for recovery details.
+
+To change the instruction format, use `upgrade --agent claude` or another
+supported target. To change the skills preference explicitly:
+
+```bash
+.venv/bin/llm-wiki upgrade --no-skills
+.venv/bin/llm-wiki upgrade --skills
+```
+
+The first command selects inline instructions; the second restores managed
+references and compact routing when verification succeeds. Choose the command
+for your desired mode, then reload the agent's project instructions.
+
 ## Choose an interface
 
 | Operation | Python API | CLI | MCP |

{agent_wiki_cli-2.4.0 → agent_wiki_cli-2.5.0}/docs/native-knowledge-provider.md

@@ -40,6 +40,68 @@ ready native knowledge, not a positive live-currentness verdict. A successful
 unavailable/fallback response is different from a ready model with no matching
 concept. Check availability before interpreting `found=False`.
 
+### Supplied path outcomes
+
+Impact requests support an explicit discovery policy:
+
+```python
+result = api.query_documentation({
+    "operation": "impact",
+    "paths": ["src/main.mjs", "src/helper.cjs"],
+    "source_policy": "discovery",
+    "limit": 8,
+})
+```
+
+This policy honors source selection, ignore rules, excluded directories,
+generated bundles, bundled helpers, and agent worktrees. Omit `source_policy`
+or select `explicit` to retain historical exact-path extraction behavior,
+including its ignore and bundle overrides. Source-selection boundaries apply
+to both policies.
+
+With `discovery`, each returned match separates these observations:
+
+| Field | Meaning |
+|---|---|
+| `present` | An extracted inventory entry exists; this is not filesystem existence. |
+| `filesystem_state` | `file`, `missing`, `not-file`, or `unknown`. Profile-excluded paths remain unknown without a metadata read. |
+| `selection_state` | `included` or `excluded` under the captured discovery policy. |
+| `extraction_state` | `extracted`, `unsupported`, `failed`, `unavailable`, `no-documentable-content`, or `not-attempted`. |
+| `reason` | A machine-readable explanation, including `gitignore`, `generated-bundle`, `source-selection`, `unsupported-extension`, `syntax-error`, or `helper-unavailable`. |
+| `failure_scope` | When available, `file` or `extractor-batch`; a batch failure does not prove each file has a syntax error. |
+
+Diagnostic reads can retain successful sources alongside attributable extraction
+failures. Missing helpers remain unavailable, and legacy helper output without
+file outcomes remains qualified rather than being treated as proof of failure.
+Invalid paths, inconsistent protected wiki state, and source/wiki/control-file
+mutation still abort the read. Normal extraction and legacy impact requests
+retain their operational error behavior.
+
+The built-in Python extractor reports parser failures as `failed` with
+`reason: "syntax-error"` and `failure_scope: "file"`. A parsed module with no
+documentable content reports `no-documentable-content`; both can have
+`present: false` while the file exists. Extractors without attributable outcomes
+retain `unavailable` with `reason: "outcome-not-reported"`.
+
+Go `_test.go` files are excluded by the default language inclusion policy.
+Discovery reports `selection_state: "excluded"`,
+`extraction_state: "not-attempted"`, and `reason: "go-tests-excluded"`, keeping
+the filesystem observation separate. Their extension is supported. Source
+snapshot and extraction interfaces that accept `include_tests=["go"]` can
+include them; impact requests do not accept an `include_tests` option.
+
+JavaScript `.js`, `.jsx`, `.mjs`, and `.cjs` share source discovery and hashing.
+Static ESM imports, including side-effect imports, and direct unshadowed
+`require("literal")` calls supply dependency observations. Function-scoped
+require calls retain deferred scope. Shadowed and indirect require calls have
+coverage gaps; computed specifiers and dynamic imports stay unresolved.
+An explicit relative suffix selects only that exact source identity. An
+ambiguous extensionless import does not create multiple guessed edges.
+
+Supply both source paths when a targeted read needs both sides of a dependency.
+These diagnostics do not expand into a full inventory or establish global
+wiki freshness. Existing response limits and truncation disclosures apply.
+
 ```python
 from llm_wiki_cli import api
 

{agent_wiki_cli-2.4.0 → agent_wiki_cli-2.5.0}/docs/wiki-guide.md

@@ -28,13 +28,44 @@ canonical wiki surface registry:
 | `workflows/` | mixed | Detected or manually maintained cross-module flow pages. |
 | `guides/` | semantic | Agent-authored navigation, operator, and contributor guides. |
 | `flows/` | mixed | User-flow pages, one per detected entry point, with bounded generated Mermaid call and data-flow diagrams. |
-| `infrastructure/` | mixed | Dockerfile, Compose, GitHub Actions, Kubernetes, and targeted runtime/config YAML pages. |
+| `infrastructure/` | mixed | Dockerfile, Compose, CI, Kubernetes, deployment and targeted runtime/config YAML pages. |
 | `api-contracts.md` | mixed | Optional production HTTP contract inventory generated from static FastAPI declarations or an exported OpenAPI document; `## Notes` is semantic. |
 | `dependencies.md` | mixed | Optional internal and external dependency architecture page. |
 | `load-order.md` | mixed | Optional load-order, cycle, and startup-caveat architecture page. |
 
 ### Generated state and content ownership
 
+When a declaration disappears from a source module that remains in the selected
+inventory, ordinary sync retains its entity page as source history. The index
+lists it under **Retired source members**, and native reads carry the explicit
+`llm-wiki/source-retirement` qualification. Historical evidence stays historical;
+unknown provenance stays unknown. This source observation does not author a
+concept lifecycle change or a human review.
+
+Retained manifest ownership lets ordinary sync recover a previously unqualified
+removed-member page. Reappearance at the exact same source coordinate can revive
+its page and authored context; an unrelated owner cannot claim the occupied path.
+Ambiguous duplicate removal requires resolved ownership before page writes.
+Previously documented sources with no documentable inventory receive a narrow
+parser qualification: a valid empty module retains its module page and source
+commitment while its removed members become history. Python aliases, parse
+failures and unavailable coverage stop that transition. A stale Markdown header
+alone does not establish retirement authority.
+
+Retained empty modules remain explicit in the owning manifest. Lint and live
+native reads request those exact parser records, preserving the distinction
+between an empty module and a missing source. Analysis caches retain attributable
+outcomes; missing qualifications are rebuilt through the same scoped parser
+route. This does not add every otherwise-undocumented empty file to the wiki.
+
+Discovery-policy impact queries report Go, Rust and Haskell parse and read
+failures at the selected file boundary. Successful parsed records remain
+available alongside failed files; missing helpers, invalid helper responses,
+and process failures retain their separate coverage or batch qualifications.
+An omitted outcome remains unavailable and cannot establish an empty module or
+authorize source-member retirement. Ordinary extraction keeps its inventory
+format; these diagnostics are an opt-in analysis contract.
+
 The wiki also contains `.llm-wiki-manifest.json`, the operational source,
 evidence, and artifact-commit state used by incremental sync and strict
 linting; `.llm-wiki-surface.json`, the deterministic machine-readable index of
@@ -126,7 +157,7 @@ The [native knowledge tutorial](../examples/native-knowledge/README.md) shows
 a library consumer using shared inspection, coverage and qualified packets.
 
 The package has a small required Python runtime footprint. `PyYAML>=6` parses
-user-supplied OpenAPI YAML, and Python versions older than 3.11 use `tomli` for
+OpenAPI and infrastructure YAML, and Python versions older than 3.11 use `tomli` for
 TOML. FastAPI, Pydantic, and the target application are not runtime
 dependencies and are never imported for contract extraction. Optional language
 features use external tools when they are available on `PATH`.
@@ -140,11 +171,42 @@ features use external tools when they are available on `PATH`.
 | Go | bundled Go extractor using `go/ast` | prepared helper binary |
 | Rust | bundled Rust extractor using `syn` | prepared helper binary |
 | Haskell | bundled GHC parser helper for syntax-only inventory | prepared helper binary |
-| Docker / Compose | built-in parsers | none |
-| Runtime/config YAML | targeted built-in parsers | none |
+| Docker / Compose | Dockerfile parser / bounded YAML parser | included with the package |
+| Infrastructure / runtime YAML | structured format summaries | included with the package |
 | OpenAPI 3.0/3.1 JSON / YAML | stdlib `json` / PyYAML safe loader | `PyYAML>=6` (installed with the package) |
 | MCP server | official Python MCP SDK | `agent-wiki-cli[mcp]`, Python 3.10+ |
 
+### YAML inputs
+
+Infrastructure discovery recognizes GitHub Actions workflows and action metadata
+(composite, JavaScript and Docker actions), GitLab CI, CircleCI, Azure Pipelines,
+Kubernetes manifests, Kustomize configurations, Helm `Chart.yaml` metadata and
+Ansible playbooks. Runtime summaries cover Prometheus configuration and rules,
+Grafana provisioning, Promtail, Loki, Envoy, Buf and service-local model settings.
+Kubernetes resources can live outside `k8s/`; multi-document streams and `List`
+resources are summarized, including CronJob container settings.
+
+Named format detection requires a matching path and recognizable structure:
+
+| Format | Discovery path |
+|---|---|
+| Action metadata | `action.yml` or `action.yaml` |
+| GitLab CI | `.gitlab-ci.yml`/`.yaml` or YAML below `.gitlab/ci/` |
+| CircleCI | `.circleci/config.yml` or `.circleci/config.yaml` |
+| Azure Pipelines | `azure-pipelines*.yml` or `azure-pipelines*.yaml` |
+| Kustomize | `kustomization.yml`, `kustomization.yaml` or `Kustomization` |
+| Helm chart metadata | `Chart.yaml` or `Chart.yml` |
+| Ansible playbooks | `playbook.yml`/`.yaml`, `site.yml`/`.yaml` or YAML below `playbooks/` |
+
+Compose and infrastructure YAML accept block and flow collections, quoted keys,
+comments, alternate indentation, multiline scalars, anchors, aliases and merge
+keys. Scalar text is preserved, including GitHub's `on` key. Parsing is bounded;
+malformed YAML, duplicate keys, recursive aliases and unsupported tags produce
+diagnostics instead of guessed summaries. Arbitrary YAML, Helm templates and
+unrecognized schemas remain unsupported. Named summaries describe structure,
+not schema validity, evaluated expressions or deployment behavior. Action input
+and output names are summarized without copying their defaults or values.
+
 TypeScript/JavaScript, Go, Rust, and Haskell helper setup is explicit; prepare
 helper dependencies and binaries with `llm-wiki prepare-extractors`. Lint, CI,
 and extract never run `npm install`, `go build`, `go run`, `cargo build`,
@@ -153,7 +215,7 @@ and extract never run `npm install`, `go build`, `go run`, `cargo build`,
 Source discovery honors `.gitignore` before extractors run. Unescaped trailing
 ASCII spaces in ignore entries are ignored, while `\ ` preserves a literal
 final space. A root, unanchored `lib/` rule is treated as a generic build-output
-pattern for TypeScript projects, so `.ts`, `.tsx`, `.js`, and `.jsx` files under
+pattern for TypeScript projects, so `.ts`, `.tsx`, `.js`, `.jsx`, `.mjs`, and `.cjs` files under
 `src/lib/` remain first-party source; top-level `lib/`, excluded
 dependency/build directories, and explicit nested `.gitignore` rules still stay
 excluded. Generated agent
@@ -239,6 +301,10 @@ CPP branches. Source coordinates then refer to the supplied snapshot.
 | `cursor` | `.cursorrules` | explicit sync or reviewed IDE prompt |
 | `generic` | `AGENTS.md` | explicit sync or reviewed IDE prompt |
 
+For package installation, project initialization, managed instruction upgrades,
+and the `--no-skills` inline fallback, follow
+[workflow installation in another project](native-agent-workflow.md#install-the-workflow-in-another-project).
+
 Use explicit `sync` and `lint` commands with any agent. `generate-prompt`
 creates a prompt for review when needed. LLM Wiki does not install Git hooks. The explicit
 `trigger-agent` command can still delegate to a CLI agent; for Claude, this uses

{agent_wiki_cli-2.4.0 → agent_wiki_cli-2.5.0}/pyproject.toml

@@ -5,7 +5,7 @@ backend-path = ["."]
 
 [project]
 name = "agent-wiki-cli"
-version = "2.4.0"
+version = "2.5.0"
 description = "CLI tool to maintain hybrid LLM Wikis for multi-language projects."
 readme = "README.md"
 license = "MIT"
@@ -135,6 +135,7 @@ where = ["src"]
     "skills/wiki-reference/SKILL.md",
     "skills/wiki-reference/reference.md",
     "skills/wiki-reference/references/context-query.md",
+    "skills/wiki-reference/references/development-workflow.md",
     "skills/wiki-reference/references/extractors-dependencies.md",
     "skills/wiki-reference/references/governance.md",
     "skills/wiki-reference/references/knowledge-consumption.md",

{agent_wiki_cli-2.4.0 → agent_wiki_cli-2.5.0/src/agent_wiki_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agent-wiki-cli
-Version: 2.4.0
+Version: 2.5.0
 Summary: CLI tool to maintain hybrid LLM Wikis for multi-language projects.
 Author-email: Denis Sivagin <denissvgn@gmail.com>
 License-Expression: MIT
@@ -127,8 +127,8 @@ for [Obsidian](docs/cli-reference.md#obsidian) or a
 | Go | `go/ast` | prepared helper binary |
 | Rust | `syn` | prepared helper binary |
 | Haskell | GHC parser, syntax-only inventory | prepared helper binary |
-| Docker / Compose | built-in parsers | none |
-| Runtime/config YAML | targeted built-in parsers | none |
+| Docker / Compose | Dockerfile parser / bounded YAML parser | included with the package |
+| Infrastructure / runtime YAML | structured format summaries | included with the package |
 | OpenAPI 3.0/3.1 JSON / YAML | `json` / PyYAML safe loader | included with the package |
 
 Discovery honors `.gitignore`. Use a
@@ -143,7 +143,9 @@ initialization. Every agent can use explicit sync, lint, and reviewed prompts;
 LLM Wiki does not install Git hooks.
 
 [Agent setup](docs/wiki-guide.md#agent-support) explains instruction files and
-skill export. The [MCP server](docs/cli-reference.md#mcp) provides read-only wiki
+skill export. [Workflow installation and upgrades](docs/native-agent-workflow.md#install-the-workflow-in-another-project)
+cover setup in another project, all agent targets, and the `--no-skills` inline fallback.
+The [MCP server](docs/cli-reference.md#mcp) provides read-only wiki
 access, and [bundled skills](docs/cli-reference.md#skills) guide documentation
 and analysis workflows.