@shivaedev/work-board 0.8.0 → 0.9.1

package/CHANGELOG.md

@@ -8,6 +8,35 @@
   and delivery scope. Keep onboarding/report templates and linked in-app review.
 - Record the approved Platform-first live client direction and its actual shared HTTP/browser fixture evidence; Work Board adopts that foundation in 0.5.0 below.
 
+## 0.9.1 - 2026-10-06
+
+### Fixed
+
+- Treat syntactically damaged frontmatter in the published responses/ record
+  namespace as unknown history, including unterminated headers. Do not mistake
+  unreadable feedback for an empty response list or an unanswered deadline.
+  Ordinary Markdown outside that namespace retains its reading compatibility.
+
+## 0.9.0 - 2026-10-06
+
+### Added
+
+- Agent-authored question directives with rich Markdown/Mermaid context, single-
+  and multiple-choice controls, open-text prompts and additional human text.
+  Submit one validated packet through the existing native response/wait path;
+  record optional typed answers alongside a readable Markdown account.
+- Explicit superseding responses with linked immutable history. Qualify earlier
+  reviewed contexts and preserve draft text/recovery while clearing selections
+  after a source edit or move. Keep legacy question/response files valid.
+
+### Changed
+
+- Render response context and history through the existing Markdown pipeline with
+  raw HTML disabled, retaining local strict Mermaid and no-JavaScript source
+  fallback. Resolve template links against the source before recording answers.
+- Scope in-memory drafts and their clearing to the workspace as well as persisted
+  storage. Keep existing retention, write opt-in, Linux publisher and wait limits.
+
 ## 0.8.0 - 2026-10-06
 
 ### Added

package/README.md

@@ -130,6 +130,8 @@ recovery, not exactly-once agent action. The server's 30-second request leases a
 one-second reconciliation checks are distinct from the human's 48-hour deadline.
 During a transport/index outage, waits retry the same question; at the deadline,
 an unavailable service is reported as unavailable rather than falsely unanswered.
+Damaged frontmatter in the `responses/` record namespace also makes history
+unavailable; repair the record before treating its question as unanswered.
 
 The client uses bundled native Effect RPC over the existing local command path.
 Serving imports are loaded only for the server command. Each waiter has no
@@ -152,7 +154,8 @@ produce an uncertain result; reconcile saved source before retrying.
 
 Source HTML cannot submit write forms: CSP disables form actions/frames, the
 native route requires same-origin/loopback and NDJSON when writes are enabled,
-and the official response surface escapes the reviewed source. Embedded apps must
+and the official response surface renders reviewed context with raw HTML disabled,
+with an escaped exact-source disclosure. Embedded apps must
 explicitly opt in with `boardLayer({ root, responses: true })` and own the trusted
 host boundary. There is no write endpoint for arbitrary paths or source rewriting.
 
@@ -512,3 +515,19 @@ unknown, invalid components retain their source with a diagnostic, and timelines
 preserve authored order. Recorded values do not establish verified acceptance.
 See [the complete source conventions](./docs/vision/delivery/visual-document-examples.md).
 GitHub alert blockquotes render as callouts; comparisons remain ordinary GFM tables.
+
+## Rich question packets
+
+Agents can prepare Markdown context with `question`/`option` directives and local
+Mermaid diagrams. People select options, always add text, and submit the whole
+packet once. Use `select="one"`, `select="many"` or `select="text"`; choices start
+unselected and a text-only answer can reject the framing. Preview the complete
+record before saving. The existing wait returns typed prompt/option IDs and human
+text with the readable Markdown and exact reviewed context.
+
+See [the full source example and contract](docs/vision/delivery/decision-write-examples.md).
+Ordinary Markdown and older response files still work. Decisions are authored
+feedback; superseding direction is explicit and does not establish acceptance or
+change tasks. Response-page raw HTML is disabled. Local strict Mermaid and
+no-JavaScript readable history/source fallback use the existing renderer; recording
+requires JavaScript and `--responses`. Linux-only write support is unchanged.