@rmyndharis/aimhooman 0.1.3 → 0.1.4

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.3",
+            "version": "0.1.4",
             "license": "MIT",
             "keywords": [
                 "git",

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name": "aimhooman",
-    "version": "0.1.3",
+    "version": "0.1.4",
     "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.3",
+    "version": "0.1.4",
     "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,25 @@ 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.4] - 2026-07-18
+
+### Fixed
+
+- Uninstall no longer leaves aimhooman artifacts in `.git`. Every atomic write takes a
+  lock whose `<lock>.queue` directory was created but never removed — the release path
+  only unlinked its own candidate file — and `--purge-state` cleared just the state
+  directory. So `.git` kept the queue directories and the `COMMIT_EDITMSG.aimhooman-bak`
+  attribution backup while the command printed "state purged". Uninstall now sweeps this
+  residue once the lifecycle lock releases; `rmdirSync` removes only an empty directory,
+  so a concurrent contender's queue is never touched, and the lifecycle queue is removable
+  precisely because its own lock has already released. A plain uninstall keeps policy
+  state and drops the operational residue; `--purge-state` leaves no aimhooman fingerprints.
+- A bare AWS access key ID is now detected. `secret.aws-key-content` fired only when an
+  `aws_secret_access_key` or `aws_session_token` name sat beside the value, so an
+  `AKIA…`/`ASIA…` access key ID committed on its own passed clean. The rule now matches the
+  access-key-ID prefixes directly — the fixed-prefix, highest-confidence AWS indicator. The
+  16-character body and word boundaries keep short lookalikes such as `AKIA123` from matching.
+
 ## [0.1.3] - 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.3-blue" alt="v0.1.3">
+  <img src="https://img.shields.io/badge/version-v0.1.4-blue" alt="v0.1.4">
   <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, rmSync } from 'node:fs';
+import { chmodSync, lstatSync, 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';
@@ -20,7 +20,7 @@ import {
 } from '../src/gitx.mjs';
 import { loadConfig, loadOverrides, loadProjectPolicy, normalizeOverrideTarget, saveConfig, saveOverrides } from '../src/state.mjs';
 import { applyExclude, inspectExclude, patternsForRules, removeExclude } from '../src/exclude.mjs';
-import { hookDiagnostics, installHooks, installGlobalHooks, uninstallGlobalHooks, globalHooksDir, installedHooks, remainingDispatchers, uninstallHooks, unrestoredChainedBackups } from '../src/githooks.mjs';
+import { effectiveHooksDir, hookDiagnostics, installHooks, installGlobalHooks, uninstallGlobalHooks, globalHooksDir, installedHooks, remainingDispatchers, uninstallHooks, unrestoredChainedBackups } from '../src/githooks.mjs';
 import { ArgumentError, parseArguments } from '../src/args.mjs';
 import { engineForPolicy, scanGitTarget, scanMessage } from '../src/scan-target.mjs';
 import { resolvePolicy } from '../src/policy-resolver.mjs';
@@ -1615,7 +1615,8 @@ function cmdUninstall(args) {
         console.error('aimhooman: not a git repository');
         return 30;
     }
-    return withLock(join(repo.commonDir, 'aimhooman-lifecycle.lock'), () => {
+    const lifecycleLock = join(repo.commonDir, 'aimhooman-lifecycle.lock');
+    const exitStatus = withLock(lifecycleLock, () => {
     const rep = uninstallHooks(repo);
     // The irreversible work is already done above, and the report is still
     // below. A throw from here unwound past all of it, so a damaged marker was
@@ -1683,6 +1684,22 @@ function cmdUninstall(args) {
     // the uninstall is genuinely incomplete and 30 is the honest answer.
     return remaining.length || rep.failures?.length || unrestored.length || excludeFailure ? 30 : 0;
     }, LIFECYCLE_LOCK_OPTIONS);
+    // Sweep the operational residue the guard authored in .git, so uninstall leaves
+    // no aimhooman fingerprints behind — the same tooling residue this tool exists
+    // to remove. rmdirSync deletes only an empty directory, so a live contender's
+    // queue is never touched; the lifecycle queue becomes removable only now, after
+    // its own lock above has released.
+    for (const queue of [
+        `${lifecycleLock}.queue`,
+        `${repo.excludeFile}.aimhooman.lock.queue`,
+        join(effectiveHooksDir(repo), '.aimhooman-hooks.lock.queue'),
+    ]) {
+        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 */ }
+    return exitStatus;
 }
 
 function usage() {

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@rmyndharis/aimhooman",
-    "version": "0.1.3",
+    "version": "0.1.4",
     "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

@@ -45,14 +45,15 @@
     },
     {
         "id": "secret.aws-key-content",
-        "version": 1,
+        "version": 2,
         "provider": "aws",
         "category": "secret",
         "confidence": "high",
         "kind": "code",
         "match": {
             "content": [
-                "(?i)\\baws_(?:secret_access_key|session_token)\\b\\s*[:=]\\s*[\\\"']?[A-Za-z0-9/+=]{32,}(?![A-Za-z0-9/+=])"
+                "(?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"
             ]
         },
         "actions": {

package/src/githooks.mjs

@@ -124,7 +124,7 @@ function canonicalPath(path) {
 
 // Ask Git for the path it actually uses. In a linked worktree this resolves to
 // the common repository hooks directory, not <gitDir>/hooks.
-function effectiveHooksDir(repo) {
+export function effectiveHooksDir(repo) {
     try {
         return execFileSync(
             'git',