Promote llm-wiki and analysis-ledger

[monoxgas]

What

• promotes analysis-ledger as a public capability at 0.2.1
• hard-forks the private item-wiki prototype into the public llm-wiki capability at 0.1.0
• ships typed Agent Output schemas, focused frontier/progress tools, agents, skills, tests, and public installation docs
• updates provenance and current Agent Output UI terminology

Why

Both capabilities preserve useful state beyond a model context window without introducing a workflow engine:

• llm-wiki compiles source material into durable, linked wiki_page items
• analysis-ledger maintains a resumable code-analysis frontier with evidence-bearing claims

The names are intentionally asymmetric: llm-wiki is specific enough for catalog discovery while analysis-ledger already describes its domain and mechanism cleanly.

Compatibility and impact

• This is an intentional hard fork from item-wiki to llm-wiki; there is no alias or compatibility shim.
• Existing private item-wiki users must install and invoke llm-wiki explicitly.
• analysis-ledger advances from private version 0.2.0 to 0.2.1 for the publication/documentation corrections.

Review

A formal reviewing-capabilities pass covered manifest structure, agent/skill contracts, tool naming and defaults, return shapes, bounded scans, Agent Output schemas, documentation, provenance, and publication readiness. No MCP ecosystem review was needed because neither capability ships an MCP server.

Validation

• uv run --with dreadnode==2.0.38 dreadnode capability validate capabilities/llm-wiki --strict
• uv run --with dreadnode==2.0.38 dreadnode capability validate capabilities/analysis-ledger --strict
• uv run --with dreadnode==2.0.38 --with pytest --with jsonschema --with pyyaml pytest -q capabilities/llm-wiki/tests capabilities/analysis-ledger/tests — 13 passed
• pre-commit run --files $(rg --files capabilities/llm-wiki capabilities/analysis-ledger)
• just validate — 17 clean, 4 unrelated optional-tool warnings, 0 failed