@shinobiapps/shinobi 0.1.2 → 0.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (36) hide show
  1. package/CHANGELOG.md +68 -11
  2. package/CODE_OF_CONDUCT.md +1 -1
  3. package/README.md +369 -271
  4. package/SECURITY.md +1 -1
  5. package/dist/cli.js +29 -24
  6. package/dist/cli.js.map +1 -1
  7. package/dist/commands/init.d.ts +2 -0
  8. package/dist/commands/init.d.ts.map +1 -1
  9. package/dist/commands/init.js +41 -21
  10. package/dist/commands/init.js.map +1 -1
  11. package/dist/dashboard/auth.js +5 -5
  12. package/dist/dashboard-spa/assets/{index-BiTX3zpZ.js → index-BgInVUB2.js} +2 -2
  13. package/dist/dashboard-spa/assets/{index-BiTX3zpZ.js.map → index-BgInVUB2.js.map} +1 -1
  14. package/dist/dashboard-spa/assets/index-h7KmljOs.css +1 -0
  15. package/dist/dashboard-spa/index.html +2 -2
  16. package/dist/lib/migrations.js +6 -6
  17. package/dist/lib/priority.js +6 -6
  18. package/dist/models/activity.js +2 -2
  19. package/dist/models/context.js +2 -2
  20. package/dist/models/dead_ends.js +11 -11
  21. package/dist/models/decisions.js +15 -15
  22. package/dist/models/notes.js +6 -6
  23. package/dist/models/plans.js +2 -2
  24. package/dist/models/projects.d.ts +2 -0
  25. package/dist/models/projects.d.ts.map +1 -1
  26. package/dist/models/projects.js +51 -24
  27. package/dist/models/projects.js.map +1 -1
  28. package/dist/models/sessions.js +23 -23
  29. package/dist/models/subtasks.js +19 -19
  30. package/dist/services/embedding/store.js +5 -5
  31. package/docs/architecture.md +108 -108
  32. package/docs/configuration.md +73 -73
  33. package/docs/plugin-development.md +104 -104
  34. package/docs/sponsorship.md +1 -1
  35. package/package.json +97 -97
  36. package/dist/dashboard-spa/assets/index-CrKsQshV.css +0 -1
package/CHANGELOG.md CHANGED
@@ -5,20 +5,68 @@ All notable changes to Shinobi will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
- ## [0.1.2] — 2026-05-28
8
+ ## [0.1.4] — 2026-06-04
9
9
 
10
- ### Fixed
10
+ Dashboard quality-of-life: project list now shows subtask completion at a glance.
11
11
 
