ai-wiki-toolkit-linux-arm64 0.1.21 → 0.1.23

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.21`.
+It is published as the platform-specific binary package for `ai-wiki-toolkit` `0.1.23`.
 Most users should install `ai-wiki-toolkit` instead of using this package directly.
 
 ---
@@ -87,11 +87,35 @@ 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
+- an effort level so simple operational tasks can stay lightweight
+- index cards with short descriptions and reference links for relevant memory
+- `must_load` docs to consult first when direct context is required
+- 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. Packet word limits are safety caps, not fill targets; agents should open
+linked reference files at runtime when an index card is relevant and the task needs more detail.
+
 ## Prompt File Integration
 
 Many coding-agent setups already create one of these repo-shared prompt files:
@@ -109,7 +133,7 @@ If none of those files exist yet, the toolkit creates `AGENT.md` as a generic de
 
 The AI wiki structure is deliberately inspired by how `SKILL.md` files work well: keep a small stable entrypoint, then fan out into focused references.
 
-Each wiki namespace starts with an `index.md` and then links to narrower files such as `constraints.md`, `conventions/`, `workflows.md`, `decisions.md`, `review-patterns/`, `problems/`, `features/`, `trails/`, and personal `drafts/`. The package-managed start-of-task routing lives in `ai-wiki/_toolkit/system.md`, while repo-owned indexes stay stable maps that humans can customize without turning them into package upgrade surfaces.
+Each wiki namespace starts with an `index.md` and then links to narrower files such as `constraints.md`, `conventions/`, `workflows.md`, `decisions.md`, `review-patterns/`, `problems/`, `features/`, `trails/`, `work/`, and personal `drafts/`. The package-managed start-of-task routing lives in `ai-wiki/_toolkit/system.md`, while repo-owned indexes stay stable maps that humans can customize without turning them into package upgrade surfaces.
 
 ## Current Scope
 
@@ -118,9 +142,10 @@ The current scope is intentionally strict about compatibility:
 - initialize the repo and home AI wiki folders
 - create starter Markdown files only if they do not already exist
 - create managed `_toolkit/` files that package updates are allowed to refresh
-- create `conventions/`, `review-patterns/`, `problems/`, `features/`, and `people/<handle>/drafts/` scaffolding
+- create `conventions/`, `review-patterns/`, `problems/`, `features/`, `work/`, and `people/<handle>/drafts/` scaffolding
 - create or refresh package-owned repo-local `.agents/skills/ai-wiki-reuse-check/`, `.agents/skills/ai-wiki-update-check/`, `.agents/skills/ai-wiki-clarify-before-code/`, `.agents/skills/ai-wiki-capture-review-learning/`, and `.agents/skills/ai-wiki-consolidate-drafts/` skills
 - create a managed `_toolkit/schema/team-memory-v1.md` guide for lightweight team coding memory
+- create a managed `_toolkit/schema/work-v1.md` guide and local generated work views for repo-native todo/epic lifecycle state
 - update managed instruction blocks inside `AGENT.md`, `AGENTS.md`, and `CLAUDE.md`
 - avoid rewriting existing user-owned `ai-wiki/**/*.md` documents outside `_toolkit/`
 
@@ -162,6 +187,13 @@ The Homebrew formula and npm distribution both consume the same versioned GitHub
 
 The npm package is a thin meta package that installs the matching platform-specific binary package for the current machine. It does not fetch release assets during `postinstall`.
 
+Enterprise/security notes for npm installs:
+
+- the root npm package does not define `preinstall`, `install`, `postinstall`, `prepare`, or other lifecycle scripts
+- the platform binary packages are installed through normal npm package resolution instead of an install-time downloader
+- `npm install -g ai-wiki-toolkit --ignore-scripts` is compatible with the package topology because install scripts are not required
+- global installation adds the `aiwiki-toolkit` command, but repo files are modified only when a user explicitly runs `aiwiki-toolkit install` inside a git repository
+
 2. Enter the target git repository and initialize the wiki scaffolding:
 
 ```bash
@@ -263,10 +295,11 @@ aiwiki-toolkit init
 
 - create `ai-wiki/` inside the current repository
 - create `~/ai-wiki/system/`
