@shivaedev/work-board 0.9.1 → 0.11.0

package/CHANGELOG.md

@@ -4,10 +4,39 @@
 
 ### Changed
 
+- Record agent-owned project editing and human-owned response content, practical
+  best-effort conflict handling, and deferred direct editing/undo in the delivery
+  plan. Ordinary file editing remains sufficient for agents; the approved D3
+  handoff convention is delivered in 0.10.0 below.
+- Build package JavaScript, declarations and source maps with TypeScript 7.
 - Remove document export and shareable artifact/packet generation from the vision
   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.11.0 - 2026-10-06
+
+### Added
+
+- Returned-result review combines explicitly linked work/criteria, reported status,
+  evidence and limitations with version-pinned human feedback. Request revision or
+  accept an exact report using existing attention/question directives and immutable
+  responses; no new source schema or writer.
+- Native navigation/live review, safe Markdown/Mermaid context and no-JavaScript
+  reading. Changed or moved reports qualify earlier feedback; missing evidence and
+  ambiguous history remain explicit. Recorded Git revisions are not compared with
+  the checkout and authored choices do not establish verified criteria.
+
+## 0.10.0 - 2026-10-06
+
+### Added
+
+- Local Markdown handoffs with reviewed source snapshots, explicit receipt states
+  and a copyable prompt for an existing agent session. Agents acknowledge using
+  ordinary file edits; preparing a handoff does not launch or wake an agent.
+- Native RPC preparation/history, draft persistence, safe rich context rendering,
+  no-JavaScript reading and native navigation. Reuse the opt-in Linux file
+  publisher; retries retain receipt rather than creating duplicate direction.
+
 ## 0.9.1 - 2026-10-06
 
 ### Fixed

package/README.md

@@ -62,9 +62,57 @@ preference says otherwise. A keyboard skip link moves directly to the content.
 | --- | --- | --- |
 | `<dir>` | required | The folder to serve. |
 | `--port` | `4747` | The port on `127.0.0.1`. `0` picks a free one. |
-| `--responses` | `false` | Explicitly enable local question/response writes. The first writer requires Linux, a real workspace directory, `/proc/self/fd`, hard links and directory synchronization. Reading remains available on other supported Node platforms. |
+| `--responses` | `false` | Explicitly enable local question/response/handoff writes. The first writer requires Linux, a real workspace directory, `/proc/self/fd`, hard links and directory synchronization. Reading remains available on other supported Node platforms. |
 | `--home` | none | The file shown at `/` as a board, relative to the folder. The command stops with an error unless it leads to one of the markdown files listed from the folder. Without it, `/` shows the first file as a document. |
 
+### Reviewing a returned result
+
+A file with `kind: result` and a unique stable ID offers **Review returned result**.
+The review page keeps its supplied result status separate from explicitly linked
+work status, lists this report's criterion-level claims and missing provenance,
+and shows the report, limitations and recorded human feedback together. The same
+page is available through a normal GET link without JavaScript.
+
+The agent declares an open attention request of kind `review` and can provide a
+rich Markdown question packet with choices such as request revision or accept
+this exact report. The human uses the existing response surface, previews and
+submits together. Choices and rationale are durable authored feedback pinned to
+that report's exact source SHA-256/path. Changed or moved reports qualify earlier
+feedback; malformed or duplicate records leave history unknown. Feedback does
+not automatically change work status or make missing criterion evidence pass.
+
+`evidence.checked_revision` remains a reported Git revision. This local reader
+does not compare it with the current checkout, so evidence freshness is unknown.
+See the [ordinary-file walkthrough](https://github.com/ShivaeDev/platform/blob/main/packages/work-board/docs/vision/delivery/result-review-examples.md).
+
+## Hand a task to an existing agent session
+
+Open a uniquely identified project item and choose **Prepare an agent handoff**.
+Review the current Markdown/Mermaid context, enter a local recipient label, goal,
+constraints and next action, then preview and prepare. The existing `--responses`
+opt-in also enables this writer. Work Board creates `handoffs/<id>.md` with a stable
+ID, direction, original source path/revision and the exact reviewed source below
+its frontmatter, including declared criteria. Context is limited to 256 KiB.
+
+**Copy tiny prompt** gives you a short instruction containing the absolute file
+path. Paste it into the agent session you already use. Preparing a file records
+`requested`; it does not wake or launch an agent. Without clipboard permission,
+the prompt is selected for manual copying. Saved handoffs remain readable without
+JavaScript; preparing them requires JavaScript and the existing Linux writer.
+
+The agent reads the file and edits `handoff.state` to `acknowledged`, `rejected`
+or `unavailable`, with optional `handoff.by` and `handoff.note`. These are literal
+local labels and receipt, independent of task status, execution or human
+acceptance. Agents can keep using the existing question poll/wait commands for
+human answers. No acknowledgment command or special project editor is required.
+
+Retries using the same handoff ID preserve the agent's receipt and extra metadata;
+conflicting direction, moved/duplicate IDs and a changed source before initial
+preparation are rejected. A missing receipt remains unconfirmed, including after
+restart. Saved context remains inspectable if the source disappears or changes.
+Drafts share the existing browser-local workspace store and its 30-day/2-MiB
+bounds; clearing that store clears response and handoff drafts together.
+
 ## Local responses and one logical wait per question
 
 Start one shared server with explicit write opt-in: