diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json index 4423fe5..aaccbc7 100644 --- a/.claude-plugin/plugin.json +++ b/.claude-plugin/plugin.json @@ -2,7 +2,7 @@ "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json", "name": "sitrep-panel", "description": "A live local HTML report Claude keeps updated as it works — status board, running narrative, screenshots, newest-first log — so you can watch progress without reading the transcript.", - "version": "1.0.0", + "version": "1.1.0", "author": { "name": "Dave" }, diff --git a/AGENTS.md b/AGENTS.md index 2086888..a72bdce 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -81,16 +81,22 @@ Update it at every real step: what you're doing right now and *why*. Replace the block's content each time; it always reflects the present, not history. 2. **Prepend a new log entry** to `#entries` (newest-first — insert right - after the `
` opening tag). One entry per real step: - what happened, what was decided and why, what was verified. Skip entries - for trivial reads; log entries for writes, decisions, and verification. + after the `
` opening tag), using the exact `.entry` / + `.entry-rail` / `.entry-dot` markup shown in the template's commented + example — the timeline rail depends on that structure. One entry per real + step: what happened, what was decided and why, what was verified. Skip + entries for trivial reads; log entries for writes, decisions, and + verification. 3. **Save screenshots** into `.sitrep-panel/report/screenshots/` and reference them with a relative `` — inline in a log entry, appended to `#shots-body`, or both. -4. **Update the board** (`#board`) — add/move/remove `.board-card` elements - as steps start, block, or finish. See the commented example markup in - the template for the exact class names (`status-todo` / - `status-progress` / `status-done` / `status-blocked`). +4. **Update the board** — the board is four columns, each with its own + container: `#board-todo`, `#board-progress`, `#board-done`, + `#board-blocked`. Add/move/remove a plain `
…
` + in the container matching its current status as steps start, block, or + finish — moving a card means removing it from one column's container and + appending it to another's, not changing a class. See the commented + example markup in the template. 5. **Touch `meta.json` last, always.** Rewrite `updated_at` to the current ISO-8601 UTC timestamp as the final write of every update — the page polls this file every 2s and reloads on change. This is the one step diff --git a/README.md b/README.md index 1a5f739..60607f7 100644 --- a/README.md +++ b/README.md @@ -30,10 +30,10 @@ everything is one static HTML page plus a stdlib Python server. ## What it shows -- **Status board** — cards for what's to do, in progress, done, or blocked. - Synced from a connected issue tracker (Jira, GitHub Issues, Linear — - whatever the agent already has access to) when one's available, otherwise - a plain checklist the agent maintains by hand. Never fabricated. +- **Status board** — four columns: to do, in progress, done, blocked. Synced + from a connected issue tracker (Jira, GitHub Issues, Linear — whatever the + agent already has access to) when one's available, otherwise a plain + checklist the agent maintains by hand. Never fabricated. - **What's happening now** — a standing paragraph of *why*, not a status word. Replaced each update, always reflecting the present. - **Screenshots** — dropped in as they're taken, inline in the log or in @@ -102,6 +102,10 @@ package files; CI runs it plus a real server-start smoke test on every PR. ## Versions +- **1.1.0** — redesign: light mode by default with a real theme toggle (no + more silent OS-based switching), a small wordmark, the status board + regrouped into kanban-style columns instead of a loose card grid, and a + sticky section nav for wayfinding without hiding anything. - **1.0.0** — initial release: status board, live "what's happening now" narrative, screenshot gallery, newest-first log, live-reload, optional tracker-synced board. diff --git a/SKILL.md b/SKILL.md index 6a77d23..90c894a 100644 --- a/SKILL.md +++ b/SKILL.md @@ -9,7 +9,7 @@ description: | or wants visibility into a multi-step task as it happens. license: MIT metadata: - version: "1.0.0" + version: "1.1.0" --- # sitrep-panel @@ -100,17 +100,22 @@ the start is worthless. Update it at every real step, not just at the end: present, not history. 2. **Prepend a new log entry** to `#entries` (newest-first — insert right after the `
` opening tag, before whatever was already - there). One entry per real step: what happened, what you decided and why, - what you verified. Skip entries for trivial reads; log entries for - writes, decisions, and verification results. + there), using the exact `.entry` / `.entry-rail` / `.entry-dot` markup + shown in the template's commented example — the timeline rail depends on + that structure. One entry per real step: what happened, what you decided + and why, what you verified. Skip entries for trivial reads; log entries + for writes, decisions, and verification results. 3. **Save screenshots** into `.sitrep-panel/report/screenshots/` and reference them with a relative `` — either inline in a log entry, or appended to `#shots-body` (or both, when a screenshot is the standout evidence for a step). -4. **Update the board** (`#board`) — add/move/remove `.board-card` elements - as steps start, block, or finish. See the commented example markup - already in the template for the exact class names - (`status-todo` / `status-progress` / `status-done` / `status-blocked`). +4. **Update the board** — the board is four columns, each with its own + container: `#board-todo`, `#board-progress`, `#board-done`, + `#board-blocked`. Add/move/remove a plain `
…
` + in the container matching its current status as steps start, block, or + finish — moving a card means removing it from one column's container and + appending it to another's, not changing a class. See the commented + example markup in the template. 5. **Touch `meta.json` last, always.** Rewrite `updated_at` to the current ISO-8601 UTC timestamp as the final write of every update — the page polls this file every 2s and reloads on change, so writing it before the @@ -123,7 +128,7 @@ If the project has a working issue tracker connection available to you right now (an already-connected Atlassian/Jira MCP, `gh issue list` for a GitHub repo, a connected Linear MCP, etc.) **and** there are real tickets relevant to this task, render the board from that real data — real ticket key, real -title, real link, real status mapped to the four status classes. Refresh it +title, real link, real status mapped to the matching column. Refresh it each time you update the doc, the same as everything else. If no tracker is connected, or nothing relevant is filed there, fall back to diff --git a/assets/template.html b/assets/template.html index 4e45010..c59792e 100644 --- a/assets/template.html +++ b/assets/template.html @@ -3,49 +3,85 @@ - + {{TITLE}} — sitrep-panel -
-
+
+
+ + sitrep-panel +
+ +
+ +

{{TITLE}}

{{SUBTITLE}}

just started
-
-
-
+

What's happening now

+

What's actually happening, in plain language — not just a status word.

Nothing yet — this fills in once work starts.

-
+

Screenshots

+

Visual proof, dropped in as it happens.

-
+

Log (newest first)

+

Everything that's happened, in order.

@@ -210,6 +327,62 @@