@heytherevibin/skillforge 0.8.0 → 0.10.1

package/CHANGELOG.md

@@ -1,5 +1,27 @@
 # Changelog
 
+## 0.10.1
+
+- **README:** Clarify that **npm** **`latest`** and **`npm view`** are authoritative for semver; note CDN/browser cache can make the shields **npm** badge lag briefly after a publish. **Badge:** add **`cacheSeconds`** so the image URL refreshes sooner.
+
+## 0.10.0
+
+- **CI:** Minimum bundled **`SKILL.md`** count is configured via **`ci/bundle-gate.json`** (`minSkillMdFiles`); **`.github/workflows/ci.yml`** reads that file. The **`ci/`** directory is included in the published package **`files`** list for transparency. Health + **route-eval** step chains both commands under a single **`cd python`** so the second command does not run from **`python/python`**.
+- **MCP `_meta`:** **`schema_version` 1.7** — optional **`routing_overlay`** (project exclude / boost / notes audit). **1.6** — optional **`feedback_effect`** (learned-weight transparency after each route). **1.5** — optional **`route_quality`** (shortlist, hybrid, policy/session signals). Implemented in **`app/mcp_contract.py`** (see constant **`MCP_RESPONSE_SCHEMA_VERSION`**).
+- **Project routing overlay:** optional **`exclude_skills`**, **`routing_boosts`**, **`project_notes`** (and aliases) in the same JSON document as regex **`rules`** — parsed by **`app/route_policies.py`**, applied in **`Router`** shortlists; **`project_notes`** require **`project_root`** to apply.
+- **Operator CLIs:** **`skillforge health`** (`python/app/health_cli.py`), **`skillforge route-eval`** (`eval_cli` + fixtures under **`python/fixtures/route_eval/`**), **`skillforge weights export|import`** (`weights_cli.py`). CI runs **health --quick** and embedding **route-eval** with **`SKILLFORGE_BUNDLED_SKILLS`** set to the workspace skills tree.
+- **MCP / search & explain:** **`search_skills`** and **`explain_route`** honor the same overlay + notes as **`route_skills`**; **`explain_route`** passes explicit shortlist **`k`** into **`Router.shortlist`**.
+- **Fix:** **`skillforge route`** defines **`db_disp`** before use in host-pick output (**`route_cli.py`**).
+
+## 0.9.0
+
+- **Host-delegated routing:** set **`SKILLFORGE_ROUTER_MODE=host`** to skip the in-process Haiku pick. First **`route_skills`** call returns a tight numbered shortlist (markdown + **`_meta.host_pick_candidates`**); second call with **`picked_names`** loads context, policies, and session **`uses`** as usual. No **`ANTHROPIC_API_KEY`** required for the pick step. Tunables: **`SKILLFORGE_HOST_PICK_MAX`**, **`SKILLFORGE_HOST_PICK_LINE_CHARS`**.
+- **`picked_names`** on **`route_skills`** (optional): in **`embedding`** / **`full`** modes, supplying **`picked_names`** skips auto-pick and uses the host list (unchanged behavior, now documented).
+- **`skillforge_bootstrap`** returns an error when **`SKILLFORGE_ROUTER_MODE=host`** (use two-step **`route_skills`** + **`materialize_project`**).
+- **CLI:** **`skillforge route --picked-names=a,b`** mirrors MCP finalize. **`--json-meta`** includes **`host_pick_shortlist`** when applicable.
+- **Cursor (global `/skillforge`)** and **Claude Code**: on **`skillforge install`** / first-run setup, Skillforge writes **`~/.cursor/commands/skillforge.md`** and/or **`~/.claude/commands/skillforge.md`** when each environment is detected; **`skillforge hosts init`** updates both without Python setup. Opt out: **`SKILLFORGE_SKIP_CURSOR_SETUP`**, **`SKILLFORGE_SKIP_CLAUDE_CODE_SETUP`**. Force: **`SKILLFORGE_CURSOR_GLOBAL_COMMAND`**, **`SKILLFORGE_CLAUDE_CODE_GLOBAL_COMMAND`**. **`--force-cursor`** replaces managed files. **Claude Desktop** remains detect-only + MCP merge hint.
+- **MCP** server version **0.9.0**; **`materialize_project`** writes per-repo **`.cursor/commands`** and **`.claude/commands`** **`/skillforge`** with **`skill_names`**.
+
 ## 0.8.0
 
 - **Smarter routing:** optional **conversation-aware** shortlist query (`SKILLFORGE_ROUTER_CONV_*`), **hybrid** retrieval (`SKILLFORGE_ROUTER_HYBRID` = `keyword` or `bm25` + `SKILLFORGE_ROUTER_HYBRID_ALPHA`), optional **Haiku rerank** (`SKILLFORGE_HAIKU_RERANK`, `SKILLFORGE_HAIKU_RERANK_MAX`, `SKILLFORGE_HAIKU_RERANK_MODEL`).