12
- - `/health` endpoint returning hardcoded `"0.1.0"` instead of the installed
13
- package version. Root cause: the published `0.1.1` tarball shipped a stale
14
- `dist/` containing both an older hardcoded `/health` route and the
15
- corrected one — Hono matches the first match, so the hardcode won.
16
- - Added `prepublishOnly` script that wipes `dist/` and runs a clean rebuild
17
- so a stale-artifact publish cannot recur.
12
+ ### Added
13
+
14
+ - **Project progress bar in the dashboard table.** New "Progress" column
15
+ renders a slim bar plus `done/total · %` text next to every project.
16
+ Color tier: emerald when 100% done, accent when ≥ 50%, amber under 50%,
17
+ em dash when the project has no subtasks. `role="progressbar"` with
18
+ `aria-valuenow` for screen readers.
19
+ - **Backend exposes `subtasks_total` + `subtasks_done` on every project
20
+ read path.** `listProjects`, `getProject`, and `projectsMatchingTargetPath`
21
+ now LEFT JOIN a subtask aggregate subquery and surface both counts on
22
+ the `Project` type. The `/api/projects` endpoint returns them without
23
+ any extra round-trips.
24
+
25
+ ### Why
26
+
27
+ The project list used to show only `project.status` (`todo` / `in_progress`
28
+ / `done`), which is operator-set and frequently lags behind the real subtask
29
+ state — projects sat at "todo" while every subtask was already done. Users
30
+ had to drill into each project just to see whether work was actually
31
+ finished. The progress column closes that loop without changing the
32
+ operator-controlled status semantics.
33
+
34
+ ## [0.1.3] — 2026-05-29
35
+
36
+ Pre-launch polish: multi-client MCP bootstrap.
37
+
38
+ ### Added
39
+
40
+ - **`shinobi init` now configures Cursor in addition to Claude Code.**
41
+ Writes `<workspace>/.cursor/mcp.json` alongside `<workspace>/.mcp.json`,
42
+ both using the absolute-path form (`command: <node>`, `args: [<cli.js>,
43
+ "mcp"]`) so they survive shell-less spawns on Windows.
44
+ - **`shinobi init --print-config`** emits the MCP server JSON snippet to
45
+ stdout for clients that do not respect workspace MCP files (Cline,
46
+ Continue.dev, Zed). Pipe / paste into the relevant config.
47
+ - **README "MCP client setup" section** with paste-ready file paths and
48
+ config snippets for all five clients (Claude Code, Cursor, Cline,
49
+ Continue.dev, Zed), plus the explicit warning that bare `shinobi`
50
+ command does not work in MCP configs because clients spawn with
51
+ `shell: false`.
52
+
53
+ ### Why
54
+
55
+ The 0.1.2 init silently only helped Claude Code users. Cursor / Cline /
56
+ Continue / Zed users would install Shinobi, run `shinobi init`, restart
57
+ their client, see no `mcp__shinobi__*` tools, and conclude it was
58
+ broken. Caught during pre-launch audit.
59
+
60
+ ## [0.1.2] — 2026-05-28
18
61
 
19
- ## [0.1.1] — 2026-06-03
62
+ First publicly installable release.
20
63
 
21
- First public release.
64
+ (Note: `0.1.1` was published earlier the same day but shipped a stale
65
+ `dist/` that left an older hardcoded `/health` route alongside the
66
+ corrected one. Hono matched the hardcode first, so the endpoint always
67
+ returned `version: "0.1.0"`. `0.1.2` is the immediate hotfix and the
68
+ de-facto launch artifact. The launch announcement on Product Hunt /
69
+ Hacker News is scheduled for **2026-06-03**.)
22
70
 
23
71
  ### Added
24
72
 
@@ -69,6 +117,15 @@ First public release.
69
117
  - **Forward-only SQL migrations** with checksum verification and adopt /
70
118
  dry-run / verify CLI flags.
71
119
 
120
+ ### Fixed (relative to the broken 0.1.1 publish)
121
+
122
+ - `/health` endpoint returning hardcoded `"0.1.0"` instead of the
123
+ installed version. Root cause: the 0.1.1 tarball shipped a stale
124
+ `dist/` containing both an older hardcoded `/health` route and the
125
+ corrected one — Hono matches the first match, so the hardcode won.
126
+ - Added `prepublishOnly` script that wipes `dist/` and runs a clean
127
+ rebuild before every publish, so a stale-artifact publish cannot recur.
128
+
72
129
  ### Distribution
73
130
 
74
131
  - `npm install -g @shinobiapps/shinobi` installs the CLI globally.
@@ -88,4 +145,4 @@ First public release.
88
145
  chain (esbuild via vite via vitest, dev server only — not in the
89
146
  shipped runtime). Tracked for v0.2 vite upgrade.
90
147
 
91
- [0.1.1]: https://github.com/numbererikson/shinobi/releases/tag/v0.1.1
148
+ [0.1.2]: https://github.com/numbererikson/shinobi/releases/tag/v0.1.2
@@ -46,7 +46,7 @@ Instances of unacceptable behavior may be reported to the project
46
46
  maintainer at:
47
47
 
48
48
  ```
49
- contact@shinobi-apps.hr
49
+ contact@shinobi-apps.com
50
50
  ```
51
51
 
52
52
  All complaints will be reviewed and investigated promptly and fairly. The