@shinobiapps/shinobi 0.1.3 → 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.
- package/CHANGELOG.md +26 -0
- package/CODE_OF_CONDUCT.md +1 -1
- package/README.md +369 -368
- package/SECURITY.md +1 -1
- package/dist/cli.js +24 -24
- package/dist/commands/init.js +11 -11
- package/dist/dashboard/auth.js +5 -5
- package/dist/dashboard-spa/assets/{index-BiTX3zpZ.js → index-BgInVUB2.js} +2 -2
- package/dist/dashboard-spa/assets/{index-BiTX3zpZ.js.map → index-BgInVUB2.js.map} +1 -1
- package/dist/dashboard-spa/assets/index-h7KmljOs.css +1 -0
- package/dist/dashboard-spa/index.html +2 -2
- package/dist/lib/migrations.js +6 -6
- package/dist/lib/priority.js +6 -6
- package/dist/models/activity.js +2 -2
- package/dist/models/context.js +2 -2
- package/dist/models/dead_ends.js +11 -11
- package/dist/models/decisions.js +15 -15
- package/dist/models/notes.js +6 -6
- package/dist/models/plans.js +2 -2
- package/dist/models/projects.d.ts +2 -0
- package/dist/models/projects.d.ts.map +1 -1
- package/dist/models/projects.js +51 -24
- package/dist/models/projects.js.map +1 -1
- package/dist/models/sessions.js +23 -23
- package/dist/models/subtasks.js +19 -19
- package/dist/services/embedding/store.js +5 -5
- package/docs/architecture.md +108 -108
- package/docs/configuration.md +73 -73
- package/docs/plugin-development.md +104 -104
- package/docs/sponsorship.md +1 -1
- package/package.json +97 -97
- package/dist/dashboard-spa/assets/index-CrKsQshV.css +0 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,32 @@ 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.4] — 2026-06-04
|
|
9
|
+
|
|
10
|
+
Dashboard quality-of-life: project list now shows subtask completion at a glance.
|
|
11
|
+
|
|
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
|
+
|
|
8
34
|
## [0.1.3] — 2026-05-29
|
|
9
35
|
|
|
10
36
|
Pre-launch polish: multi-client MCP bootstrap.
|
package/CODE_OF_CONDUCT.md
CHANGED