@akasecurity/ai-tc-antigravity 0.9.13 → 0.9.14
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/package.json +6 -6
- package/plugin.json +1 -1
- package/scripts/apply-suppressions.js +2444 -1022
- package/scripts/backfill.js +2474 -1027
- package/scripts/content-retention.js +2360 -982
- package/scripts/filescan.js +2470 -1029
- package/scripts/firstrun.js +2411 -997
- package/scripts/history-sync.js +2360 -982
- package/scripts/intro.js +2197 -931
- package/scripts/onboard.js +2366 -992
- package/scripts/post-tool-use.js +2232 -951
- package/scripts/pre-invocation.js +2422 -1008
- package/scripts/pre-tool-use.js +2441 -1020
- package/scripts/query.js +2410 -996
- package/scripts/reconcile.js +2417 -1003
- package/scripts/remediate.js +2443 -1029
- package/scripts/scan-worker.js +1754 -871
- package/scripts/start-light.js +2195 -929
- package/scripts/stop.js +2232 -951
- package/scripts/sync.js +2472 -1031
- package/skills/setup/SKILL.md +27 -0
package/skills/setup/SKILL.md
CHANGED
|
@@ -923,6 +923,33 @@ so each command falls back to the default CLI install location
|
|
|
923
923
|
installed somewhere else, edit `hooks.json` and replace `${PLUGIN_ROOT:-…}` with
|
|
924
924
|
the absolute path to the plugin directory.
|
|
925
925
|
|
|
926
|
+
**On an Antigravity older than 1.1.10, the `Stop` hook never runs**, and that is
|
|
927
|
+
the host's own behaviour rather than a misconfiguration: hooks declared in
|
|
928
|
+
`hooks.json` used to be ordered behind the built-in termination checks, so a
|
|
929
|
+
`Stop` entry loaded and was never reached. 1.1.10 moved them in front. The
|
|
930
|
+
host's own `/hooks` listing did not show it either — that command omitted
|
|
931
|
+
plugin-bundled hooks, which AKA's are, until 1.2.3. What it costs is narrower
|
|
932
|
+
than losing the event sounds — AKA's `Stop` hook triggers the background pass
|
|
933
|
+
that reads the transcript, and `PreInvocation` and `PostToolUse` trigger it too,
|
|
934
|
+
so capture still happens and what is missing is the trigger that reconciles the
|
|
935
|
+
tail of a turn once nothing further is coming. On an older host that tail waits
|
|
936
|
+
for the next turn — and if the user closes the session after that turn there is
|
|
937
|
+
no next turn, so it waits until they reopen that conversation or a history sweep
|
|
938
|
+
picks it up — `node "${PLUGIN_ROOT}/scripts/backfill.js"`, the plain
|
|
939
|
+
human-output form of the scan this skill runs during calibration. It covers the
|
|
940
|
+
last 30 days and needs the historical-read grant, so it is not a fallback for
|
|
941
|
+
a user who declined that; do **not** reach for `--triage` here, which is the
|
|
942
|
+
machine JSONL channel for the judge pipeline: it carries `rawMatch` and its
|
|
943
|
+
surrounding context unmasked, and its own contract requires a consumer to run
|
|
944
|
+
the raw-egress guardrails before either reaches a persisted row, a log, or a
|
|
945
|
+
rendered surface.
|
|
946
|
+
Check there first if a recent session looks like it is missing its last
|
|
947
|
+
exchange. **AKA cannot detect this and will not warn about it**: this host tells
|
|
948
|
+
a session nothing about its own version — no payload field, no transcript
|
|
949
|
+
record, no environment variable carries one — so if a user asks why the last
|
|
950
|
+
stretch of a turn showed up late, ask for their `agy` version rather than
|
|
951
|
+
expecting AKA to have flagged it.
|
|
952
|
+
|
|
926
953
|
**The reversible secret vault is not wired for Antigravity sessions**, so this
|
|
927
954
|
wizard does not offer the vault-consent step: everything AKA redacts here is
|
|
928
955
|
one-way (the safe direction), and nothing this plugin captures is ever vaulted —
|