-- create starter indexes such as `ai-wiki/conventions/index.md`, `ai-wiki/review-patterns/index.md`, `ai-wiki/problems/index.md`, `ai-wiki/features/index.md`, `ai-wiki/trails/index.md`, and `ai-wiki/people/<handle>/index.md`
-- create `ai-wiki/conventions/`, `ai-wiki/review-patterns/`, `ai-wiki/problems/`, `ai-wiki/features/`, `ai-wiki/people/<handle>/drafts/`, `ai-wiki/metrics/`, and repo/home `_toolkit/`
-- generate package-managed `_toolkit/index.md`, `_toolkit/workflows.md`, `_toolkit/catalog.json`, `_toolkit/schema/reuse-v1.md`, `_toolkit/schema/team-memory-v1.md`, and `_toolkit/metrics/*.json`
-- upsert a managed `.gitignore` block that ignores AI wiki telemetry and generated aggregate snapshots so routine agent use does not dirty `git status`
+- create a gitignored `.env.aiwiki` file for the current local actor identity
+- create starter indexes such as `ai-wiki/conventions/index.md`, `ai-wiki/review-patterns/index.md`, `ai-wiki/problems/index.md`, `ai-wiki/features/index.md`, `ai-wiki/trails/index.md`, `ai-wiki/work/index.md`, and `ai-wiki/people/<handle>/index.md`
+- create `ai-wiki/conventions/`, `ai-wiki/review-patterns/`, `ai-wiki/problems/`, `ai-wiki/features/`, `ai-wiki/work/`, `ai-wiki/people/<handle>/drafts/`, `ai-wiki/metrics/`, and repo/home `_toolkit/`
+- generate package-managed `_toolkit/index.md`, `_toolkit/workflows.md`, `_toolkit/catalog.json`, `_toolkit/schema/reuse-v1.md`, `_toolkit/schema/team-memory-v1.md`, `_toolkit/schema/work-v1.md`, `_toolkit/metrics/*.json`, and `_toolkit/work/*`
+- upsert a managed `.gitignore` block that ignores `.env.aiwiki`, AI wiki telemetry, and generated aggregate snapshots so routine agent use does not dirty `git status`
 - create or refresh package-owned `.agents/skills/ai-wiki-reuse-check/`, `.agents/skills/ai-wiki-update-check/`, `.agents/skills/ai-wiki-clarify-before-code/`, `.agents/skills/ai-wiki-capture-review-learning/`, and `.agents/skills/ai-wiki-consolidate-drafts/`
 - update `AGENT.md`, `AGENTS.md`, and/or `CLAUDE.md` with a managed instruction block that reads `ai-wiki/_toolkit/system.md`
 
@@ -304,6 +337,41 @@ Only record user-owned AI wiki knowledge docs with `record-reuse`.
 
 Managed control-plane docs under `_toolkit/**` should still be cited in user-facing notes when they affect behavior, but they should not be logged as knowledge-reuse events.
 
