Kjell Tore Guttormsen
677eab9294
A1-10 + D-5. The queue answers "what is scheduled"; nothing answered "is the week covered, and what is still being written". N13 makes both readable at session start. - Publishing slots are operator config: profile/publishing-slots.json in the per-user data dir, schema + OPT-IN template in config/publishing-slots.template.json. The plugin ships no publishing times and writes the grid for nobody; absent config means every slot surface stays silent (same never-nag discipline as the trend/brain nudges). Data dir rather than the state file, which is machine-written and whose frontmatter reader does not parse lists. - hooks/scripts/slots.mjs (new): one implementation behind four surfaces. Zero-dep (a SessionStart hook must not spawn tsx), pure core (dates in as strings, no clock), imported by the commands exactly as queue-manager.mjs already is — so session-start's vacancy warning and Step 10's slot default cannot drift apart. - Coverage counts the short-form queue (scheduled/published; cancelled frees the slot) AND editions-register rows claiming that date, counted per date, so long-form and short-form cannot be double-booked and a two-slot day needs two posts. - Session start gains "## Editions in Flight" (series, phase, next action, claimed slot, days in flight) and "## Publishing Slots" (next open slot, open count in 14 days, and how to fill it when the gap is <=3 days). The existing discovery nudge is untouched. - /linkedin router + /linkedin:calendar surface the same roll-up; calendar documents the opt-in copy. /linkedin:newsletter Step 10 defaults to the next open slot (one confirmation, not an interview) and writes --slot onto the register row. - D-5: references/scheduling-strategy.md marked "confidence: low / directional" per the algorithm reference's own standard, deferring to the operator's grid and their own analytics. Neutral example time replaces the operator-specific one in the N12 docs. TDD: red proven first (module absent; 5 session-start behaviours failing). hooks 140 -> 174 · test-runner 184 -> 197 (Section 16t: 13 unconditional greps incl. a de-niche check that no publishing time is hardcoded in the slot path and no operator grid is committed, + non-vacuity self-test; anti-erosion floor 166 -> 179). Suites green: trends 300/0 · brain 134/0 · editions 72/0 · specifics-bank 45/0 · tests 35/0 · render 60/0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QxvWAjte7vPcF79QeSRvRJ
16 lines
2.1 KiB
JSON
16 lines
2.1 KiB
JSON
{
|
|
"_doc": {
|
|
"purpose": "Schema for publishing-slots.json (N13 / A1-10) — the recurring weekly slots you publish in. Session start reads it to name the next slot nothing covers yet, /linkedin:calendar shows the grid, and /linkedin:newsletter Step 10 defaults its scheduling to the next open slot instead of asking.",
|
|
"install": "OPT-IN — the plugin never writes this file for you and imposes no schedule. Copy it into your data dir and edit the times: cp \"${CLAUDE_PLUGIN_ROOT}/config/publishing-slots.template.json\" \"${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/profile/publishing-slots.json\". While the file is absent, every slot surface stays silent.",
|
|
"slots": "Recurring weekly slots: day = a weekday, either three-letter (mon/tue/wed/thu/fri/sat/sun) or spelled out; time = 24-hour HH:MM (zero-padded). label is free text shown next to the slot (e.g. which format usually goes there). Unparseable rows are dropped rather than throwing — a typo costs you that slot, not your session start.",
|
|
"timezone": "IANA zone the times are meant in, e.g. \"Europe/Oslo\" or \"America/New_York\". Recorded for your own clarity and displayed as-is; the plugin does not convert times (it schedules in your local wall clock, like the queue).",
|
|
"coverage": "A slot counts as covered when something lands on that date: a queue entry with status scheduled or published (/linkedin:batch, /linkedin:quick, Step 10 of an edition), or an editions-register row whose slot claims that date. Cancelled entries free the slot again. A day carrying two slots needs two posts to be full.",
|
|
"defaults": "The times below are the plugin's own DIRECTIONAL 2x/week starting point (references/scheduling-strategy.md — confidence: low / directional, no primary source). They are a hypothesis to test, not a recommendation about your audience. Replace them with what your own analytics show (/linkedin:report, /linkedin:analyze)."
|
|
},
|
|
"schemaVersion": 1,
|
|
"timezone": "",
|
|
"slots": [
|
|
{ "day": "tue", "time": "08:30", "label": "" },
|
|
{ "day": "thu", "time": "12:00", "label": "" }
|
|
]
|
|
}
|