package/CONTRIBUTING.md

@@ -1,38 +1,49 @@
 # Contributing
 
-Thanks for helping improve skillforge.
+Thank you for improving Skillforge.
 
-## How to contribute
+## Workflow
+
+1. **Fork** the repository and create a branch from **`main`**.
+2. Keep changes **focused**; follow patterns in surrounding code.
+3. Run **local checks** before opening a PR from the **package root** (the directory that contains **`package.json`**):
 
-1. **Fork** the repository and create a branch from `main`.
-2. Make focused changes; match existing style in the touched files.
-3. Run local checks before pushing:
    ```bash
    node --check bin/cli.js && node --check lib/packs.js
    npm test
    ```
-4. Open a **pull request** into `main` with a clear description of the change and why.
 
-Pull requests should pass the **CI** workflow (see [RELEASING.md](RELEASING.md)).
+   For Python (after **`pip install -r python/requirements.txt -r python/requirements-dev.txt`** from the same directory):
 
-## Branch protection (maintainers)
+   ```bash
+   cd python && PYTHONPATH=. pytest tests/ -q
+   ```
 
-For an “enterprise-style” mainline, enable in GitHub: **Settings → Branches → Add rule** for `main`:
+   When you add a new **`python/app/*.py`** module, extend the **`py_compile`** list in **`.github/workflows/ci.yml`** (authoritative source) and mirror it in **[RELEASING.md](RELEASING.md)** local checks if you maintain that snippet.
 
-- Require a pull request before merging
-- Require status checks to pass before merging (add **CI** / `verify`)
-- Optionally: require reviews, disallow force pushes
+   If you **intentionally** shrink or grow the bundled **`skills/`** tree below/above the current CI minimum, update **`ci/bundle-gate.json`** (`minSkillMdFiles`) and note it in the PR—see **[RELEASING.md](RELEASING.md)**.
 
-This is configured in the GitHub UI; it is not stored in this repo.
+4. Open a **pull request** into **`main`** with:
+   - What changed and **why**  
+   - How you **verified** it (tests, manual MCP smoke, etc.)
 
-## Releases
+PRs should pass **CI** (see [RELEASING.md](RELEASING.md)).
 
-Maintainers: follow [RELEASING.md](RELEASING.md) for version bumps, tags, **`NPM_TOKEN`**, and npm **2FA**.
+## Branch protection (maintainers)
+
+For a protected **`main`**:
+
+- Require PRs before merge  
+- Require **CI** / `verify` to pass  
+- Optionally require reviews and disallow force-push  
 
-## Code of conduct
+Configured in **GitHub → Settings → Branches**; not stored in-repo.
+
+## Releases
 
-Please read [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md). Report problems to the maintainers.
+Maintainers: [RELEASING.md](RELEASING.md) (**semver**, tags, **`NPM_TOKEN`**, npm tokens).
 
-## Security
+## Conduct & security
 
-See [SECURITY.md](SECURITY.md) for vulnerability reporting.
+- [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)  
+- [SECURITY.md](SECURITY.md) for vulnerability reporting