scar-cli 0.22.0__tar.gz → 0.24.0__tar.gz

scar_cli-0.24.0/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.24.0"
+}

{scar_cli-0.22.0 → scar_cli-0.24.0}/.scars/0005-history-rewrite-orphans-commit-evidence.landmine.md

@@ -8,8 +8,13 @@ created: 2026-06-11
 authors: ["claude-code", "Kibukx"]
 anchors:
   - path: .scars/
+  - command: "git push.*--force"
+  - command: "git rebase"
+  - command: "git filter-repo|git filter-branch"
+  - command: "git commit.*--amend"
 violation: "commit: [0-9a-f]{7,40}"
 evidence:
+  - note: "2026-09-05 anchors: path .scars/ KEPT on purpose. The violation tripwire commit: [0-9a-f]{7,40} only evaluates on files an anchor matched, so dropping it to cut firings would silently disarm the scar. Command anchors added instead, so the history-rewrite half fires on the act rather than on any scar edit"
   - note: v0.1.0 public release (2026-06-11): fresh-start force-push orphaned 3 commit SHAs cited by scars 0001 and 0002; SHAs still resolve on GitHub by URL but fail in any fresh clone, and GitHub may GC them eventually
 expires:
   condition: "evidence schema gains a resolvable form (full URL or archived diff) or lint warns on bare SHAs at promotion"

{scar_cli-0.22.0 → scar_cli-0.24.0}/.scars/0006-yaml-pattern-anchor-over-escaping.landmine.md

@@ -9,8 +9,9 @@ authors: ["claude-code", "kibukx"]
 anchors:
   - path: src/scar/orphan.py
   - path: src/scar/match.py
-  - path: .scars/
+  - pattern: "\n\s*-\s*pattern:"
 evidence:
+  - note: "2026-09-05 anchors: path .scars/ replaced by a pattern matching a scar frontmatter pattern: entry. The directory anchor fired on every scar edit, while the hazard only exists when a pattern anchor is being authored"
   - pr: 40
   - note: scar 1 grep pattern matched only its own body, never experiments/anchor-survival/RESULTS.md
 expires:

{scar_cli-0.22.0 → scar_cli-0.24.0}/.scars/0008-rich-output-nontty-must-bypass-rich.landmine.md

@@ -7,10 +7,10 @@ confidence: 0.9
 created: 2026-06-30
 authors: ["claude-code", "kibukx"]
 anchors:
-  - path: src/scar/cli.py
   - path: src/scar/output.py
-  - pattern: "output\.render\("
+  - pattern: "def plain\(\):"
 evidence:
+  - note: "2026-09-05 anchors: path src/scar/cli.py dropped, it is 3000+ lines and the tty gate is 17 of them. The 18 output.render( call sites only invoke the already-safe dispatcher, so that pattern is replaced by def plain():, which marks the 14 non-tty contract closures this scar actually protects"
   - issue: 78
   - note: 187-test suite asserts plain substrings like '0001-bad.deadend.md' and long anchor paths on main([...]) under capsys
 expires:

{scar_cli-0.22.0 → scar_cli-0.24.0}/.scars/0011-lint-compile-check-lets-redos-anchors-hang-hotpath.landmine.md

@@ -7,11 +7,11 @@ confidence: 0.9
 created: 2026-06-30
 authors: ["claude-code", "Kibukx"]
 anchors:
-  - path: src/scar/lint.py
-  - path: src/scar/match.py
   - pattern: "rx\.search\("
   - pattern: "MAX_ANCHOR_SCAN"
+  - pattern: "_is_redos_prone"
 evidence:
+  - note: "2026-09-05 anchors: both whole-file path anchors dropped, lint.py and match.py serve many concerns beyond ReDoS. _is_redos_prone added so the GATE itself stays anchored, since the body says the gate is the defense and the 64 KiB cap is not"
   - issue: 88
 expires:
   condition: "lint gains full regex-safety analysis OR the matcher runs on a hardened regex engine with a hard timeout"

{scar_cli-0.22.0 → scar_cli-0.24.0}/.scars/0017-codex-pretool-context-can-replay-apply-patch.landmine.md

@@ -8,7 +8,6 @@ created: 2026-08-28
 authors: ["codex", "Kibukx"]
 anchors:
   - path: src/scar/codex.py
