@rmyndharis/aimhooman 0.1.4 → 0.1.5

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
             "name": "aimhooman",
             "source": "./",
             "description": "Keeps AI session files, secrets, and unwanted attribution out at the agent and Git boundary.",
-            "version": "0.1.4",
+            "version": "0.1.5",
             "license": "MIT",
             "keywords": [
                 "git",

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name": "aimhooman",
-    "version": "0.1.4",
+    "version": "0.1.5",
     "description": "AI works. Hoomans ship. Keeps AI session files, secrets, and unwanted attribution out at the agent and Git boundary.",
     "author": {
         "name": "aimhooman"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name": "aimhooman",
-    "version": "0.1.4",
+    "version": "0.1.5",
     "description": "AI works. Hoomans ship. Keeps AI session files, secrets, and unwanted attribution out at the agent and Git boundary.",
     "author": {
         "name": "aimhooman maintainers",

package/CHANGELOG.md

@@ -5,6 +5,51 @@ All notable changes to this project are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.5] - 2026-07-18
+
+### Fixed
+
+- AWS's own published example key no longer blocks a commit. 0.1.4 began matching bare
+  `AKIA…`/`ASIA…` access key IDs, which also matched `AKIAIOSFODNN7EXAMPLE` — the value AWS
+  prints in its own documentation, and one that lands in READMEs, Terraform samples, and test
+  fixtures. Because the rule's category is `secret`, neither a rule allow nor a plain path
+  allow is accepted, so a documentation example became an unconditional block on every profile
+  with only a per-file escape. Every AWS example key ends in `EXAMPLE`, so the pattern now
+  excludes that suffix and keeps blocking real keys. Path scoping was deliberately not used:
+  excluding `docs/` or `tests/` from secret scanning would hide genuine keys in the places they
+  most often leak.
+- `uninstall --purge-state` no longer leaves a backup behind in a linked worktree. Git writes
+  the commit message file into the per-worktree Git directory, so 0.1.4's sweep — which looked
+  only in the common directory — printed "state purged" with `COMMIT_EDITMSG.aimhooman-bak`
+  still on disk. Uninstall disarms every worktree at once, so it now sweeps the main Git
+  directory and each linked one, and matches the `.aimhooman-bak` suffix so a backup left by a
+  merge goes with it.
+- A plain `uninstall` keeps the attribution backup. It printed "state kept" and then deleted
+  the one file holding the lines stripped from the last commit message. Only `--purge-state`,
+  which promises to remove everything, takes it now.
+- Sweeping an empty lock queue can no longer stop a concurrent `aimhooman init`. Between its
+  `mkdir` and its first publication a lock contender owns no file in the queue, so the sweep
+  saw an empty directory and removed it, and the contender then failed on a bare `ENOENT`. The
+  window is wide enough to lose because building the candidate probes the process identity,
+  which spawns `ps` on macOS and BSD. Publication now recreates the directory and retries once.
+- The unstage summary no longer claims the files were "kept in your working tree". That is
+  false when a path was staged and then deleted before the commit, and when a staged deletion
+  is unstaged — the file is absent either way, though aimhooman never removed it. Unstaging
+  only ever touches the index, so the note says that instead of guessing where the file is.
+
+### Changed
+
+- An ordinary commit no longer pays a Node cold start for a phase that does nothing. Git fires
+  `reference-transaction` twice per commit, and `refcheck` returns immediately for `committed`
+  and `aborted`, so the dispatcher now short-circuits those phases in the shell — after the
+  chained-hook call, so a chained hook still sees every phase. Measured locally, an ordinary
+  commit drops from about 870ms to about 710ms. The `prepared` scan, and the `--no-verify`
+  backstop that rides on it, are unchanged. A repository installed with an earlier release
+  keeps a valid dispatcher; re-run `aimhooman init` to pick up the faster one.
+- The attribution backup no longer lingers indefinitely. `commit-msg` clears the previous run's
+  backup before it may write its own, so at most one exists at a time and a later clean commit
+  leaves none. The recovery window is now until your next commit rather than unbounded.
+
 ## [0.1.4] - 2026-07-18
 
 ### Fixed

package/README.md

@@ -9,7 +9,7 @@
 
 <p align="center">
   <img src="https://img.shields.io/github/actions/workflow/status/rmyndharis/aimhooman/test.yml?branch=main&label=CI" alt="CI">
-  <img src="https://img.shields.io/badge/version-v0.1.4-blue" alt="v0.1.4">
+  <img src="https://img.shields.io/badge/version-v0.1.5-blue" alt="v0.1.5">
   <img src="https://img.shields.io/badge/node-%E2%89%A522.8-339933?logo=node.js&logoColor=white" alt="Node 22.8+">
   <img src="https://img.shields.io/badge/dependencies-0-brightgreen" alt="Zero dependencies">
   <img src="https://img.shields.io/badge/license-MIT-111111" alt="MIT">

package/bin/aimhooman.mjs

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 import { execFileSync } from 'node:child_process';
-import { chmodSync, lstatSync, readFileSync, rmdirSync, rmSync } from 'node:fs';
+import { chmodSync, lstatSync, readdirSync, readFileSync, rmdirSync, rmSync } from 'node:fs';
 import { join } from 'node:path';
 import { fileURLToPath } from 'node:url';
 import { GIT_TIMEOUT_MS } from '../src/git-environment.mjs';
@@ -372,7 +372,7 @@ function cmdPrecommit(args) {
         emptied = stagedBefore !== null
             && stagedBefore.every((path) => unstageTargets.has(path));
         process.stderr.write(
-            `aimhooman: unstaged ${paths.length} file(s) from this commit: ${paths.map(visible).join(', ')}${emptied ? ' — nothing else was staged, so the commit is stopped rather than left empty' : ''}\n`
+            `aimhooman: unstaged ${paths.length} file(s) from this commit: ${paths.map(visible).join(', ')} (index only; nothing on disk was deleted)${emptied ? ' — nothing else was staged, so the commit is stopped rather than left empty' : ''}\n`
         );
     } catch (e) {
         process.stderr.write(
@@ -409,6 +409,10 @@ function cmdCommitmsg(args) {
     const file = positionals[0];
     const repo = tryRepo();
     if (!repo) { console.error('aimhooman: not a git repository'); return 30; }
+    // A .aimhooman-bak from an earlier commit went stale the moment that commit
+    // finished, and git reuses this message path. Clear the previous run's backup
+    // now, before this run may write its own, so at most one ever lingers.
+    try { rmSync(`${file}.aimhooman-bak`, { force: true }); } catch { /* best effort */ }
     // Frictionless profiles (clean/compliance) never cancel a commit merely
     // because the message file cannot be read; only strict fails closed.
     let hookProfile = 'clean';
@@ -1696,9 +1700,29 @@ function cmdUninstall(args) {
     ]) {
         try { rmdirSync(queue); } catch { /* held by another aimhooman, or already gone */ }
     }
-    // A one-commit-ago attribution backup that git's next COMMIT_EDITMSG makes stale.
-    try { rmSync(join(repo.commonDir, 'COMMIT_EDITMSG.aimhooman-bak'), { force: true }); }
-    catch { /* nothing to remove */ }
+    // The attribution backup is the user's only copy of the lines stripped from
+    // their last message — commit-msg already clears the previous one, so what
+    // survives here is current, not stale. A plain uninstall says "state kept"
+    // and must not delete it; only --purge-state, which promises to remove
+    // everything, sweeps it. Git names the message file per operation
+    // (COMMIT_EDITMSG, MERGE_MSG, ...) and the backup inherits that name, so
+    // match the suffix rather than one filename. It lands beside that file, in
+    // the per-worktree git directory rather than the common one, and uninstall
+    // disarms every worktree at once — so cover the main one and each linked.
+    if (purge) {
+        const messageDirs = [repo.commonDir];
+        try {
+            const linked = join(repo.commonDir, 'worktrees');
+            for (const name of readdirSync(linked)) messageDirs.push(join(linked, name));
+        } catch { /* no linked worktrees */ }
+        for (const dir of messageDirs) {
+            try {
+                for (const name of readdirSync(dir)) {
+                    if (name.endsWith('.aimhooman-bak')) rmSync(join(dir, name), { force: true });
+                }
+            } catch { /* directory missing or unreadable */ }
+        }
+    }
     return exitStatus;
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@rmyndharis/aimhooman",
-    "version": "0.1.4",
+    "version": "0.1.5",
     "description": "AI works. Hoomans ship. Keep AI session files, secrets, and attribution out of your commits.",
     "homepage": "https://github.com/rmyndharis/aimhooman#readme",
     "repository": {

package/rules/secrets.json

@@ -53,7 +53,7 @@
         "match": {
             "content": [
                 "(?i)\\baws_(?:secret_access_key|session_token)\\b\\s*[:=]\\s*[\\\"']?[A-Za-z0-9/+=]{32,}(?![A-Za-z0-9/+=])",
-                "\\b(?:AKIA|ASIA)[A-Z0-9]{16}\\b"
+                "\\b(?:AKIA|ASIA)(?![A-Z0-9]{9}EXAMPLE\\b)[A-Z0-9]{16}\\b"
             ]
         },
         "actions": {

package/src/atomic-write.mjs

@@ -259,18 +259,34 @@ export function withLock(lockPath, fn, options = {}) {
     let held = false;
     let published = false;
     let primaryError = null;
+    // Between the mkdir above and the first publication below this contender owns
+    // no file in the queue, so a concurrent cleanup that removes empty queue
+    // directories — `aimhooman uninstall` sweeps them — can delete it out from
+    // under us. The gap is wide enough to lose: building the candidate probes the
+    // process identity, which spawns `ps` on macOS and BSD. Recreate and retry
+    // once rather than failing the caller with a bare ENOENT. Once a candidate is
+    // published the directory is no longer empty, so no cleanup can remove it.
+    const publish = () => {
+        try {
+            publishCandidate(candidatePath, candidate, options.candidateOperations);
+        } catch (error) {
+            if (error?.code !== 'ENOENT') throw error;
+            mkdirSync(queueDir, { recursive: true });
+            publishCandidate(candidatePath, candidate, options.candidateOperations);
+        }
+    };
     try {
         // Own the UUID pathname before publication begins. If the rename lands
         // but its directory fsync fails, finally still removes the candidate;
         // unlinking ENOENT is harmless when publication failed earlier.
         published = true;
-        publishCandidate(candidatePath, candidate, options.candidateOperations);
+        publish();
         const observed = queueCandidates(queueDir, staleMs);
         candidate.ticket = observed.reduce((maximum, peer) => (
             peer.ticket === null ? maximum : Math.max(maximum, peer.ticket)
         ), 0) + 1;
         candidate.choosing = false;
-        publishCandidate(candidatePath, candidate, options.candidateOperations);
+        publish();
 
         for (let attempt = 0; attempt < retries; attempt += 1) {
             // A file at the pre-queue lock path may belong to a concurrently

package/src/githooks.mjs

@@ -642,6 +642,14 @@ function hookScript(name, cmd, cliPath, chainedPath) {
     const aimInvocation = name === 'reference-transaction'
         ? `printf '%s\\n' "$AIMHOOMAN_REF_UPDATES" | run_aimhooman ${aimCommand} || exit $?`
         : `run_aimhooman ${aimCommand} || exit $?`;
+    // committed/aborted fire only after refs are locked in, and refcheck can do
+    // nothing but return 0 for them (see cmdRefcheck). Short-circuit in the shell
+    // so an ordinary commit no longer pays a Node cold start for the committed
+    // phase. Placed after the chained-hook call, so a chained hook still sees
+    // every phase.
+    const phaseShortCircuit = name === 'reference-transaction'
+        ? 'case "$1" in committed|aborted) exit 0 ;; esac\n'
+        : '';
     const template = `#!/bin/sh -p
 ${MARKER} (${name})
 # aimhooman-hook-version: ${HOOK_FORMAT_VERSION}
@@ -691,7 +699,7 @@ fi
 if [ -x "$CHAINED" ]; then
 ${chainedInvocation}
 fi
-${aimInvocation}
+${phaseShortCircuit}${aimInvocation}
 `;
     const fingerprint = hookFingerprint(template);
     return template.replace(FINGERPRINT_PLACEHOLDER, fingerprint);