ai-wiki-toolkit-linux-arm64 0.1.22 → 0.1.23
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +63 -14
- package/bin/aiwiki-toolkit +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# ai-wiki-toolkit-linux-arm64
|
|
2
2
|
|
|
3
3
|
This package contains the `aiwiki-toolkit` executable for `linux-arm64-glibc`.
|
|
4
|
-
It is published as the platform-specific binary package for `ai-wiki-toolkit` `0.1.
|
|
4
|
+
It is published as the platform-specific binary package for `ai-wiki-toolkit` `0.1.23`.
|
|
5
5
|
Most users should install `ai-wiki-toolkit` instead of using this package directly.
|
|
6
6
|
|
|
7
7
|
---
|
|
@@ -104,14 +104,17 @@ text because the CLI cannot see the private chat request on its own.
|
|
|
104
104
|
The command emits a transient AI Wiki Context Packet with:
|
|
105
105
|
|
|
106
106
|
- a coarse task type and risk tags
|
|
107
|
-
-
|
|
107
|
+
- an effort level so simple operational tasks can stay lightweight
|
|
108
|
+
- index cards with short descriptions and reference links for relevant memory
|
|
109
|
+
- `must_load` docs to consult first when direct context is required
|
|
108
110
|
- source-cited `must_follow` rules extracted from authoritative user-owned docs
|
|
109
111
|
- exploratory `context_notes` from drafts or other non-authoritative docs
|
|
110
112
|
- lower-confidence `maybe_load` docs and explicit skip reasons
|
|
111
113
|
|
|
112
114
|
Markdown remains the source of truth. A context packet is a generated, auditable working set for the
|
|
113
115
|
current task, not canonical memory. Agents should record reuse only for user-owned docs they actually
|
|
114
|
-
consult or materially use.
|
|
116
|
+
consult or materially use. Packet word limits are safety caps, not fill targets; agents should open
|
|
117
|
+
linked reference files at runtime when an index card is relevant and the task needs more detail.
|
|
115
118
|
|
|
116
119
|
## Prompt File Integration
|
|
117
120
|
|
|
@@ -130,7 +133,7 @@ If none of those files exist yet, the toolkit creates `AGENT.md` as a generic de
|
|
|
130
133
|
|
|
131
134
|
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.
|
|
132
135
|
|
|
133
|
-
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.
|
|
136
|
+
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.
|
|
134
137
|
|
|
135
138
|
## Current Scope
|
|
136
139
|
|
|
@@ -139,9 +142,10 @@ The current scope is intentionally strict about compatibility:
|
|
|
139
142
|
- initialize the repo and home AI wiki folders
|
|
140
143
|
- create starter Markdown files only if they do not already exist
|
|
141
144
|
- create managed `_toolkit/` files that package updates are allowed to refresh
|
|
142
|
-
- create `conventions/`, `review-patterns/`, `problems/`, `features/`, and `people/<handle>/drafts/` scaffolding
|
|
145
|
+
- create `conventions/`, `review-patterns/`, `problems/`, `features/`, `work/`, and `people/<handle>/drafts/` scaffolding
|
|
143
146
|
- 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
|
|
144
147
|
- create a managed `_toolkit/schema/team-memory-v1.md` guide for lightweight team coding memory
|
|
148
|
+
- create a managed `_toolkit/schema/work-v1.md` guide and local generated work views for repo-native todo/epic lifecycle state
|
|
145
149
|
- update managed instruction blocks inside `AGENT.md`, `AGENTS.md`, and `CLAUDE.md`
|
|
146
150
|
- avoid rewriting existing user-owned `ai-wiki/**/*.md` documents outside `_toolkit/`
|
|
147
151
|
|
|
@@ -183,6 +187,13 @@ The Homebrew formula and npm distribution both consume the same versioned GitHub
|
|
|
183
187
|
|
|
184
188
|
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`.
|
|
185
189
|
|
|
190
|
+
Enterprise/security notes for npm installs:
|
|
191
|
+
|
|
192
|
+
- the root npm package does not define `preinstall`, `install`, `postinstall`, `prepare`, or other lifecycle scripts
|
|
193
|
+
- the platform binary packages are installed through normal npm package resolution instead of an install-time downloader
|
|
194
|
+
- `npm install -g ai-wiki-toolkit --ignore-scripts` is compatible with the package topology because install scripts are not required
|
|
195
|
+
- 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
|
|
196
|
+
|
|
186
197
|
2. Enter the target git repository and initialize the wiki scaffolding:
|
|
187
198
|
|
|
188
199
|
```bash
|
|
@@ -284,10 +295,11 @@ aiwiki-toolkit init
|
|
|
284
295
|
|
|
285
296
|
- create `ai-wiki/` inside the current repository
|
|
286
297
|
- create `~/ai-wiki/system/`
|
|
287
|
-
- create
|
|
288
|
-
- create `ai-wiki/conventions
|
|
289
|
-
-
|
|
290
|
-
-
|
|
298
|
+
- create a gitignored `.env.aiwiki` file for the current local actor identity
|
|
299
|
+
- 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`
|
|
300
|
+
- 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/`
|
|
301
|
+
- 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/*`
|
|
302
|
+
- 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`
|
|
291
303
|
- 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/`
|
|
292
304
|
- update `AGENT.md`, `AGENTS.md`, and/or `CLAUDE.md` with a managed instruction block that reads `ai-wiki/_toolkit/system.md`
|
|
293
305
|
|
|
@@ -325,6 +337,41 @@ Only record user-owned AI wiki knowledge docs with `record-reuse`.
|
|
|
325
337
|
|
|
326
338
|
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.
|
|
327
339
|
|
|
340
|
+
To turn conversation todos or epics into routeable repo-local work state:
|
|
341
|
+
|
|
342
|
+
```bash
|
|
343
|
+
aiwiki-toolkit work capture \
|
|
344
|
+
--work-id aiwiki-framework-roadmap \
|
|
345
|
+
--title "Build the coding agent working framework" \
|
|
346
|
+
--item-type epic \
|
|
347
|
+
--status proposed \
|
|
348
|
+
--source conversation
|
|
349
|
+
|
|
350
|
+
aiwiki-toolkit work capture \
|
|
351
|
+
--work-id work-ledger \
|
|
352
|
+
--title "Capture conversation todos as AI wiki work state" \
|
|
353
|
+
--status todo \
|
|
354
|
+
--epic-id aiwiki-framework-roadmap \
|
|
355
|
+
--assignee your-handle \
|
|
356
|
+
--link ai-wiki/people/your-handle/drafts/agent-framework-roadmap.md
|
|
357
|
+
|
|
358
|
+
aiwiki-toolkit work status \
|
|
359
|
+
--work-id work-ledger \
|
|
360
|
+
--status processing
|
|
361
|
+
```
|
|
362
|
+
|
|
363
|
+
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`.
|
|
364
|
+
|
|
365
|
+
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:
|
|
366
|
+
|
|
367
|
+
```bash
|
|
368
|
+
aiwiki-toolkit work mine
|
|
369
|
+
aiwiki-toolkit work list --assignee your-handle
|
|
370
|
+
aiwiki-toolkit work list --reporter your-handle --include-closed
|
|
371
|
+
```
|
|
372
|
+
|
|
373
|
+
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.
|
|
374
|
+
|
|
328
375
|
To record that a completed task was checked for AI wiki reuse, even when no wiki docs were needed:
|
|
329
376
|
|
|
330
377
|
```bash
|
|
@@ -342,7 +389,7 @@ Both metrics logs are sharded by handle under:
|
|
|
342
389
|
|
|
343
390
|
These logs are intended as local telemetry by default, not merge-heavy source files.
|
|
344
391
|
|
|
345
|
-
If you need a fresh local telemetry snapshot, regenerate package-managed aggregate views such as `ai-wiki/_toolkit/catalog.json
|
|
392
|
+
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:
|
|
346
393
|
|
|
347
394
|
```bash
|
|
348
395
|
aiwiki-toolkit refresh-metrics
|
|
@@ -362,10 +409,11 @@ This command does not rewrite user-owned repo docs. It prints which paths need a
|
|
|
362
409
|
- `ai-wiki/problems/index.md`
|
|
363
410
|
- `ai-wiki/features/index.md`
|
|
364
411
|
- `ai-wiki/trails/index.md`
|
|
412
|
+
- `ai-wiki/work/index.md`
|
|
365
413
|
- `ai-wiki/people/<handle>/index.md`
|
|
366
414
|
- `ai-wiki/metrics/index.md`
|
|
367
415
|
|
|
368
|
-
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.
|
|
416
|
+
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.
|
|
369
417
|
|
|
370
418
|
To remove the managed layer while keeping your user-owned wiki documents:
|
|
371
419
|
|
|
@@ -376,7 +424,7 @@ aiwiki-toolkit uninstall
|
|
|
376
424
|
This removes:
|
|
377
425
|
|
|
378
426
|
- managed prompt blocks from `AGENT.md` / `AGENTS.md` / `CLAUDE.md`
|
|
379
|
-
- the managed `.gitignore` block for AI wiki telemetry
|
|
427
|
+
- the managed `.gitignore` block for AI wiki local identity and telemetry
|
|
380
428
|
- `ai-wiki/_toolkit/**`
|
|
381
429
|
- `~/ai-wiki/system/_toolkit/**`
|
|
382
430
|
- the `aiwikiToolkit` key from `opencode.json`
|
|
@@ -395,11 +443,12 @@ Even with `--purge-user-docs --yes`, the shared home wiki under `~/ai-wiki/syste
|
|
|
395
443
|
|
|
396
444
|
- Existing user-owned `ai-wiki/**/*.md` files are treated as stable data.
|
|
397
445
|
- `install`/`init` only create missing starter files; they do not merge or overwrite existing user wiki documents.
|
|
398
|
-
- 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.
|
|
446
|
+
- 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.
|
|
399
447
|
- `ai-wiki/_toolkit/**` and `~/ai-wiki/system/_toolkit/**` are package-managed and may be refreshed by future versions.
|
|
400
448
|
- `ai-wiki/index.md` is a repo-owned map and is not treated as a starter-drift upgrade target by `doctor`.
|
|
401
449
|
- `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.
|
|
402
|
-
- `
|
|
450
|
+
- `.env.aiwiki` stores the current local actor identity in a managed block. It is gitignored and should not be committed.
|
|
451
|
+
- `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`.
|
|
403
452
|
- 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.
|
|
404
453
|
- `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.
|
|
405
454
|
- 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/bin/aiwiki-toolkit
CHANGED
|
Binary file
|
package/package.json
CHANGED