akm-cli 0.9.0-rc.5 → 0.9.0-rc.7

package/dist/assets/stash-skeleton/facts/conventions/assets/skill.md

@@ -42,6 +42,6 @@ Use a skill when the stash needs reusable procedural guidance for a recurring cl
 ## Placement & linking
 
 - Skills are **reuse-born**: place `skills/<domain>/<name>/SKILL.md` under a
-  stable **domain** prefix from `fact:conventions/domains`
-  (`skill:testing/flaky-test-triage`) so any project finds and reuses it instead
+  stable **domain** prefix from `facts/conventions/domains`
+  (`skills/testing/flaky-test-triage`) so any project finds and reuses it instead
   of duplicating the procedure.

package/dist/assets/stash-skeleton/facts/conventions/assets/workflow.md

@@ -45,5 +45,5 @@ Use a workflow when the task requires multiple steps, branching decisions, repea
 ## Placement & linking
 
 - Workflows are usually **global**: keep them at the type root or under a
-  tool/domain slug (`workflow:release-train`). Scoping a workflow to one project
+  tool/domain slug (`workflows/release-train`). Scoping a workflow to one project
   rarely improves retrieval and adds rename risk.

package/dist/assets/stash-skeleton/facts/conventions/backlinks.md

@@ -1,7 +1,7 @@
 ---
 category: convention
 description: How to cross-link assets so retrieval compounds — a provenance xref when derived, sparse real associative xrefs, corrections as new assets, and canonical entity naming.
-when_to_use: Surfaced to authoring agents when they create or revise any non-wiki asset that derives from, corrects, or relates to another asset.
+when_to_use: Surfaced to authoring agents when they create or revise any asset that derives from, corrects, or relates to another asset.
 ---
 
 <!--
@@ -9,8 +9,8 @@ when_to_use: Surfaced to authoring agents when they create or revise any non-wik
   mechanism, not decoration: `xrefs:` frontmatter folds into the search index;
   the entity/relation graph is extracted from BODY prose (memory + knowledge),
   never from frontmatter. Over-linking degrades ranking, so these rules are
