kata-cli 0.8.0__tar.gz → 0.9.2__tar.gz

{kata_cli-0.8.0 → kata_cli-0.9.2}/.claude/skills/cicd/SKILL.md

@@ -9,7 +9,7 @@ description: >
   review feedback, polling CI status, or the user says "create PR",
   "review comments", "address feedback", "resolve threads". Renamed
   from `pr-review` in steward 0.7.0; rebased on agex in 0.12.0.
-  seer-cli divergence: `scripts/portability-lint.sh` drops the GNU-only
+  antoine divergence: `scripts/portability-lint.sh` drops the GNU-only
   `xargs -r` flag for BSD/macOS portability — see `docs/skill-sources.md`.
 ---
 

{kata_cli-0.8.0 → kata_cli-0.9.2}/.claude/skills/cicd/scripts/portability-lint.sh

@@ -21,7 +21,7 @@ esac
 [ -z "$files" ] && { echo "(no files to check)"; exit 0; }
 
 # ----- Check 1: hard-coded /home/<user>/... paths -----
-# seer-cli divergence: `xargs -r` is GNU-only and fails on BSD/macOS xargs.
+# antoine divergence: `xargs -r` is GNU-only and fails on BSD/macOS xargs.
 # `$files` is already guarded non-empty above, so `-r` is redundant — dropped.
 hits1=$(echo "$files" | xargs grep -nE '/home/[a-z][a-z0-9_-]+/' 2>/dev/null || true)
 
