open/linkedin-studio
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity Actions

feat(linkedin-studio): M0 — per-user external data dir (v0.5.0)

Browse source
This commit is contained in:
Kjell Tore Guttormsen 2026-06-18 13:17:35 +02:00
commit 55ec0edff9
5 changed files with 41 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/m0/log.md
View file

@ -89,6 +89,24 @@ after the default flipped external (the exact M3 failure). Dropped all 5 (surgic
only the `ANALYTICS_ROOT=… ` prefix, kept the `node --import tsx` form — no CLI-style change),
matching how Step 11 left the commands. Lint now **81/0**.
### Step 18 — release 0.4.0 → 0.5.0 (minor, non-breaking)
Bumped `.claude-plugin/plugin.json` + the three lint-grepped literals (README
`version-0.5.0-blue` badge, CLAUDE.md `(v0.5.0)` header, CHANGELOG `## [0.5.0]`).
Also synced the README `reference_docs-25→26` badge (not lint-checked, but stale after
the convention doc) and refreshed the now-false "user data still lives inside the plugin"
prose in README + CLAUDE.md to "M0 done — data external." Version-consistency lint green;
the only remaining `0.4.0` refs are CHANGELOG history + the `docs/m0/` planning docs that
describe the `0.4.0 → 0.5.0` transition itself (correct, not stale declarations).
**Plan deviation — root marketplace docs NOT touched (scope).** Plan Step 18 listed
`/Users/ktg/.claude/plugins/marketplaces/ktg-plugin-marketplace/{README,CLAUDE}.md` as
"root docs." Skipped: that path is the **installed** marketplace artifact, **outside this
polyrepo**, and STATE.md scope is "KUN denne pluginnen" (+ global "don't write in other
repos"). The binding gate (the lint) checks only this plugin's four declarations, all
green. **Follow-up (separate catalog repo task):** reflect linkedin-studio v0.5.0 in the
marketplace catalog README if/when desired — operator's call, not this plugin's M0.
## Session 3 — Steps 11–13 (2026-06-18)
### Environment reality vs. plan assumptions