ai-wiki-toolkit-linux-arm64 0.1.36 → 0.1.37
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 +32 -1
- 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.37`.
|
|
5
5
|
Most users should install `ai-wiki-toolkit` instead of using this package directly.
|
|
6
6
|
|
|
7
7
|
---
|
|
@@ -356,6 +356,37 @@ This appends to the user-owned `ai-wiki/metrics/reuse-events/<handle>.jsonl` sha
|
|
|
356
356
|
|
|
357
357
|
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
358
|
|
|
359
|
+
When a reused memory came from a real earlier incident, record the original trial/error acquisition cost separately from `--saved-seconds`:
|
|
360
|
+
|
|
361
|
+
```bash
|
|
362
|
+
aiwiki-toolkit record-reuse \
|
|
363
|
+
--doc-id problems/retry-loop \
|
|
364
|
+
--task-id followup-using-memory \
|
|
365
|
+
--retrieval-mode lookup \
|
|
366
|
+
--evidence-mode explicit \
|
|
367
|
+
--reuse-outcome resolved \
|
|
368
|
+
--reuse-effect avoided_retry \
|
|
369
|
+
--source-task-id original-retry-loop \
|
|
370
|
+
--source-incident-seconds 780 \
|
|
371
|
+
--source-incident-source manual \
|
|
372
|
+
--source-incident-note "Failed attempt plus correction turn."
|
|
373
|
+
```
|
|
374
|
+
|
|
375
|
+
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:
|
|
376
|
+
|
|
377
|
+
```bash
|
|
378
|
+
aiwiki-toolkit record-reuse \
|
|
379
|
+
--doc-id problems/retry-loop \
|
|
380
|
+
--task-id followup-using-memory \
|
|
381
|
+
--retrieval-mode lookup \
|
|
382
|
+
--evidence-mode explicit \
|
|
383
|
+
--reuse-outcome resolved \
|
|
384
|
+
--source-session-id 019dcf06-example \
|
|
385
|
+
--source-incident-from-codex-session
|
|
386
|
+
```
|
|
387
|
+
|
|
388
|
+
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.
|
|
389
|
+
|
|
359
390
|
Only record user-owned AI wiki knowledge docs with `record-reuse`.
|
|
360
391
|
|
|
361
392
|
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.
|
package/bin/aiwiki-toolkit
CHANGED
|
Binary file
|
package/package.json
CHANGED