@@ -31,7 +31,7 @@ hits1=$(echo "$files" | xargs grep -nE '/home/[a-z][a-z0-9_-]+/' 2>/dev/null ||
 #   - ~/.culture/                     Culture mesh data this skill is supposed to read
 md_yaml=$(echo "$files" | grep -E '\.(md|ya?ml|toml|json|jsonc)$' || true)
 if [ -n "$md_yaml" ]; then
-    # seer-cli divergence: `xargs -r` is GNU-only; `$md_yaml` is guarded
+    # antoine divergence: `xargs -r` is GNU-only; `$md_yaml` is guarded
     # non-empty by the enclosing `if`, so `-r` is redundant — dropped.
     hits2=$(echo "$md_yaml" | xargs grep -nE '~/\.[A-Za-z]' 2>/dev/null \
         | grep -vE '~/\.claude/skills/[^[:space:]"]+/scripts/' \

{kata_cli-0.8.0 → kata_cli-0.9.2}/.claude/skills/code-lookup/SKILL.md

@@ -96,5 +96,5 @@ One call each, no re-grepping.
 
 ## Engine
 
-`seer/lookup/` — `python -m seer <verb> …`. Each shell wrapper is a
+`antoine/lookup/` — `python -m antoine <verb> …`. Each shell wrapper is a
 one-liner; the agent-facing contract is the verb and its flags.

{kata_cli-0.8.0 → kata_cli-0.9.2}/.claude/skills/code-lookup/scripts/classify.sh

@@ -1,4 +1,4 @@
 #!/usr/bin/env bash
 set -euo pipefail
 PROJECT_ROOT="$(cd "$(dirname "$0")/../../../.." && pwd)"
-exec uv run --directory "$PROJECT_ROOT" python -m seer classify "$@"
+exec uv run --directory "$PROJECT_ROOT" python -m antoine classify "$@"

{kata_cli-0.8.0 → kata_cli-0.9.2}/.claude/skills/code-lookup/scripts/grep.sh

@@ -1,4 +1,4 @@
 #!/usr/bin/env bash
 set -euo pipefail
 PROJECT_ROOT="$(cd "$(dirname "$0")/../../../.." && pwd)"
-exec uv run --directory "$PROJECT_ROOT" python -m seer grep "$@"
+exec uv run --directory "$PROJECT_ROOT" python -m antoine grep "$@"

{kata_cli-0.8.0 → kata_cli-0.9.2}/.claude/skills/code-lookup/scripts/recent.sh

@@ -1,4 +1,4 @@
 #!/usr/bin/env bash
 set -euo pipefail
 PROJECT_ROOT="$(cd "$(dirname "$0")/../../../.." && pwd)"
-exec uv run --directory "$PROJECT_ROOT" python -m seer recent "$@"
+exec uv run --directory "$PROJECT_ROOT" python -m antoine recent "$@"

{kata_cli-0.8.0 → kata_cli-0.9.2}/.claude/skills/eval/SKILL.md

@@ -7,8 +7,8 @@ description: >
   dispatches + records, then `summarize` + commit to the round's
   accumulator file. Use when the user says "run eval set", "eval",
   "scripts-eval", "round-NN set", or asks to execute a row of the corpus.
-  Three arms: A (banned — rider forbids the seer skills), B (directed
-  — rider instructs use of seer skills), C (organic — rider permits
+  Three arms: A (banned — rider forbids the antoine skills), B (directed
+  — rider instructs use of antoine skills), C (organic — rider permits
   but doesn't direct). Two judge pairs: A-vs-B ("do the skills help
   when used") and A-vs-C ("do the skills get adopted organically").
   `judge prepare --pair AB|AC` selects the pair.
@@ -28,17 +28,17 @@ operator procedure that sequences them per session.
 Before doing anything, verify the user's intent matches the session
 state. Stop and ask if any of these hold:
 
-- `env | grep SEER_EVAL_RUN_ID` is empty → the harness hooks no-op, no
+- `env | grep ANTOINE_EVAL_RUN_ID` is empty → the harness hooks no-op, no
   metrics get captured. Operator needs to re-launch with the env vars
   exported.
-- `SEER_EVAL_ARM` is set to anything other than `A`, `B`, or `C` → bad config.
+- `ANTOINE_EVAL_ARM` is set to anything other than `A`, `B`, or `C` → bad config.
 - User says "do arm C" but the matching arm-A cells don't exist on
-  disk under `experiments/scripts_eval/results/$SEER_EVAL_RUN_ID/arm-A/`
+  disk under `experiments/scripts_eval/results/$ANTOINE_EVAL_RUN_ID/arm-A/`
   → arm A must complete first; there's nothing to pair against.
 
 All three arms run with `repo-map` and `code-lookup` enabled on disk.
 Arm-A's constraint is **verbal** — the rider in the dispatched prompt
-is the sole guard against the subagent using the seer skills. Do not
+is the sole guard against the subagent using the antoine skills. Do not
 edit the rider; copy it verbatim. (Earlier versions of this skill
 physically moved `.claude/skills/repo-map/` aside for arm A as
 defense-in-depth; that step was dropped because the rider proved
@@ -46,13 +46,13 @@ sufficient and the move-aside dance made operator setup brittle.)
 
 Three arms, three questions they answer:
 
-- **A (banned)** — verbal rider forbids both seer skills. Establishes
+- **A (banned)** — verbal rider forbids both antoine skills. Establishes
   the "without the new skills" baseline.
 - **B (directed)** — verbal rider instructs the subagent to use the
-  seer skills where applicable. Establishes the "with the new skills,
+  antoine skills where applicable. Establishes the "with the new skills,
   when actually used" upper bound.
 - **C (organic)** — verbal rider permits but does not direct use of
-  the seer skills. Measures organic adoption rate.
+  the antoine skills. Measures organic adoption rate.
 
 A-vs-B is the primary "do the skills help?" comparison; A-vs-C is the
 adoption canary. The judge supports both pairs via the `--pair` flag.
@@ -60,7 +60,7 @@ adoption canary. The judge supports both pairs via the `--pair` flag.
 ## Preflight (every session)
 
 ```bash
-env | grep -E "^SEER_EVAL_(RUN_ID|ARM)="
+env | grep -E "^ANTOINE_EVAL_(RUN_ID|ARM)="
 # expect both set to the intended round / arm
 ```
 
@@ -68,11 +68,11 @@ If unset, export them in your shell before launching `claude`:
 
 ```bash
 # arm-A session (banned):
-export SEER_EVAL_RUN_ID=2026-05-NN-round-XX SEER_EVAL_ARM=A
+export ANTOINE_EVAL_RUN_ID=2026-05-NN-round-XX ANTOINE_EVAL_ARM=A
 # arm-B session (directed):
-export SEER_EVAL_RUN_ID=2026-05-NN-round-XX SEER_EVAL_ARM=B
+export ANTOINE_EVAL_RUN_ID=2026-05-NN-round-XX ANTOINE_EVAL_ARM=B
 # arm-C session (organic):
-export SEER_EVAL_RUN_ID=2026-05-NN-round-XX SEER_EVAL_ARM=C
+export ANTOINE_EVAL_RUN_ID=2026-05-NN-round-XX ANTOINE_EVAL_ARM=C
 ```
 
 `experiments/scripts_eval/switch-arm.sh A|B|C <run_id>` does the same
@@ -82,7 +82,7 @@ If this is the first set of the run (idempotent, safe to re-run):
 
 ```bash
 uv run --group experiments python -m experiments.scripts_eval.manifest \
-    init --run $SEER_EVAL_RUN_ID
+    init --run $ANTOINE_EVAL_RUN_ID
 ```
 
 ## Arm-A procedure
@@ -99,11 +99,11 @@ uv run --group experiments python -m experiments.scripts_eval.manifest \
    ```text
 
    Constraints (verbatim):
-   - You may NOT use the `repo-map` skill, `python -m seer.repo`,
-     the `seer.repo` Python module, or any `scripts/*.sh` paths under
+   - You may NOT use the `repo-map` skill, `python -m antoine.repo`,
+     the `antoine.repo` Python module, or any `scripts/*.sh` paths under
      `.claude/skills/repo-map/`.
-   - You may NOT use the `code-lookup` skill, the `seer.lookup`
-     Python module, the `seer grep` / `seer recent` / `seer classify`
+   - You may NOT use the `code-lookup` skill, the `antoine.lookup`
+     Python module, the `antoine grep` / `antoine recent` / `antoine classify`
      CLI verbs, or any `scripts/*.sh` paths under
      `.claude/skills/code-lookup/`.
      If you cannot answer without them, say so explicitly and stop.
@@ -121,7 +121,7 @@ uv run --group experiments python -m experiments.scripts_eval.manifest \
 
    ```bash
    TRIAL_ID=$(uv run --group experiments python -m experiments.scripts_eval.trial \
-       start --run $SEER_EVAL_RUN_ID --arm $SEER_EVAL_ARM \
+       start --run $ANTOINE_EVAL_RUN_ID --arm $ANTOINE_EVAL_ARM \
        --target <target> --question <question_id> --trial <n>)
    ```
 
@@ -140,17 +140,17 @@ uv run --group experiments python -m experiments.scripts_eval.manifest \
    ```
 
 6. Confirm the cell JSON appeared under
-   `experiments/scripts_eval/results/$SEER_EVAL_RUN_ID/arm-A/`.
+   `experiments/scripts_eval/results/$ANTOINE_EVAL_RUN_ID/arm-A/`.
 
 **After all 3 trials**, summarize + commit:
 
 ```bash
 uv run --group experiments python -m experiments.scripts_eval.summarize \
-    --run $SEER_EVAL_RUN_ID \
-    --out docs/eval-rounds/$SEER_EVAL_RUN_ID.md
+    --run $ANTOINE_EVAL_RUN_ID \
+    --out docs/eval-rounds/$ANTOINE_EVAL_RUN_ID.md
 
-git add docs/eval-rounds/$SEER_EVAL_RUN_ID.md
-git commit -m "$SEER_EVAL_RUN_ID: arm-A captured for <target>/<question_id> (3 trials)"
+git add docs/eval-rounds/$ANTOINE_EVAL_RUN_ID.md
+git commit -m "$ANTOINE_EVAL_RUN_ID: arm-A captured for <target>/<question_id> (3 trials)"
 ```
 
 Report back: cell count under arm-A/, what's pending for arm-B and
@@ -161,7 +161,7 @@ accumulator file.
 
 Arm-B captures the **directed** trials so the A-vs-B judge run can
 assess "do the skills help when actually used?". Capture happens in
-its own session (`SEER_EVAL_ARM=B`); the A-vs-B judges then run in
+its own session (`ANTOINE_EVAL_ARM=B`); the A-vs-B judges then run in
 the arm-C session's Judge phase, alongside the A-vs-C judges
 (`judge prepare --pair AB`).
 
@@ -173,12 +173,12 @@ the arm-C session's Judge phase, alongside the A-vs-C judges
    ```text
 
    Constraints (verbatim):
-   - For this question, you MUST use the seer skills where they
+   - For this question, you MUST use the antoine skills where they
      apply:
        * `repo-map` (`scripts/profile.sh`, `scripts/connections.sh`,
          `scripts/graph.sh` under `.claude/skills/repo-map/`) for
          repo overview, dependencies, and workspace shape.
-       * `code-lookup` (`seer grep`, `seer recent`, `seer classify`,
+       * `code-lookup` (`antoine grep`, `antoine recent`, `antoine classify`,
          or the equivalent scripts under
          `.claude/skills/code-lookup/`) for symbol references,
          recent commit-symbol diffs, and project-kind classification.
@@ -196,7 +196,7 @@ the arm-C session's Judge phase, alongside the A-vs-C judges
 
    ```bash
    TRIAL_ID=$(uv run --group experiments python -m experiments.scripts_eval.trial \
-       start --run $SEER_EVAL_RUN_ID --arm $SEER_EVAL_ARM \
+       start --run $ANTOINE_EVAL_RUN_ID --arm $ANTOINE_EVAL_ARM \
        --target <target> --question <question_id> --trial <n>)
    # dispatch one Explore subagent with the rendered prompt above
    uv run --group experiments python -m experiments.scripts_eval.trial \
@@ -204,17 +204,17 @@ the arm-C session's Judge phase, alongside the A-vs-C judges
    ```
 
 3. Confirm the cell JSON appeared under
-   `experiments/scripts_eval/results/$SEER_EVAL_RUN_ID/arm-B/`.
+   `experiments/scripts_eval/results/$ANTOINE_EVAL_RUN_ID/arm-B/`.
 
 **After all 3 trials**, summarize + commit:
 
 ```bash
 uv run --group experiments python -m experiments.scripts_eval.summarize \
-    --run $SEER_EVAL_RUN_ID \
-    --out docs/eval-rounds/$SEER_EVAL_RUN_ID.md
+    --run $ANTOINE_EVAL_RUN_ID \
+    --out docs/eval-rounds/$ANTOINE_EVAL_RUN_ID.md
 
-git add docs/eval-rounds/$SEER_EVAL_RUN_ID.md
-git commit -m "$SEER_EVAL_RUN_ID: arm-B captured for <target>/<question_id> (3 trials)"
+git add docs/eval-rounds/$ANTOINE_EVAL_RUN_ID.md
+git commit -m "$ANTOINE_EVAL_RUN_ID: arm-B captured for <target>/<question_id> (3 trials)"
 ```
 
 Report back: cell count under arm-B/, whether the subagent actually
@@ -227,7 +227,7 @@ pending set per the run-state table.
 **Precondition check (mandatory):**
 
 ```bash
-ls experiments/scripts_eval/results/$SEER_EVAL_RUN_ID/arm-A/<target>-<question_id>-t*.json
+ls experiments/scripts_eval/results/$ANTOINE_EVAL_RUN_ID/arm-A/<target>-<question_id>-t*.json
 # expect: 3 files (t1, t2, t3)
 ```
 
@@ -246,7 +246,7 @@ If fewer than 3, stop — arm A must complete first.
    - You may use the `repo-map` skill (and its scripts under
      `.claude/skills/repo-map/`) and the `code-lookup` skill (and its
      scripts under `.claude/skills/code-lookup/`) at your discretion.
-     This includes `seer grep` / `seer recent` / `seer classify`.
+     This includes `antoine grep` / `antoine recent` / `antoine classify`.
    - After answering, append two sections and stop:
      ### tools_used
      - <ToolName>: <count>
@@ -258,7 +258,7 @@ If fewer than 3, stop — arm A must complete first.
 
    ```bash
    TRIAL_ID=$(uv run --group experiments python -m experiments.scripts_eval.trial \
-       start --run $SEER_EVAL_RUN_ID --arm $SEER_EVAL_ARM \
+       start --run $ANTOINE_EVAL_RUN_ID --arm $ANTOINE_EVAL_ARM \
        --target <target> --question <question_id> --trial <n>)
    # dispatch one Explore subagent with the rendered prompt above
    uv run --group experiments python -m experiments.scripts_eval.trial \
@@ -286,7 +286,7 @@ cells exist) and then the A-vs-B judge (if arm-B cells exist):
 
    ```bash
    uv run --group experiments python -m experiments.scripts_eval.judge \
-       prepare --run $SEER_EVAL_RUN_ID \
+       prepare --run $ANTOINE_EVAL_RUN_ID \
        --pair AC \
        --pair-key <target>/<question_id>/<n> \
        --seed 0 > /tmp/judge-AC-<n>.json
@@ -317,7 +317,7 @@ cells exist) and then the A-vs-B judge (if arm-B cells exist):
    A_LABEL=$(jq -r .blind_label_for_A /tmp/judge-AC-<n>.json)
    C_LABEL=$(jq -r .blind_label_for_C /tmp/judge-AC-<n>.json)
    uv run --group experiments python -m experiments.scripts_eval.judge \
-       record --run $SEER_EVAL_RUN_ID \
+       record --run $ANTOINE_EVAL_RUN_ID \
        --pair AC \
        --pair-key <target>/<question_id>/<n> \
        --blind-label-for-a "$A_LABEL" \
@@ -332,7 +332,7 @@ cells exist) and then the A-vs-B judge (if arm-B cells exist):
 
    ```bash
    uv run --group experiments python -m experiments.scripts_eval.judge \
-       prepare --run $SEER_EVAL_RUN_ID \
+       prepare --run $ANTOINE_EVAL_RUN_ID \
        --pair AB \
        --pair-key <target>/<question_id>/<n> \
        --seed 0 > /tmp/judge-AB-<n>.json
@@ -342,7 +342,7 @@ cells exist) and then the A-vs-B judge (if arm-B cells exist):
    A_LABEL=$(jq -r .blind_label_for_A /tmp/judge-AB-<n>.json)
    B_LABEL=$(jq -r .blind_label_for_B /tmp/judge-AB-<n>.json)
    uv run --group experiments python -m experiments.scripts_eval.judge \
-       record --run $SEER_EVAL_RUN_ID \
+       record --run $ANTOINE_EVAL_RUN_ID \
        --pair AB \
        --pair-key <target>/<question_id>/<n> \
        --blind-label-for-a "$A_LABEL" \
@@ -363,19 +363,19 @@ land under `cell["judges"]["AB"]` only.
 
 ```bash
 uv run --group experiments python -m experiments.scripts_eval.validate \
-    --run $SEER_EVAL_RUN_ID
+    --run $ANTOINE_EVAL_RUN_ID
 
 uv run --group experiments python -m experiments.scripts_eval.summarize \
-    --run $SEER_EVAL_RUN_ID \
-    --out docs/eval-rounds/$SEER_EVAL_RUN_ID.md
+    --run $ANTOINE_EVAL_RUN_ID \
+    --out docs/eval-rounds/$ANTOINE_EVAL_RUN_ID.md
 
-git add docs/eval-rounds/$SEER_EVAL_RUN_ID.md
-git commit -m "$SEER_EVAL_RUN_ID: completed <target>/<question_id> (both arms + judge)"
+git add docs/eval-rounds/$ANTOINE_EVAL_RUN_ID.md
+git commit -m "$ANTOINE_EVAL_RUN_ID: completed <target>/<question_id> (both arms + judge)"
 ```
 
 Report back:
 - A-vs-B winners (A / B / tie) and A-vs-C winners (A / C / tie).
-- Whether arm B and arm C actually used the seer scripts (look at the
+- Whether arm B and arm C actually used the antoine scripts (look at the
   `### tools_used` of each cell — `B_did_not_use_scripts` and
   `C_did_not_use_scripts` are findings, not bugs).
 - The next pending set per the run-state table.
@@ -383,7 +383,7 @@ Report back:
 ## Reading the run state
 
 The committed run-state table and per-set verdicts live in
-`docs/eval-rounds/$SEER_EVAL_RUN_ID.md`, between the
+`docs/eval-rounds/$ANTOINE_EVAL_RUN_ID.md`, between the
 `<!-- runstate:start -->` / `<!-- runstate:end -->` and
 `<!-- evidence:start -->` / `<!-- evidence:end -->` markers. `summarize.py`
 rewrites those regions idempotently — do not hand-edit them.
@@ -394,6 +394,6 @@ are needed; `judged` below the arm counts means judges still owe verdicts.
 
 ## Cite-don't-import
 
-This skill is original to seer-cli (the harness only exists here). When
+This skill is original to antoine (the harness only exists here). When
 promoted upstream, it would re-vendor into steward's skill suppliers —
 update `docs/skill-sources.md` accordingly at that point.

{kata_cli-0.8.0 → kata_cli-0.9.2}/.claude/skills/repo-map/SKILL.md

@@ -97,8 +97,8 @@ Flags always override config.
 
 ## Engine
 
-The actual logic lives in `seer/repo/` and is invoked via
-`uv run python -m seer.repo <verb>`. The shell scripts are one-line wrappers; the
+The actual logic lives in `antoine/repo/` and is invoked via
+`uv run python -m antoine.repo <verb>`. The shell scripts are one-line wrappers; the
 agent-facing contract is the verbs and their flags, not the wrappers.
 
 > **Interpreter note:** the scripts use `uv run --directory <project-root>`

{kata_cli-0.8.0 → kata_cli-0.9.2}/.claude/skills/repo-map/scripts/connections.sh

@@ -1,4 +1,4 @@
 #!/usr/bin/env bash
 set -euo pipefail
 PROJECT_ROOT="$(cd "$(dirname "$0")/../../../.." && pwd)"
-exec uv run --directory "$PROJECT_ROOT" python -m seer.repo connections "$@"
+exec uv run --directory "$PROJECT_ROOT" python -m antoine.repo connections "$@"

{kata_cli-0.8.0 → kata_cli-0.9.2}/.claude/skills/repo-map/scripts/graph.sh

@@ -1,4 +1,4 @@
 #!/usr/bin/env bash
 set -euo pipefail
 PROJECT_ROOT="$(cd "$(dirname "$0")/../../../.." && pwd)"
-exec uv run --directory "$PROJECT_ROOT" python -m seer.repo graph "$@"
+exec uv run --directory "$PROJECT_ROOT" python -m antoine.repo graph "$@"

{kata_cli-0.8.0 → kata_cli-0.9.2}/.claude/skills/repo-map/scripts/profile.sh

@@ -1,4 +1,4 @@
 #!/usr/bin/env bash
 set -euo pipefail
 PROJECT_ROOT="$(cd "$(dirname "$0")/../../../.." && pwd)"
-exec uv run --directory "$PROJECT_ROOT" python -m seer.repo profile "$@"
+exec uv run --directory "$PROJECT_ROOT" python -m antoine.repo profile "$@"

{kata_cli-0.8.0 → kata_cli-0.9.2}/.github/workflows/publish.yml

@@ -5,12 +5,12 @@ on:
     branches: [main]
     paths:
       - "pyproject.toml"
-      - "seer/**"
+      - "antoine/**"
   pull_request:
     branches: [main]
     paths:
       - "pyproject.toml"
-      - "seer/**"
+      - "antoine/**"
 
 jobs:
   test:
@@ -57,7 +57,7 @@ jobs:
       - name: Build and publish each distribution to TestPyPI
         run: |
           set -euo pipefail
-          for pkg in seer-cli kata-cli code-lens-cli; do
+          for pkg in antoine-cli kata-cli code-lens-cli; do
             echo "::group::TestPyPI publish $pkg"
             # Run the per-package steps in a subshell so set -e failures
             # don't skip the ::endgroup:: marker — keeps Actions logs
@@ -81,7 +81,7 @@ jobs:
       - name: Print install commands
         if: always()
         run: |
-          for pkg in seer-cli kata-cli code-lens-cli; do
+          for pkg in antoine-cli kata-cli code-lens-cli; do
             echo "::notice::Test with: uv tool install --index-url https://test.pypi.org/simple/ --index-strategy unsafe-best-match $pkg==${DEV_VERSION}"
           done
 
@@ -105,7 +105,7 @@ jobs:
       - name: Build and publish each distribution
         run: |
           set -euo pipefail
-          for pkg in seer-cli kata-cli code-lens-cli; do
+          for pkg in antoine-cli kata-cli code-lens-cli; do
             echo "::group::Publishing $pkg"
             # Run the per-package steps in a subshell so set -e failures
             # don't skip the ::endgroup:: marker — keeps Actions logs

{kata_cli-0.8.0 → kata_cli-0.9.2}/.github/workflows/security-checks.yml

@@ -25,11 +25,11 @@ jobs:
       - run: uv sync
 
       - name: Run Bandit
-        run: uv run bandit -r seer/ -f json -o bandit-results.json -c pyproject.toml
+        run: uv run bandit -r antoine/ -f json -o bandit-results.json -c pyproject.toml
         continue-on-error: true
 
       - name: Run Pylint
-        run: uv run pylint seer/ --output-format=json:pylint-results.json,text
+        run: uv run pylint antoine/ --output-format=json:pylint-results.json,text
         continue-on-error: true
 
       - name: Upload Security Results

{kata_cli-0.8.0 → kata_cli-0.9.2}/.github/workflows/tests.yml

@@ -30,7 +30,7 @@ jobs:
 
       - run: uv sync
 
-      - run: uv run pytest -n auto --cov=seer --cov-report=xml:coverage.xml --cov-report=term -v
+      - run: uv run pytest -n auto --cov=antoine --cov-report=xml:coverage.xml --cov-report=term -v
 
       - name: SonarCloud Scan
         if: env.SONAR_TOKEN != ''
@@ -56,16 +56,16 @@ jobs:
       - run: uv sync
 
       - name: black --check
-        run: uv run black --check seer tests
+        run: uv run black --check antoine tests
 
       - name: isort --check
-        run: uv run isort --check-only seer tests
+        run: uv run isort --check-only antoine tests
 
       - name: flake8
-        run: uv run flake8 --config=.flake8 seer/ tests/
+        run: uv run flake8 --config=.flake8 antoine/ tests/
 
       - name: bandit
-        run: uv run bandit -c pyproject.toml -r seer
+        run: uv run bandit -c pyproject.toml -r antoine
 
       - name: markdownlint-cli2
         run: |

{kata_cli-0.8.0 → kata_cli-0.9.2}/.markdownlint-cli2.yaml

@@ -1,4 +1,4 @@
-# markdownlint-cli2 config for seer-cli.
+# markdownlint-cli2 config for antoine.
 # markdownlint-cli2 stops walking at the git root, so a global
 # markdownlint config in the user's home directory isn't picked up from
 # inside the repo. Keep this file aligned with the global preset.

{kata_cli-0.8.0 → kata_cli-0.9.2}/CHANGELOG.md

@@ -5,6 +5,25 @@ All notable changes to this project will be documented in this file.
 Format follows [Keep a Changelog](https://keepachangelog.com/). This project
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.9.2] - 2026-05-17
+
+### Changed
+
+- CLAUDE.md + README.md: add Name section explaining antoine = N to 1 (collapse N ad-hoc tool calls into one `kata` / `antoine` verb; `kata-cli` is the PyPI distribution label, not a command name).
+- README.md: expand "What's here" to cover the three things antoine manages — the CLI surface (dual-published as `antoine-cli` / `kata-cli` / `code-lens-cli`), the `experiments/scripts_eval/` A/B harness, and the recorded results in `docs/eval-rounds/`.
+
+## [0.9.1] - 2026-05-17
+
+### Changed
+
+- PyPI distribution renamed from `antoine` to `antoine-cli` to avoid name collision and stay consistent with the `kata-cli` / `code-lens-cli` alt-publish naming convention. The Python module (`antoine`) and console script (`antoine`) are unchanged; only the wheel-distribution name moves. `_resolve_version()` fallback list and `.github/workflows/publish.yml` publish loop updated to match.
+
+## [0.9.0] - 2026-05-17
+
+### Changed
+
+- **Repository rename: `seer-cli` → `antoine`.** GitHub remote moved to `agentculture/antoine`; primary PyPI distribution renamed from `seer-cli` to `antoine`; `kata-cli` and `code-lens-cli` alt-publishes preserved. Python module renamed `seer/` → `antoine/`; primary console script renamed `seer` → `antoine` (the `kata` alias is retained). All imports, error classes (`SeerError` → `AntoineError`, `_SeerArgumentParser` → `_AntoineArgumentParser`), env vars (`SEER_EVAL_*` → `ANTOINE_EVAL_*`), Sonar project key (`agentculture_seer-cli` → `agentculture_antoine`), `culture.yaml` agent suffix, vendored skill bodies, and the scripts-eval harness's banned-pattern detection updated accordingly. Historical `CHANGELOG.md` entries, `docs/eval-rounds/`, and dated `docs/superpowers/{specs,plans}/` files are intentionally left referring to `seer` — those describe past state.
+
 ## [0.8.0] - 2026-05-16
 
 ### Added

{kata_cli-0.8.0 → kata_cli-0.9.2}/CLAUDE.md

@@ -2,9 +2,23 @@
 
 This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
 
+## Name
+
+**antoine** = **"N to 1"** (an-to-one). The name encodes the goal: collapse
+the N ad-hoc tool calls an agent would otherwise make against a codebase
+(`ls` + `cat` + `grep` + `git log` + `git show` + …) into **one** call to a
+purpose-built `kata` verb (or its `antoine` alias — both console scripts are
+defined in [`pyproject.toml`](./pyproject.toml); `kata-cli` is the PyPI
+**distribution** name, not a command name) that returns the same information
+as structured data. Every verb antoine ships is a bet that some recurring
+N-call pattern
+has a 1-call replacement that is cheaper, more reliable, and easier to
+delegate to a subagent. You are that agent — when you face a task shape
+covered by the dispatching table below, prefer the 1-call verb.
+
 ## Project Status
 
-`seer-cli` is an AgentCulture sibling repo — **codebase lookup and indexing for
+`antoine` is an AgentCulture sibling repo — **codebase lookup and indexing for
 agent skills**. The onboarding scaffold is in place (package, CLI chassis, CI,
 vendored skills); the actual lookup and indexing engine — how codebases are
 scanned, the index format, where it is stored, and how agent skills consume the
@@ -20,8 +34,8 @@ uv sync                       # install the package + dev dependencies
 ## Run
 
 ```bash
-uv run seer --version         # or: uv run python -m seer
-uv run seer learn             # placeholder verbs: learn / explain / whoami
+uv run antoine --version         # or: uv run python -m antoine
+uv run antoine learn             # placeholder verbs: learn / explain / whoami
 ```
 
 ## Test
@@ -34,9 +48,9 @@ uv run pytest tests/test_cli_chassis.py::test_no_args_prints_help_and_returns_ze
 ## Lint / Format
 
 ```bash
-uv run flake8 --config=.flake8 seer/ tests/
-uv run black seer/ tests/
-uv run isort seer/ tests/
+uv run flake8 --config=.flake8 antoine/ tests/
+uv run black antoine/ tests/
+uv run isort antoine/ tests/
 markdownlint-cli2 "**/*.md"
 ```
 
@@ -44,14 +58,14 @@ Bandit and pylint run in CI (`.github/workflows/security-checks.yml`).
 
 ## Architecture
 
-- `seer/cli/__init__.py` — the argparse CLI chassis: structured error
-  routing (`_SeerArgumentParser`), `--json` hint detection, and
-  `_dispatch` (invokes the verb handler, translating `SeerError` and bare
+- `antoine/cli/__init__.py` — the argparse CLI chassis: structured error
+  routing (`_AntoineArgumentParser`), `--json` hint detection, and
+  `_dispatch` (invokes the verb handler, translating `AntoineError` and bare
   exceptions to structured exit codes). `main()` is the entry point, exposed
-  as the `seer` console script and via `python -m seer`.
-- `seer/cli/_errors.py` — `SeerError` and the exit-code policy.
-- `seer/cli/_output.py` — strict stdout/stderr split helpers.
-- `seer/cli/_commands/` — one module per verb, each exposing `register()`.
+  as the `antoine` console script and via `python -m antoine`.
+- `antoine/cli/_errors.py` — `AntoineError` and the exit-code policy.
+- `antoine/cli/_output.py` — strict stdout/stderr split helpers.
+- `antoine/cli/_commands/` — one module per verb, each exposing `register()`.
   All three verbs are currently greenfield stubs.
 
 ## Version Management
@@ -70,9 +84,9 @@ from `../steward/.claude/skills/<name>/`.
 
 `experiments/scripts_eval/` is the round-1 A/B-test harness for the
 `repo-map` skill. The three Claude Code hooks wired in
-`.claude/settings.json` are **env-var-gated** (`SEER_EVAL_RUN_ID`,
-`SEER_EVAL_ARM`) and no-op outside an active eval session, so
-day-to-day seer-cli work is unaffected.
+`.claude/settings.json` are **env-var-gated** (`ANTOINE_EVAL_RUN_ID`,
+`ANTOINE_EVAL_ARM`) and no-op outside an active eval session, so
+day-to-day antoine work is unaffected.
 
 When asked to run an eval round, work the harness, or interpret its
 results, read these in order:
@@ -124,7 +138,7 @@ not subagents you dispatch):
 of the PR #18 organic-adoption smokes showed that **subagents construct
 their plan from the prompt body before consulting the skills catalog** —
 so a description-shape change on the skill itself does not move adoption
-(0 of 2 models picked up `seer recent` for a question perfectly tuned for
+(0 of 2 models picked up `antoine recent` for a question perfectly tuned for
 it). Round-3 confirmed the parent-agent path: a fresh session loading the
 table delegated *and the subagent invoked the verb directly via the
 injected directive*.
@@ -140,4 +154,4 @@ in row 1 above — the table does not change that.
 
 ## Workspace Context
 
-The GitHub remote is `agentculture/seer-cli`. When opening PRs or posting comments here as an AI assistant, sign them so it's clear they're AI-authored — e.g. `- seer (Claude)`.
+The GitHub remote is `agentculture/antoine`. When opening PRs or posting comments here as an AI assistant, sign them so it's clear they're AI-authored — e.g. `- antoine (Claude)`.