ai-wiki-toolkit-linux-arm64 0.1.36 → 0.1.38
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 +65 -3
- 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.38`.
|
|
5
5
|
Most users should install `ai-wiki-toolkit` instead of using this package directly.
|
|
6
6
|
|
|
7
7
|
---
|
|
@@ -334,6 +334,16 @@ non-interactive shells, pass `--handle your-name` or set `AIWIKI_TOOLKIT_HANDLE`
|
|
|
334
334
|
|
|
335
335
|
The tool works best when `git user.name` and `git user.email` are configured first.
|
|
336
336
|
|
|
337
|
+
For stronger trial/error capture, configure your agent runner to call the post-turn capture command
|
|
338
|
+
after completed AI Wiki write-back turns:
|
|
339
|
+
|
|
340
|
+
```bash
|
|
341
|
+
aiwiki-toolkit source-incident capture-post-turn --apply
|
|
342
|
+
```
|
|
343
|
+
|
|
344
|
+
This hook is recommended when your runner supports it, but `install` does not enable hooks
|
|
345
|
+
automatically or mutate agent runtime configuration.
|
|
346
|
+
|
|
337
347
|
If package-owned repo-local skill files already exist under `.agents/skills/ai-wiki-*`, the installer refreshes them from the current package so new workflow and footer contracts propagate on upgrade. Because these files live in git, local customizations remain visible in `git diff` after running `install`.
|
|
338
348
|
|
|
339
349
|
`init` remains as a backward-compatible alias for `install`. The actual scaffold creation does not happen at package install time; it happens when you run `aiwiki-toolkit install` or `aiwiki-toolkit init` inside a git repository.
|
|
@@ -356,6 +366,55 @@ This appends to the user-owned `ai-wiki/metrics/reuse-events/<handle>.jsonl` sha
|
|
|
356
366
|
|
|
357
367
|
For post-task diagnosis, reuse events can also carry optional provenance such as `--session-id`, `--source-session-id`, `--source-task-id`, `--consulted-order`, `--signal-status candidate`, `--not-helpful-reason superseded_by_later_doc`, `--resolved-by-doc-id`, and `--superseded-by-doc-id`. Candidate not-helpful signals are review hints; confirmed outcomes still require explicit human or agent judgment.
|
|
358
368
|
|
|
369
|
+
When a reused memory came from a real earlier incident, record the original trial/error acquisition cost separately from `--saved-seconds`:
|
|
370
|
+
|
|
371
|
+
```bash
|
|
372
|
+
aiwiki-toolkit record-reuse \
|
|
373
|
+
--doc-id problems/retry-loop \
|
|
374
|
+
--task-id followup-using-memory \
|
|
375
|
+
--retrieval-mode lookup \
|
|
376
|
+
--evidence-mode explicit \
|
|
377
|
+
--reuse-outcome resolved \
|
|
378
|
+
--reuse-effect avoided_retry \
|
|
379
|
+
--source-task-id original-retry-loop \
|
|
380
|
+
--source-incident-seconds 780 \
|
|
381
|
+
--source-incident-source manual \
|
|
382
|
+
--source-incident-note "Failed attempt plus correction turn."
|
|
383
|
+
```
|
|
384
|
+
|
|
385
|
+
If the source incident was a local Codex session, `record-reuse` can derive the active-turn estimate from `task_complete.duration_ms` plus timed `turn_aborted.duration_ms` records:
|
|
386
|
+
|
|
387
|
+
```bash
|
|
388
|
+
aiwiki-toolkit record-reuse \
|
|
389
|
+
--doc-id problems/retry-loop \
|
|
390
|
+
--task-id followup-using-memory \
|
|
391
|
+
--retrieval-mode lookup \
|
|
392
|
+
--evidence-mode explicit \
|
|
393
|
+
--reuse-outcome resolved \
|
|
394
|
+
--source-session-id 019dcf06-example \
|
|
395
|
+
--source-incident-from-codex-session
|
|
396
|
+
```
|
|
397
|
+
|
|
398
|
+
Diagnostics and `eval impact discover` report this as `source_incident_timing`. Treat it as source active-turn context for research, not as exact human time saved or a formal no-AI-wiki baseline.
|
|
399
|
+
|
|
400
|
+
For older memories where the original `record-reuse` event did not include source timing, backfill a separate evidence ledger from local Codex write-back footers:
|
|
401
|
+
|
|
402
|
+
```bash
|
|
403
|
+
aiwiki-toolkit source-incident backfill-writeback \
|
|
404
|
+
--writeback-path ai-wiki/problems/retry-loop.md \
|
|
405
|
+
--apply
|
|
406
|
+
```
|
|
407
|
+
|
|
408
|
+
This scans local `~/.codex/sessions` for the first `AI Wiki Write-Back Path:` footer in a session whose `cwd` matches the current repository, counts active `task_complete.duration_ms` plus timed `turn_aborted.duration_ms` rows from the current user task start through that first write-back turn, and appends the result to `ai-wiki/metrics/source-incidents/<handle>.jsonl`. It does not mutate historical reuse events. Omit `--apply` for a dry run, or pass `--doc-id`/`--writeback-path` to scope the backfill.
|
|
409
|
+
|
|
410
|
+
For a post-turn hook or wrapper, capture only the latest completed write-back turn for the current repo:
|
|
411
|
+
|
|
412
|
+
```bash
|
|
413
|
+
aiwiki-toolkit source-incident capture-post-turn --apply
|
|
414
|
+
```
|
|
415
|
+
|
|
416
|
+
This command is idempotent. If the latest write-back was already captured, it reports `skipped_existing` instead of appending another row. A runner that knows the Codex session id can pass `--session-id <id>` to avoid scanning all local session files.
|
|
417
|
+
|
|
359
418
|
Only record user-owned AI wiki knowledge docs with `record-reuse`.
|
|
360
419
|
|
|
361
420
|
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.
|
|
@@ -405,10 +464,11 @@ aiwiki-toolkit record-reuse-check \
|
|
|
405
464
|
|
|
406
465
|
This appends to the user-owned `ai-wiki/metrics/task-checks/<handle>.jsonl` shard and refreshes the handle-scoped generated views under `ai-wiki/_toolkit/metrics/by-handle/<handle>/`. The installer ignores both the shard and the generated aggregate views by default so these telemetry updates stay local.
|
|
407
466
|
|
|
408
|
-
|
|
467
|
+
The local metrics logs are sharded by handle under:
|
|
409
468
|
|
|
410
469
|
- `ai-wiki/metrics/reuse-events/<handle>.jsonl`
|
|
411
470
|
- `ai-wiki/metrics/task-checks/<handle>.jsonl`
|
|
471
|
+
- `ai-wiki/metrics/source-incidents/<handle>.jsonl`
|
|
412
472
|
|
|
413
473
|
These logs are intended as local telemetry by default, not merge-heavy source files.
|
|
414
474
|
|
|
@@ -432,7 +492,9 @@ Use `--focus trial-error` to generate a focused trial/error reduction report fro
|
|
|
432
492
|
AI wiki evidence. It summarizes material effects such as `avoided_retry`,
|
|
433
493
|
`blocked_wrong_path`, `changed_plan`, and `faster_resolution`, separates missed or repeated issue
|
|
434
494
|
signals from unproven wiki use, and lists replay candidates that still need source incident
|
|
435
|
-
artifacts before becoming formal impact-eval families.
|
|
495
|
+
artifacts before becoming formal impact-eval families. Source incident timing can come either from
|
|
496
|
+
new `record-reuse` provenance fields or from the separate `source-incident backfill-writeback`
|
|
497
|
+
ledger.
|
|
436
498
|
|
|
437
499
|
To turn diagnostics and handle-local drafts into a human-reviewable consolidation queue:
|
|
438
500
|
|
package/bin/aiwiki-toolkit
CHANGED
|
Binary file
|
package/package.json
CHANGED