+To turn conversation todos or epics into routeable repo-local work state:
+
+```bash
+aiwiki-toolkit work capture \
+  --work-id aiwiki-framework-roadmap \
+  --title "Build the coding agent working framework" \
+  --item-type epic \
+  --status proposed \
+  --source conversation
+
+aiwiki-toolkit work capture \
+  --work-id work-ledger \
+  --title "Capture conversation todos as AI wiki work state" \
+  --status todo \
+  --epic-id aiwiki-framework-roadmap \
+  --assignee your-handle \
+  --link ai-wiki/people/your-handle/drafts/agent-framework-roadmap.md
+
+aiwiki-toolkit work status \
+  --work-id work-ledger \
+  --status processing
+```
+
+By default, `work capture` resolves the current actor from explicit CLI input, environment, `.env.aiwiki`, git config, then fallback. It uses that actor as `author_handle`, `reporter_handle`, and the default assignee. This appends to `ai-wiki/work/events/<handle>.jsonl` and regenerates local package-managed views under `ai-wiki/_toolkit/work/`. Route packets can then surface matching active, processing, blocked, planned, or todo work items before an agent starts acting. Work events are not knowledge-reuse evidence by themselves, so they are kept separate from `record-reuse`.
+
+For team use, canonical work stays in the central `ai-wiki/work/events/` ledger. People are linked through `reporter_handle` and `assignee_handles`; work is not stored inside `people/<handle>/`. Use these views when you need owner-scoped state:
+
+```bash
+aiwiki-toolkit work mine
+aiwiki-toolkit work list --assignee your-handle
+aiwiki-toolkit work list --reporter your-handle --include-closed
+```
+
+Generated local views are also written under `ai-wiki/_toolkit/work/by-assignee/` and `ai-wiki/_toolkit/work/by-reporter/`. Route packets treat work assigned to the current `.env.aiwiki` actor as actionable by default; another person's work appears only when directly matched by the current task request.
+
 To record that a completed task was checked for AI wiki reuse, even when no wiki docs were needed:
 
 ```bash
@@ -321,7 +389,7 @@ Both metrics logs are sharded by handle under:
 
 These logs are intended as local telemetry by default, not merge-heavy source files.
 
-If you need a fresh local telemetry snapshot, regenerate package-managed aggregate views such as `ai-wiki/_toolkit/catalog.json` or `ai-wiki/_toolkit/metrics/*.json` with:
+If you need a fresh local telemetry and work snapshot, regenerate package-managed aggregate views such as `ai-wiki/_toolkit/catalog.json`, `ai-wiki/_toolkit/metrics/*.json`, or `ai-wiki/_toolkit/work/*` with:
 
 ```bash
 aiwiki-toolkit refresh-metrics
@@ -341,10 +409,11 @@ This command does not rewrite user-owned repo docs. It prints which paths need a
 - `ai-wiki/problems/index.md`
 - `ai-wiki/features/index.md`
 - `ai-wiki/trails/index.md`
+- `ai-wiki/work/index.md`
 - `ai-wiki/people/<handle>/index.md`
 - `ai-wiki/metrics/index.md`
 
-It also checks whether the managed `.gitignore` block is present and whether telemetry paths are still tracked in the git index from older versions. If those paths are still tracked, `doctor` prints a one-time `git rm --cached` command to untrack them.
+It also checks whether the managed `.gitignore` block is present and whether local identity, telemetry, or generated-view paths are still tracked in the git index from older versions. If those paths are still tracked, `doctor` prints a one-time `git rm --cached` command to untrack them.
 
 To remove the managed layer while keeping your user-owned wiki documents:
 
@@ -355,7 +424,7 @@ aiwiki-toolkit uninstall
 This removes:
 
 - managed prompt blocks from `AGENT.md` / `AGENTS.md` / `CLAUDE.md`
-- the managed `.gitignore` block for AI wiki telemetry
+- the managed `.gitignore` block for AI wiki local identity and telemetry
 - `ai-wiki/_toolkit/**`
 - `~/ai-wiki/system/_toolkit/**`
 - the `aiwikiToolkit` key from `opencode.json`
@@ -374,11 +443,12 @@ Even with `--purge-user-docs --yes`, the shared home wiki under `~/ai-wiki/syste
 
 - Existing user-owned `ai-wiki/**/*.md` files are treated as stable data.
 - `install`/`init` only create missing starter files; they do not merge or overwrite existing user wiki documents.
-- Starter indexes such as `ai-wiki/index.md`, `conventions/index.md`, `review-patterns/index.md`, `problems/index.md`, `features/index.md`, `trails/index.md`, `people/<handle>/index.md`, and `metrics/index.md` become user-owned once created and are not rewritten by future package updates.
+- Starter indexes such as `ai-wiki/index.md`, `conventions/index.md`, `review-patterns/index.md`, `problems/index.md`, `features/index.md`, `trails/index.md`, `work/index.md`, `people/<handle>/index.md`, and `metrics/index.md` become user-owned once created and are not rewritten by future package updates.
 - `ai-wiki/_toolkit/**` and `~/ai-wiki/system/_toolkit/**` are package-managed and may be refreshed by future versions.
 - `ai-wiki/index.md` is a repo-owned map and is not treated as a starter-drift upgrade target by `doctor`.
 - `ai-wiki/workflows.md` remains user-owned; package-managed workflow updates land in `ai-wiki/_toolkit/workflows.md` instead of rewriting the repo-owned file.
-- `ai-wiki/metrics/reuse-events/<handle>.jsonl` and `ai-wiki/metrics/task-checks/<handle>.jsonl` are user-owned evidence data. Package-managed aggregate views are regenerated under `ai-wiki/_toolkit/metrics/`, and the installer ignores all of those telemetry paths by default in `.gitignore`.
+- `.env.aiwiki` stores the current local actor identity in a managed block. It is gitignored and should not be committed.
+- `ai-wiki/metrics/reuse-events/<handle>.jsonl` and `ai-wiki/metrics/task-checks/<handle>.jsonl` are user-owned evidence data. `ai-wiki/work/events/<handle>.jsonl` is user-owned work state. Package-managed aggregate views are regenerated under `ai-wiki/_toolkit/metrics/` and `ai-wiki/_toolkit/work/`, and the installer ignores those generated paths by default in `.gitignore`.
 - Legacy flat files such as `ai-wiki/metrics/reuse-events.jsonl` and `ai-wiki/metrics/task-checks.jsonl` are still read for compatibility, but new writes should use the handle-sharded layout.
 - `aiwiki-toolkit doctor --suggest-index-upgrade` prints suggested replacements for missing repo starter docs and repo-owned companion docs such as `ai-wiki/workflows.md`, but it does not overwrite them automatically.
 - Package-owned `.agents/skills/ai-wiki-reuse-check/**`, `.agents/skills/ai-wiki-update-check/**`, `.agents/skills/ai-wiki-clarify-before-code/**`, `.agents/skills/ai-wiki-capture-review-learning/**`, and `.agents/skills/ai-wiki-consolidate-drafts/**` are refreshed by `install` so package workflow updates reach existing repos.

package/package.json

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