-  - path: plugin/hooks/hooks.json
 evidence:
   - issue: 243
   - note: live codex-cli 0.147.0 A/B emitted two tool_use_ids for one identical apply_patch after the first PreToolUse context injection

scar_cli-0.22.0/.scars/candidates/one-directional-health-check-leaves-flattering-direction-unwatched.md → scar_cli-0.24.0/.scars/0020-one-directional-health-check-leaves-flattering-direction-unwatched.landmine.md

@@ -1,21 +1,25 @@
 ---
-id: 0
+id: 20
 type: landmine
 title: A health check that watches one direction of pipeline failure leaves the flattering direction unwatched
 severity: high
 confidence: 0.9
 created: 2026-08-30
 authors: ["claude-code"]
+promoted_by: Kibukx
+promoted_by_source: git-config
 anchors:
   - path: src/scar/cli.py
   - path: src/scar/hooks.py
+  - path: src/scar/codex.py
+  - path: src/scar/cascade.py
   - pattern: "instrument_disconnected|posttool_silent|verdict_observed"
 evidence:
   - issue: 277
   - issue: 237
 expires:
   condition: "the pipeline stops having two independently-installable halves"
-status: candidate
+status: active
 ---
 
 The precheck and posttool hooks install separately and fail separately. #237

scar_cli-0.22.0/.scars/candidates/posttool-fix-in-hooks-does-not-reach-codex-or-cascade.md → scar_cli-0.24.0/.scars/0021-posttool-fix-in-hooks-does-not-reach-codex-or-cascade.landmine.md

@@ -1,16 +1,17 @@
 ---
-id: 0
+id: 21
 type: landmine
 title: A posttool change in hooks.py does not reach codex.py or cascade.py, which carry their own copy of the same logic
 severity: high
 confidence: 0.8
 created: 2026-09-02
 authors: ["claude-code"]
+promoted_by: Kibukx
+promoted_by_source: git-config
 anchors:
   - path: src/scar/hooks.py
   - path: src/scar/codex.py
   - path: src/scar/cascade.py
-violation: "if not violations:"
 evidence:
   - issue: 277
   - issue: 293
@@ -18,7 +19,8 @@ evidence:
 expires:
   condition: "the three posttool paths share one implementation, or the adapters delegate to hooks.posttool"
   review_after: 2026-12-01
-status: candidate
+violation: "if not violations:"
+status: active
 ---
 
 The posttool verdict logic exists three times: `hooks.posttool` for Claude

scar_cli-0.22.0/.scars/candidates/codex-hook-delivery-needs-user-file-and-trust.md → scar_cli-0.24.0/.scars/0022-codex-hook-delivery-needs-user-file-and-trust.landmine.md

@@ -1,13 +1,14 @@
 ---
-id: 0
+id: 22
 type: landmine
 title: Codex plugin hooks are not materialized, and untrusted Codex hooks are skipped silently
 severity: high
 confidence: 0.9
 created: 2026-08-28
 authors: ["claude-code"]
+promoted_by: Kibukx
+promoted_by_source: git-config
 anchors:
-  - path: plugin/hooks/hooks.json
   - path: src/scar/codex.py
   - pattern: "hooks/hooks\.json|CODEX_HOME|codex-(pretool|posttool|session-notice)"
 evidence:
@@ -17,7 +18,7 @@ evidence:
 expires:
   condition: "Codex materializes a plugin's hooks/hooks.json into the installed cache AND surfaces an error for untrusted hooks"
   review_after: 2027-02-28
-status: candidate
+status: active
 ---
 
 Shipping a Codex hook through a plugin's `hooks/hooks.json` does not deliver it,

scar_cli-0.24.0/.scars/candidates/host-detection-must-not-read-the-process-home.md

@@ -0,0 +1,40 @@
+---
+id: 0
+type: deadend
+title: Host detection must take home from installer.CLAUDE_DIR, never Path.home() — a bare call passes locally and fails every other machine
+severity: high
+confidence: 0.9
+created: 2026-09-07
+authors: ["claude-code"]
+anchors:
+  - pattern: "detect_hosts\("
+  - symbol: src/scar/cli.py::_detect
+evidence:
+  - issue: 318
+  - note: "2026-09-07, during the multi-host skill install work: the skill-install refusal resolved home with Path.home(). Under HOME=empty the suite went 1031 passed / 2 FAILED, both PRE-EXISTING tests, printing 'claude not detected on this machine, nothing written'. Fixed by reusing _detect(). Branch SHAs deliberately omitted: scar #5 fired on the amend that wrote this, and squash-merge would orphan them."
+expires:
+  condition: "detect_hosts takes home from one injected seam no caller can bypass"
+  review_after: 2027-03-08
+status: candidate
+---
+
+`Path.home()` in a detection path looks obviously right and is a trap. Tests
+patch `installer.CLAUDE_DIR`, not the environment, and `_detect()` derives
+home from `installer.CLAUDE_DIR.parent`. A bare call reads the author's real
+home, finds their real `~/.claude`, and passes. On any machine without one,
+every CI runner included, detection returns nothing and the caller refuses.
+
+The failure is invisible where it is introduced: the suite was fully green on
+the authoring machine, and the tests that finally failed were pre-existing
+ones nobody had touched. Use `_detect(kind)`, or `installer.CLAUDE_DIR.parent`
+exactly as `_detect` does. Never add a second answer to where home is.
+
+Two anchors on purpose. `cli.py` is 143 KiB and its first `detect_hosts(` sits
+at byte ~123,000, past the 64 KiB `MAX_ANCHOR_SCAN` bound, so the pattern is
+blind to the very file the defect landed in. The `symbol:` anchor covers it,
+at the cost of needing `scar-cli[symbols]`. Lint reports neither gap: the
+pattern matches `hosts.py`, so the scar reads live while blind where it counts.
+
+Not armed. The obvious tripwire is `Path\.home\(\)`, but `cli.py` carries that
+string in a warning comment and `installer.py` uses it correctly for module
+constants, so it would fire on prose and on correct code.

scar_cli-0.24.0/.scars/candidates/one-plugin-hook-manifest-two-hosts-two-root-variables.md

@@ -0,0 +1,30 @@
+---
+id: 0
+type: landmine
+title: A plugin hook manifest is read by every host that installs the plugin, and hosts expand different root variables
+severity: high
+confidence: 0.9
+created: 2026-09-03
+authors: ["claude-code"]
+anchors:
+  - path: plugin/
+  - path: src/scar/installer.py
+  - pattern: "PLUGIN_ROOT"
+evidence:
+  - issue: 303
+  - issue: 244
+expires:
+  condition: "the plugin format gains per-host scoping for hook files"
+  review_after: 2026-12-01
+status: candidate
+---
+
+Claude Code merges plugin.json hooks with hooks/hooks.json and defines only
+CLAUDE_PLUGIN_ROOT. Codex reads the same file and defines both PLUGIN_ROOT
+and CLAUDE_PLUGIN_ROOT. A hooks/hooks.json written for Codex with
+${PLUGIN_ROOT} therefore ran on every Claude session start and Bash call as
+"/hooks/run.sh": No such file or directory, on every machine with the plugin
+(#244 introduced it, #303 removed it). There is no way to mark a plugin
+hook file as one host's only. Ship one manifest per plugin, on
+${CLAUDE_PLUGIN_ROOT}, and deliver host-specific hooks through
+`scar hook install --runtime <host>`, whose files live outside the plugin.

scar_cli-0.24.0/.scars/candidates/path-anchor-breadth-drives-the-review-due-threshold.md

@@ -0,0 +1,37 @@
+---
+id: 0
+type: landmine
+title: A whole-file or whole-directory path anchor makes the review-due threshold report anchor breadth, not code hazard
+severity: medium
+confidence: 0.8
+created: 2026-09-04
+authors: ["claude-code"]
+anchors:
+  - path: SCAR-FORMAT.md
+  - pattern: "review_after_firings"
+evidence:
+  - issue: 312
+  - note: "triage of all five over-threshold scars in this repo on 2026-09-04: four were over-anchored, one was a real code fix"
+expires:
+  condition: "lint reports what share of a scar's firings touched the hazard, so the review-due warning can distinguish breadth from recurrence"
+  review_after: 2027-03-04
+status: candidate
+---
+
+`scar lint` warns past `review_after_firings` that either the guarded code
+merits the fix or the scar merits revision. Read literally that sends you to
+the code first. It is usually the anchor.
+
+A `path:` anchor is a repo-relative PREFIX, so it fires on every edit beneath
+it. Scar #8 guards a 17-line tty branch inside a 52-line module but anchored
+the whole 3,090-line `src/scar/cli.py`; roughly nine of every ten of its 47
+firings touched nothing related. Scar #5 guards against history rewrites and
+anchored all of `.scars/`, so it fired on 22 routine promotions and zero
+force-pushes, which is zero of its actual trigger events.
+
+A firing count therefore measures anchor breadth first and hazard recurrence
+second, and the two are not separable from the log. Before reading a
+review-due warning as evidence that code needs fixing, check what share of the
+firings touched the hazard at all. Then narrow the anchor to the smallest file
+holding the branching, or switch to a `command:` anchor when the trigger is an
+action rather than a file (#312 is the one case here that really was the code).

{scar_cli-0.22.0 → scar_cli-0.24.0}/AGENTS.md

@@ -26,8 +26,11 @@ The full authoring contract — qualification criteria, the candidates-only writ
 path, mandatory YAML frontmatter, and the regex over-escaping trap — is packaged
 as the `scar-authoring` skill.
 
-- **Claude Code:** install the plugin (recommended) or `scar skill install` to
-  drop the skill into `~/.claude/skills/`. It auto-loads on trigger.
+- **Claude Code, Codex, Cursor, opencode, Windsurf:** `scar skill install`
+  detects which of those hosts are on the machine and writes the skill to each
+  one's native skills directory. On Claude Code the plugin is the recommended
+  route and carries the same skill. The per-host destination table is in
+  [website/docs/agents.md](website/docs/agents.md).
 - **MCP agents (Cursor/Windsurf/opencode):** the `scar_draft` tool enforces the
   candidates-only path and lints before writing; its description carries the
   digest.

{scar_cli-0.22.0 → scar_cli-0.24.0}/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## [0.24.0](https://github.com/Daily-Nerd/Scar/compare/v0.23.0...v0.24.0) (2026-09-08)
+
+
+### Features
+
+* **firing-log:** one shared validated reader for the firing log ([#313](https://github.com/Daily-Nerd/Scar/issues/313)) ([d316922](https://github.com/Daily-Nerd/Scar/commit/d31692205715e63380b8ac104643de4ceac0338d))
+* **skill:** install the authoring skill to every detected host ([#320](https://github.com/Daily-Nerd/Scar/issues/320)) ([1d9c985](https://github.com/Daily-Nerd/Scar/commit/1d9c985e3e5815ba67d222defa86d549886c7e94))
+
+
+### Bug Fixes
+
+* **promote:** record whether a promotion happened at a terminal ([#315](https://github.com/Daily-Nerd/Scar/issues/315)) ([f28e8eb](https://github.com/Daily-Nerd/Scar/commit/f28e8eb90a5fb3161aa40565dbfb218d1b9b4160)), closes [#308](https://github.com/Daily-Nerd/Scar/issues/308)
+
+## [0.23.0](https://github.com/Daily-Nerd/Scar/compare/v0.22.0...v0.23.0) (2026-09-03)
+
+
+### ⚠ BREAKING CHANGES
+
+* **install:** with no --runtime, no terminal, and more than one detected host, scar hook install and scar skill install write nothing and print the commands to run instead of installing Claude Code by default.
+
+### Features
+
+* **install:** detect installed hosts and the channel that already serves each ([#304](https://github.com/Daily-Nerd/Scar/issues/304)) ([180cf6f](https://github.com/Daily-Nerd/Scar/commit/180cf6f53ab671e6fb9ce6636fe718aabead1c7c))
+
 ## [0.22.0](https://github.com/Daily-Nerd/Scar/compare/v0.21.0...v0.22.0) (2026-09-03)
 
 

{scar_cli-0.22.0 → scar_cli-0.24.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: scar-cli
-Version: 0.22.0
+Version: 0.24.0
 Summary: SCAR — version control for negative knowledge (deadends, fences, landmines)
 License: MIT
 License-File: LICENSE
@@ -75,20 +75,16 @@ cp .scars/template.md .scars/candidates/redis-sessions.md
 $EDITOR .scars/candidates/redis-sessions.md
 scar lint                        # validate format
 scar promote redis-sessions.md   # human review gate: candidate -> active
-scar hook install                # Claude Code: inject scars before agent edits
-scar skill install               # Claude Code: authoring skill into ~/.claude/skills/
-scar hook install --runtime windsurf   # Windsurf/Cascade: block-once injection
+scar hook install                # detects installed hosts, asks which to wire (--all, --runtime X)
+scar skill install               # same detection for the scar-authoring skill
+scar hook status                 # every host with the channel that serves it (settings, plugin, none)
 ```
 
-Claude Code users: the marketplace **plugin** ships the hooks and the
-scar-authoring skill together; the two commands above are the manual fallback.
-Re-run `scar skill install` after upgrading — the installed skill is a static copy.
+`scar skill install` writes the scar-authoring skill to a native path for Claude Code, Codex, Cursor, opencode, or Windsurf. Claude Code is the one confirmed to load it, and the rest are written per vendor documentation but unverified: see the [per-host table](https://daily-nerd.github.io/Scar/agents#where-scar-skill-install-writes) for which is which.
 
-Codex users: install and enable the Scar plugin, then open `/hooks` to review
-and trust its current hook definitions. The native plugin hooks push matching
-scars before `Bash` and `apply_patch` calls and report post-patch `violation:`
-tripwires without blocking or rewriting the action. Plugin updates that change
-the hook definitions require trust review again.
+Claude Code users: the marketplace **plugin** ships the hooks and the scar-authoring skill together. `scar hook install` and `scar skill install` see the plugin and skip Claude unless you pass `--runtime claude --force`. Re-run `scar skill install` after upgrading a manual install; the installed skill is a static copy.
+
+Codex users: run `scar hook install --runtime codex`, then open `/hooks` in Codex to review and trust the entries. The hooks push matching scars before `Bash` and `apply_patch` calls and report post-patch `violation:` tripwires without blocking. The plugin no longer carries Codex hook definitions; the installer is the one path.
 
 Full walkthrough, lifecycle commands, and agent wiring (Claude Code plugin,
 Codex native hooks, Windsurf/Cascade hooks, MCP server, `scar draft-check`):

{scar_cli-0.22.0 → scar_cli-0.24.0}/README.md

@@ -60,20 +60,16 @@ cp .scars/template.md .scars/candidates/redis-sessions.md
 $EDITOR .scars/candidates/redis-sessions.md
 scar lint                        # validate format
 scar promote redis-sessions.md   # human review gate: candidate -> active
-scar hook install                # Claude Code: inject scars before agent edits
-scar skill install               # Claude Code: authoring skill into ~/.claude/skills/
-scar hook install --runtime windsurf   # Windsurf/Cascade: block-once injection
+scar hook install                # detects installed hosts, asks which to wire (--all, --runtime X)
+scar skill install               # same detection for the scar-authoring skill
+scar hook status                 # every host with the channel that serves it (settings, plugin, none)
 ```
 
-Claude Code users: the marketplace **plugin** ships the hooks and the
-scar-authoring skill together; the two commands above are the manual fallback.
-Re-run `scar skill install` after upgrading — the installed skill is a static copy.
+`scar skill install` writes the scar-authoring skill to a native path for Claude Code, Codex, Cursor, opencode, or Windsurf. Claude Code is the one confirmed to load it, and the rest are written per vendor documentation but unverified: see the [per-host table](https://daily-nerd.github.io/Scar/agents#where-scar-skill-install-writes) for which is which.
 
-Codex users: install and enable the Scar plugin, then open `/hooks` to review
-and trust its current hook definitions. The native plugin hooks push matching
-scars before `Bash` and `apply_patch` calls and report post-patch `violation:`
-tripwires without blocking or rewriting the action. Plugin updates that change
-the hook definitions require trust review again.
+Claude Code users: the marketplace **plugin** ships the hooks and the scar-authoring skill together. `scar hook install` and `scar skill install` see the plugin and skip Claude unless you pass `--runtime claude --force`. Re-run `scar skill install` after upgrading a manual install; the installed skill is a static copy.
+
+Codex users: run `scar hook install --runtime codex`, then open `/hooks` in Codex to review and trust the entries. The hooks push matching scars before `Bash` and `apply_patch` calls and report post-patch `violation:` tripwires without blocking. The plugin no longer carries Codex hook definitions; the installer is the one path.
 
 Full walkthrough, lifecycle commands, and agent wiring (Claude Code plugin,
 Codex native hooks, Windsurf/Cascade hooks, MCP server, `scar draft-check`):

{scar_cli-0.22.0 → scar_cli-0.24.0}/SCAR-FORMAT.md

@@ -43,7 +43,7 @@ is deliberate: consumers in hook hot-paths parse with zero dependencies.
 | `created` | yes | ISO date | |
 | `authors` | yes | inline list | who drafted it: agents as `"claude-code"` etc. The reviewer is no longer appended here |
 | `promoted_by` | active scars | string | the human who promoted it. Written only by `scar promote`, which overwrites anything a candidate carried. Empty on scars promoted before the field existed, and never inferred from `authors` |
-| `promoted_by_source` | optional | `explicit` \| `git-config` | whether `promoted_by` came from `--reviewer` or from `git config user.name`. Written only alongside `promoted_by`, never on its own. Absent on scars promoted before the field existed |
+| `promoted_by_source` | optional | `explicit` \| `git-config-interactive` \| `git-config` | how strongly `promoted_by` is evidenced. `explicit` = a name was typed with `--reviewer`. `git-config-interactive` = no name typed, but `promote` ran at a terminal, so a person was there. `git-config` = no name typed and no terminal recorded, which is the unattended shape `lint` warns on. Written only alongside `promoted_by`, never on its own. Absent on scars promoted before the field existed, and plain `git-config` on scars promoted before interactivity was recorded, so neither absence proves an agent did it |
 | `anchors` | yes, ≥1 | list of `- path:`, `- pattern:`, `- symbol:`, and/or `- command:` | §4 |
 | `evidence` | recommended | list of `- commit:`/`- pr:`/`- issue:`/`- incident:`/`- note:`/`- url:` | absent ⇒ challengeable on sight; `issue:`/`url:` are durable forms that survive squash-merge |
 | `expires.condition` | recommended | quoted string | what change obsoletes this scar |

{scar_cli-0.22.0 → scar_cli-0.24.0}/SPEC.md

@@ -464,3 +464,9 @@ just as well as edit rows do.
 command output, and asserts the nullable semantics of §9.2. A guarantee no
 test enforces is an untestable assertion, and untestable assertions are the
 ones that reach `main` wrong.
+
+### 9.10 Install detection
+
+`scar hook install` and `scar skill install` without `--runtime` detect hosts (claude, codex, windsurf, cursor, opencode) by config directory or binary on PATH, and resolve for each the channel that already serves it: `settings` (Scar's own entries in the host's hook file), `plugin` (the scar marketplace plugin installed and not disabled), or `none`. windsurf is repo-scoped: its hooks file is written into the working repo, so the binary on PATH counts only when that repo is inside a git repository. On a terminal, one question per present, wirable, unserved host, default no. Without a terminal, exactly one such host is installed; zero or several means the commands are printed and nothing is written. Zero detected hosts says so, rather than naming the plugin. `--all` wires every such host. `--runtime claude` on a Claude Code already served by the plugin refuses unless `--force`. `--all` and `--force` apply to `install` only, and `--force` applies to `--runtime claude` only. A missing or unreadable plugin registry never counts as `plugin`.
+
+Two rules differ for the skill kind. windsurf is not repo-scoped there: its global skills live under home (`~/.codeium/windsurf/skills`), so the binary on PATH counts on its own, with no git-repo guard. And `scar skill install --runtime <host>` refuses, exit 1, when detection does not find that host on the machine, rather than creating a skill directory nothing reads. Every destination resolves through the same home the detection pass used, and the Codex destination honours `$CODEX_HOME`, so a reported success always names a directory the detected host actually reads.

{scar_cli-0.22.0 → scar_cli-0.24.0}/plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "scar",
-  "version": "0.22.0",
+  "version": "0.24.0",
   "description": "SCAR — version control for negative knowledge (deadends, fences, landmines)",
   "hooks": {
     "PreToolUse": [

{scar_cli-0.22.0 → scar_cli-0.24.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "scar-cli"
-version = "0.22.0"
+version = "0.24.0"
 description = "SCAR — version control for negative knowledge (deadends, fences, landmines)"
 readme = "README.md"
 requires-python = ">=3.10"

{scar_cli-0.22.0 → scar_cli-0.24.0}/release-please-config.json

@@ -3,6 +3,7 @@
   "packages": {
     ".": {
       "release-type": "python",
+      "bump-minor-pre-major": true,
       "extra-files": [
         {
           "type": "json",