@plinth-music/cli 0.13.0 → 0.15.0
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 +52 -0
- package/dist/build-stamp.json +2 -2
- package/dist/cli.js +891 -160
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,58 @@
|
|
|
2
2
|
|
|
3
3
|
Notable changes to `@plinth-music/cli`. Grouped by what a user notices, not by PR.
|
|
4
4
|
|
|
5
|
+
## 0.15.0 - 2026-08-31
|
|
6
|
+
|
|
7
|
+
One code PR since `0.14.0` (`v0.14.0..f293dd0`, #153). A minor because sync gains a
|
|
8
|
+
refusal: there is now a case where Plinth declines to upload a file.
|
|
9
|
+
|
|
10
|
+
- ⚠️ **A memory file that looks like it carries a credential is held back instead of
|
|
11
|
+
synced.** The file is never modified and nothing is lost - it stays on your machine
|
|
12
|
+
until you decide. Plinth is not approved to store credentials, so it will not take one
|
|
13
|
+
without you saying so explicitly. Sharing one with your own team is not the problem and
|
|
14
|
+
the message does not treat it as one.
|
|
15
|
+
- **You clear it in one of two ways:** take the line out, or mark it `plinth-allow-secret`
|
|
16
|
+
on the line itself. The marker sits in the file where your teammates can see it, so an
|
|
17
|
+
allow is a decision on the record rather than a setting nobody can find.
|
|
18
|
+
- **`plinth status` names the file, the line and the remedy**, and the daemon logs it. The
|
|
19
|
+
finding is local only - it is never posted to your team, because "there is a key at line
|
|
20
|
+
42 of workspace-memory.md" is a pointer straight at the key.
|
|
21
|
+
- **It matches vendor-prefixed shapes only** (AWS, GitHub, Slack, Stripe, Google,
|
|
22
|
+
OpenAI/Anthropic, private-key blocks, JWTs, signed URLs). Recall is deliberately low:
|
|
23
|
+
this stops a recognisable token going up by accident, and it is not a guarantee against
|
|
24
|
+
a determined leak. Measured against every real memory file on the first workspace
|
|
25
|
+
(81,897 bytes across 12 files): no false positives.
|
|
26
|
+
- Covers `workspace-memory.md`, `user-memory.md` and `artists/<slug>/memory.md`.
|
|
27
|
+
|
|
28
|
+
⚠️ **The check runs under the daemon only.** `plinth sync` is pull-only and never scans, so
|
|
29
|
+
a workspace with no daemon running is not protected.
|
|
30
|
+
|
|
31
|
+
The desktop app pins `0.14.0` exact and picks none of this up until its own release repins.
|
|
32
|
+
|
|
33
|
+
## 0.14.0 - 2026-08-31
|
|
34
|
+
|
|
35
|
+
One code PR since `0.13.0` (`v0.13.0..50ab852`, #150; #149 was 0.13.0's own History row).
|
|
36
|
+
A minor because the generated workspace surface gains a whole section and `status` gains
|
|
37
|
+
three readouts.
|
|
38
|
+
|
|
39
|
+
- **Your workspace `CLAUDE.md` now carries a map of every file that guides the agent** -
|
|
40
|
+
path, who writes it, when it is read, how far it reaches, and its size bar. Generated
|
|
41
|
+
from the same constants the code uses, so it cannot drift from the behaviour.
|
|
42
|
+
- **Every guiding file has a size bar, and growth is visible before the bar.** `plinth
|
|
43
|
+
status` shows each file's size and its change since your last session end, reports
|
|
44
|
+
over-bar files with the generated and member shares stated separately, and names
|
|
45
|
+
over-long memory index lines as split candidates - never cuts.
|
|
46
|
+
- **You hear about it when you are actually there.** One line at session start, only when
|
|
47
|
+
a file YOU can act on is past its bar, and `/plinth:start` offers the trim (also after
|
|
48
|
+
30 quiet days when there is something to propose). Nothing fires when nothing is over,
|
|
49
|
+
and nothing is ever trimmed for you.
|
|
50
|
+
- `plinth session end --trimmed` records a trim so the offer stands down.
|
|
51
|
+
- ⚠️ Plinth's own `close.md` body currently renders OVER the very bar this release ships,
|
|
52
|
+
and `status` says so honestly - the trim of Plinth's text is Plinth's owed work, and the
|
|
53
|
+
session-start line never nags you about files only Plinth can fix.
|
|
54
|
+
|
|
55
|
+
The desktop app pins `0.13.0` exact and picks none of this up until its own release repins.
|
|
56
|
+
|
|
5
57
|
## 0.13.0 - 2026-08-30
|
|
6
58
|
|
|
7
59
|
Four code PRs since `0.12.0` (`v0.12.0..07a74f8`, #144-#147; #143 is 0.12.0's own History row).
|
package/dist/build-stamp.json
CHANGED