fix: update CodeBoarding dependency to 0.15.0 (#146)

Amp-Thread-ID: https://ampcode.com/threads/T-01a13bd6-a427-7096-a1ef-2beec231f78e

Co-authored-by: Amp <amp@ampcode.com>

Author: ivanmilevtues

README.md

@@ -344,7 +344,7 @@ The first sync after the merge creates `codeboarding/baseline`, catching up from
 
 `target_branch` and `sync_strategy` are deprecated, and read as the `codeboarding_analysis_location` they stand for, with a warning: `sync_strategy: push` as `in_place`, `sync_strategy: pull_request` as `codeboarding_branch`. `target_branch` is accepted only when it names the branch the run is on: the push trigger picks the branch. `force_full: true` is ignored with a warning. Anything the new input cannot express fails, linking to [moving an existing setup](#moving-an-existing-setup).
 
-The `/codeboarding` command, comment heading, Mermaid direction (`LR`), hosted webview URL, commit message, and CodeBoarding 0.14.5 version are intentionally fixed rather than exposed as configuration.
+The `/codeboarding` command, comment heading, Mermaid direction (`LR`), hosted webview URL, commit message, and CodeBoarding 0.15.0 version are intentionally fixed rather than exposed as configuration.
 
 Review mode needs no sync job or committed `.codeboarding` directory. If no
 usable merge-base analysis exists, it runs full analysis there directly, then
@@ -401,7 +401,7 @@ Run the local analysis pipeline:
 
 ```bash
 export OPENROUTER_API_KEY=sk-or-...
-python -m pip install codeboarding==0.14.5
+python -m pip install codeboarding==0.15.0
 tests/run_local.sh --repo /path/to/repo --base main --head feature
 ```
 

action.yml

@@ -404,7 +404,7 @@ runs:
       if: steps.guard.outputs.skip != 'true'
       shell: bash
       run: |
-        python -m pip install --disable-pip-version-check 'codeboarding==0.14.5'
+        python -m pip install --disable-pip-version-check 'codeboarding==0.15.0'
         # Fail here, with the reason, rather than mid-analysis with a traceback:
         # pinning a release does not pin what its dependencies resolve to. Run
         # the console script, not `python -c`, which would put the analyzed

scripts/action/supported-providers.json

@@ -18,7 +18,7 @@
     "a selection env (AWS_DEFAULT_REGION, OLLAMA_API_KEY) therefore cannot select a provider",
     "on its own, which is why ollama and litellm need their base URL and not just a key."
   ],
-  "engine": "0.14.5",
+  "engine": "0.15.0",
   "hosted_provider": "openrouter",
   "providers": {
     "openrouter": {