-  deliberately conservative. Wikis have their own xref + lint system — this
-  convention is for non-wiki assets.
+  deliberately conservative. (LLM-wiki bundles carry their own xref system in
+  their pages' frontmatter — this convention is for in-stash assets.)
 -->
 
 # Back-linking conventions
@@ -26,36 +26,37 @@ lever — which means both too few and too many hurt.
 description: OAuth refresh-token race on token rotation
 tags: [auth, projectA]
 xrefs:
-  - knowledge:auth/vendor-x-token-api   # provenance: what this was synthesized from
-  - lesson:projectA/token-refresh-gotcha # one real associative link
+  - knowledge/auth/vendor-x-token-api   # provenance: what this was synthesized from
+  - lessons/projectA/token-refresh-gotcha # one real associative link
 ---
 ```
 
 ## Link rules
 
 - **One xref is mandatory when the asset derives from another: cite the source
-  ref** (`memory:projectA/token-quirk` xrefs `knowledge:auth/vendor-x-token-api`
+  ref** (`memories/projectA/token-quirk` xrefs `knowledge/auth/vendor-x-token-api`
   — it also makes this asset findable from searches for its source). An
   original observation with no source carries none — never invent provenance.
   `akm remember`/`akm import` write this channel via `--xref <ref>`
-  (repeatable; refs are checked at write time). Wikis enforce the analogous
-  rule mechanically (`sources:` + `uncited-raw` lint); non-wiki provenance is
-  discipline only.
+  (repeatable; refs are checked at write time). LLM-wiki bundles enforce the
+  analogous rule mechanically (`sources:` frontmatter citations); in-stash
+  provenance is discipline only.
 - **Associative xrefs are discretionary — real relationships only.** Add one when
   you already know a genuine load-bearing connection. Do **not** hit a link
   quota by pointing at the topically-nearest sibling — a plausible-but-wrong
   xref makes this asset a false search match for the other topic, and a wrong
   relationship asserted in prose poisons the entity graph. A relationship you
   want the graph to learn must be named in the body (e.g. open with "Corrects
-  knowledge:auth/oauth-refresh-races").
+  knowledge/auth/oauth-refresh-races").
 - **Cap total xrefs at ~5 (a heuristic, not a measured threshold).** Each xref
   folds its ref tokens into THIS asset's search hints — past a handful, the
   asset matches queries about several other topics and its own ranking signal
   blurs.
-- **Corrections are new assets; ingested material is immutable.** Treat wiki
-  `raw/`, vendored docs, and transcripts as immutable-by-discipline: a hard-won
-  fix is a new `lesson:` or `knowledge:` asset that xrefs what it corrects.
-  Synthesized `knowledge:` pages are the rewritable layer — update them in
+- **Corrections are new assets; ingested material is immutable.** Treat
+  ingested raw material, vendored docs, and transcripts as
+  immutable-by-discipline: a hard-won fix is a new `lessons/` or `knowledge/`
+  asset that xrefs what it corrects.
+  Synthesized `knowledge/` pages are the rewritable layer — update them in
   place. When a correction supersedes a standalone asset (memory OR knowledge),
   also set the old asset's `beliefState: superseded` and
   `supersededBy: [<new ref>]` — a metadata edit, not a content edit — so the
@@ -78,14 +79,13 @@ open the body with a plain title plus a one-line
 orientation naming what it is, its scope/domain, and its key entities in
 canonical spelling (`Postgres`, `OAuth`, `TLS`, `Acme`) — the entity/relation
 graph is extracted from body prose, and readers land here from `akm show`.
-Keep the canonical-spelling list in `fact:conventions/domains` so agents don't
+Keep the canonical-spelling list in `facts/conventions/domains` so agents don't
 fragment `postgres` / `postgresql` / `pg`.
 
 ## Hubs are optional, not per-namespace obligations
 
-A hub (a `wiki:` overview page that xrefs the key assets in a domain) is worth
-authoring for a **few genuinely high-traffic domains** — wikis are the one type
-with real orphan/broken-xref/stale-index lint to keep a hub honest. Do **not**
+A hub (a `knowledge/` overview page that xrefs the key assets in a domain) is
+worth authoring for a **few genuinely high-traffic domains**. Do **not**
 mandate a hub per namespace and do not edit a hub on every write: that is O(n)
 maintenance, a concurrent-write contention point, and it flattens the multi-hop
 graph into a namespace-wide star. Let the FTS index be the catalog; spend the

package/dist/assets/stash-skeleton/facts/conventions/domains.md

@@ -1,7 +1,7 @@
 ---
 category: convention
-description: The closed vocabulary of domain prefixes for reuse-born assets (knowledge/skill/wiki/fact/script), plus canonical entity spellings. Edit this to match your stash.
-when_to_use: Surfaced to authoring agents alongside the other convention facts; consult it when picking a domain prefix for a knowledge, skill, fact, or script asset (for wikis, the domain names the wiki).
+description: The closed vocabulary of domain prefixes for reuse-born assets (knowledge/skill/fact/script), plus canonical entity spellings. Edit this to match your stash.
+when_to_use: Surfaced to authoring agents alongside the other convention facts; consult it when picking a domain prefix for a knowledge, skill, fact, or script asset.
 ---
 
 <!--
@@ -14,10 +14,9 @@ when_to_use: Surfaced to authoring agents alongside the other convention facts;
 
 # Domain vocabulary
 
-Reuse-born assets (`knowledge`, `skill`, `wiki`, `fact`, `script`) take a
-**domain prefix** from this list, e.g. `knowledge:auth/oauth-refresh-races`,
-`skill:testing/flaky-test-triage` (for a wiki, the domain names the wiki:
-`wikis/auth/`). Pick the closest match. If two fit, take the one naming the
+Reuse-born assets (`knowledge`, `skill`, `fact`, `script`) take a
+**domain prefix** from this list, e.g. `knowledge/auth/oauth-refresh-races`,
+`skills/testing/flaky-test-triage`. Pick the closest match. If two fit, take the one naming the
 SUBJECT of the doc (what it teaches, not where it was met) and put the other in
 tags; if still tied, the earlier entry in this list wins. If nothing fits, write
 the asset at the type root and propose an addition here — do **not** invent a
@@ -41,8 +40,8 @@ volume justifies it.
 - `frontend` — UI, rendering, client state
 - `data-pipelines` — ETL, streaming, batch processing
 - `tooling` — dev tooling, editor/agent integration, scripts
-- `policies` — organizational/business rules the work must obey (PII handling, licensing) (`fact:policies/…`)
-- `conventions` — stash authoring house-rules (`fact:conventions/…`; auto-surfaced to authoring agents — keep them in this directory)
+- `policies` — organizational/business rules the work must obey (PII handling, licensing) (`facts/policies/…`)
+- `conventions` — stash authoring house-rules (`facts/conventions/…`; auto-surfaced to authoring agents — keep them in this directory)
 
 ## Canonical entity spellings
 
@@ -57,7 +56,7 @@ fragment the entity graph. Extend as your stash grows.
 
 Project and client slugs are **not** listed here — those are scope slugs for
 scope-born types (`memory`, `lesson`, `task`, `env`, `secret`). Keep their
-canonical spellings in a `category: meta` fact (e.g. `fact:active-projects`) so
+canonical spellings in a `category: meta` fact (e.g. `facts/active-projects`) so
 they auto-inject at authoring time — not in `.meta/`, which is unindexed and
 invisible mid-task — and `akm search` for an existing spelling before minting a
 new one.

package/dist/assets/stash-skeleton/facts/conventions/organization.md

@@ -1,7 +1,7 @@
 ---
 category: convention
 description: Where to place an asset in the stash — the one path partition axis, chosen by asset type, so refs stay stable and slug search (akm search "<slug>" --type <type>) co-locates related assets.
-when_to_use: Surfaced to authoring agents when they create or move any non-wiki asset and must decide its subdirectory/name.
+when_to_use: Surfaced to authoring agents when they create or move any asset and must decide its subdirectory/name.
 ---
 
 <!--
@@ -14,7 +14,7 @@ when_to_use: Surfaced to authoring agents when they create or move any non-wiki
 # Stash organization conventions
 
 A file's path under its type directory **becomes part of its ref**
-(`knowledge/auth/oauth-refresh-races.md` → `knowledge:auth/oauth-refresh-races`).
+(`knowledge/auth/oauth-refresh-races.md` → `knowledge/auth/oauth-refresh-races`).
 That ref is an address other assets cite, and its segments are search terms —
 `akm search "projectA" --type memory` reconstructs a project's memories. The
 path is therefore the one facet you **cannot express twice and cannot change
@@ -39,18 +39,16 @@ differently and bake the wrong guess into an immutable ref. Decide by type:
   `git remote`/package.json spell it) — ranking auto-boosts assets whose name
   or tags match the current repo. Client/team slugs get no such boost; just
   reuse the existing spelling.
-  - `memory:projectA/auth-token-refresh`
-  - `lesson:clientX/migration-rollback-gotcha`
-  - `secret:clientX/api-key`
+  - `memories/projectA/auth-token-refresh`
+  - `lessons/clientX/migration-rollback-gotcha`
+  - `secrets/clientX/api-key`
 - **Reuse-born types → stable domain from a short vocabulary.**
-  `knowledge`, `skill`, `wiki`, `fact`, `script`. These are meant to be reused
+  `knowledge`, `skill`, `fact`, `script`. These are meant to be reused
   across projects, so co-locate them by subject — any project retrieves them
-  with `akm search "<domain>" --type <type>`. For a wiki the domain names the
-  wiki itself (`wikis/auth/`); inside it, its `schema.md` and wiki lint govern
-  layout, not these rules.
-  - `knowledge:auth/oauth-refresh-races`
-  - `skill:testing/flaky-test-triage`
-  - `fact:policies/pii-handling`
+  with `akm search "<domain>" --type <type>`.
+  - `knowledge/auth/oauth-refresh-races`
+  - `skills/testing/flaky-test-triage`
+  - `facts/policies/pii-handling`
 - **Global-by-nature types → type root or a tool slug.**
   `command`, `agent`, `workflow`, and stash-wide `env`. Scoping these to a
   project rarely improves precision and only adds rename risk. `env` defaults
@@ -78,13 +76,13 @@ cross-project reuse.
   author, `wip`/`done`. Each one changes and forces a ref-breaking rename. They
   belong in frontmatter tags.
 - **Flat fallback beats an invented folder.** If no domain fits a reuse-type
-  asset, write it at the type root (`knowledge:http-retry-basics`) rather than
+  asset, write it at the type root (`knowledge/http-retry-basics`) rather than
   coining a one-off domain. An unneeded folder is pure rename liability; propose
   a vocabulary addition instead of fragmenting the tree.
 - **Reuse an existing slug before minting a new one.** Before coining a new
   project/client/domain slug, `akm search` for the existing spelling
   (`acme` vs `acme-corp`) so the prefix does not fragment. Keep the domain
-  vocabulary in `fact:conventions/domains`.
+  vocabulary in `facts/conventions/domains`.
 - **Off-axis facets go in `tags:`, not a bare field.** The indexed FTS fields are
   name, description, tags, hints, and content (headings only — body prose is
   not indexed by default; the opt-in `index.indexBodyOpening` flag adds just
@@ -115,7 +113,7 @@ cross-project reuse.
   xref-fixing operation: grep the stash for the old ref string and fix every
   inbound reference in the same pass.
 - When a project-scoped note turns out to be domain-general, **append, don't
-  promote**: write a new `knowledge:<domain>/…` asset that xrefs the originating
+  promote**: write a new `knowledge/<domain>/…` asset that xrefs the originating
   memory. Never rename the memory up a rung — that breaks its ref. The atomic
   note still serves factoid recall; the new synthesis serves reuse; the xref
   bridges them.

package/dist/assets/tasks/core/extract.yml

@@ -1,5 +1,5 @@
 version: 2
 schedule: "*/30 * * * *"
-command: akm extract
+command: akm extract --auto
 enabled: true
-description: Extract insights from session files every 30 min
+description: Opt-in all-harness session extraction every 30 min

package/dist/assets/tasks/core/improve.yml

@@ -1,5 +1,5 @@
 version: 2
 schedule: "0 2 * * *"
-command: akm improve --auto-accept safe
+command: akm improve
 enabled: true
 description: Run improve pipeline nightly

package/dist/assets/templates/html/health.html

@@ -4,9 +4,8 @@
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
   <title>%%REPORT_TITLE%%</title>
-  <!-- %%ECHARTS_TAG%% : either an inlined <script>…echarts…</script> (self-contained
-       / deterministic / offline) or a CDN <script src> when the renderer is run
-       with --echarts cdn. -->
+  <!-- %%ECHARTS_TAG%% : a <script src> pointed at the jsDelivr CDN (chunk-9
+       WI-9.4d) — viewing this report requires network access. -->
   %%ECHARTS_TAG%%
   <style>
     *, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }