ai-wiki-toolkit-linux-arm64 0.1.20 → 0.1.22

package/README.md

@@ -1,7 +1,7 @@
 # ai-wiki-toolkit-linux-arm64
 
 This package contains the `aiwiki-toolkit` executable for `linux-arm64-glibc`.
-It is published as the platform-specific binary package for `ai-wiki-toolkit` `0.1.20`.
+It is published as the platform-specific binary package for `ai-wiki-toolkit` `0.1.22`.
 Most users should install `ai-wiki-toolkit` instead of using this package directly.
 
 ---
@@ -87,11 +87,32 @@ That is why the installer manages both wiki files and prompt wiring together:
 
 - `ai-wiki/` and `~/ai-wiki/system/` hold the durable Markdown memory
 - `AGENT.md`, `AGENTS.md`, or `CLAUDE.md` tell the agent to read that memory and follow the workflow
+- `aiwiki-toolkit route` generates a task-aware context packet so the agent can load the most relevant memory before falling back to the broader read order
 - `.agents/skills/ai-wiki-reuse-check/` and `.agents/skills/ai-wiki-update-check/` provide repeatable end-of-task checks for Codex-style agent runs
 - `.agents/skills/ai-wiki-clarify-before-code/` and `.agents/skills/ai-wiki-capture-review-learning/` help agents clarify ambiguous requests and preserve reusable review feedback
 
 The toolkit does not replace coding agents. It gives them a shared repo-local memory layer so they can avoid repeating the same review issues, misunderstanding the same requirements, or rediscovering the same fixes.
 
+## Task-Aware Context Routing
+
+The managed prompt block asks agents to run `aiwiki-toolkit route --task "<current user request>"`
+at the start of a task when the command is available.
+
+Users do not need to run this manually during normal agent use. The agent supplies the current task
+text because the CLI cannot see the private chat request on its own.
+
+The command emits a transient AI Wiki Context Packet with:
+
+- a coarse task type and risk tags
+- `must_load` docs to consult first
+- source-cited `must_follow` rules extracted from authoritative user-owned docs
+- exploratory `context_notes` from drafts or other non-authoritative docs
+- lower-confidence `maybe_load` docs and explicit skip reasons
+
+Markdown remains the source of truth. A context packet is a generated, auditable working set for the
+current task, not canonical memory. Agents should record reuse only for user-owned docs they actually
+consult or materially use.
+
 ## Prompt File Integration
 
 Many coding-agent setups already create one of these repo-shared prompt files:
@@ -218,6 +239,9 @@ npm install -g ai-wiki-toolkit@latest
 
 - Files under `ai-wiki/_toolkit/**` and `~/ai-wiki/system/_toolkit/**` are package-managed.
 - Files such as `ai-wiki/index.md`, `ai-wiki/workflows.md`, and other docs you add under `ai-wiki/` are user-owned.
+- Starter files such as `ai-wiki/constraints.md` and `ai-wiki/decisions.md` may look mostly empty
+  after install. That is intentional: they are placeholders for rules and decisions your team has
+  actually made, not generic package defaults.
 - `ai-wiki/_toolkit/system.md` is the managed entrypoint for package-managed repo guidance and evolving read order.
 - `ai-wiki/index.md` is a repo-owned map, not a package upgrade surface.
 - `ai-wiki/_toolkit/workflows.md` carries the managed baseline workflows that package upgrades can refresh.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-wiki-toolkit-linux-arm64",
-  "version": "0.1.20",
+  "version": "0.1.22",
   "description": "Platform binary package for ai-wiki-toolkit (linux-arm64-glibc).",
   "license": "MIT",
   "homepage": "https://github.com/BochengYin/ai-wiki-toolkit#readme",