@shivaedev/work-board 0.12.0 → 0.14.0

package/dist/server/views/state.js

@@ -1,45 +1,12 @@
-import { Option, Schema } from "effect";
-const View = Schema.Literals(["board", "table"]);
-const Sort = Schema.Literals(["title", "owner", "status"]);
-export const State = Schema.Struct({
-    board: Schema.String,
-    item: Schema.String,
-    owner: Schema.String,
-    query: Schema.String,
-    sort: Sort,
-    status: Schema.String,
-    view: View,
-});
+import { fieldFilter as filter, stateOf as readState, viewUrl as urlOf, State as ViewState } from "#browser/views/state.ts";
+export const State = ViewState;
 export function stateOf(url) {
-    const params = new URL(url, "http://127.0.0.1").searchParams;
-    return {
-        board: params.get("board") ?? "",
-        item: params.get("item") ?? "",
-        owner: params.get("owner") ?? "",
-        query: (params.get("q") ?? "").slice(0, 200),
-        sort: Option.getOrElse(Schema.decodeUnknownOption(Sort)(params.get("sort")), () => "title"),
-        status: params.get("status") ?? "",
-        view: Option.getOrElse(Schema.decodeUnknownOption(View)(params.get("view")), () => "board"),
-    };
+    return readState(url);
 }
 export function viewUrl(state, changes = {}, hash = "") {
-    const next = { ...state, ...changes };
-    const params = new URLSearchParams({ view: next.view });
-    for (const [key, value] of Object.entries({
-        board: next.board,
-        item: next.item,
-        owner: next.owner,
-        q: next.query,
-        sort: next.sort,
-        status: next.status,
-    })) {
-        if (value) {
-            params.set(key, value);
-        }
-    }
-    return `/_board/work?${params}${hash ? `#${hash}` : ""}`;
+    return urlOf(state, changes, hash);
 }
 export function fieldFilter(value) {
-    return value === undefined ? "missing" : `value:${value}`;
+    return filter(value);
 }
 //# sourceMappingURL=state.js.map

package/dist/server/views/state.js.map

@@ -1 +1 @@
-{"version":3,"file":"state.js","sourceRoot":"","sources":["../../../src/server/views/state.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,QAAQ,CAAC;AAExC,MAAM,IAAI,GAAG,MAAM,CAAC,QAAQ,CAAC,CAAC,OAAO,EAAE,OAAO,CAAC,CAAC,CAAC;AACjD,MAAM,IAAI,GAAG,MAAM,CAAC,QAAQ,CAAC,CAAC,OAAO,EAAE,OAAO,EAAE,QAAQ,CAAC,CAAC,CAAC;AAC3D,MAAM,CAAC,MAAM,KAAK,GAAG,MAAM,CAAC,MAAM,CAAC;IAClC,KAAK,EAAE,MAAM,CAAC,MAAM;IACpB,IAAI,EAAE,MAAM,CAAC,MAAM;IACnB,KAAK,EAAE,MAAM,CAAC,MAAM;IACpB,KAAK,EAAE,MAAM,CAAC,MAAM;IACpB,IAAI,EAAE,IAAI;IACV,MAAM,EAAE,MAAM,CAAC,MAAM;IACrB,IAAI,EAAE,IAAI;CACV,CAAC,CAAC;AAGH,MAAM,UAAU,OAAO,CAAC,GAAW;IAClC,MAAM,MAAM,GAAG,IAAI,GAAG,CAAC,GAAG,EAAE,kBAAkB,CAAC,CAAC,YAAY,CAAC;IAC7D,OAAO;QACN,KAAK,EAAE,MAAM,CAAC,GAAG,CAAC,OAAO,CAAC,IAAI,EAAE;QAChC,IAAI,EAAE,MAAM,CAAC,GAAG,CAAC,MAAM,CAAC,IAAI,EAAE;QAC9B,KAAK,EAAE,MAAM,CAAC,GAAG,CAAC,OAAO,CAAC,IAAI,EAAE;QAChC,KAAK,EAAE,CAAC,MAAM,CAAC,GAAG,CAAC,GAAG,CAAC,IAAI,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,EAAE,GAAG,CAAC;QAC5C,IAAI,EAAE,MAAM,CAAC,SAAS,CAAC,MAAM,CAAC,mBAAmB,CAAC,IAAI,CAAC,CAAC,MAAM,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC,EAAE,GAAG,EAAE,CAAC,OAAO,CAAC;QAC3F,MAAM,EAAE,MAAM,CAAC,GAAG,CAAC,QAAQ,CAAC,IAAI,EAAE;QAClC,IAAI,EAAE,MAAM,CAAC,SAAS,CAAC,MAAM,CAAC,mBAAmB,CAAC,IAAI,CAAC,CAAC,MAAM,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC,EAAE,GAAG,EAAE,CAAC,OAAO,CAAC;KAC3F,CAAC;AACH,CAAC;AACD,MAAM,UAAU,OAAO,CAAC,KAAY,EAAE,OAAO,GAAmB,EAAE,EAAE,IAAI,GAAG,EAAE;IAC5E,MAAM,IAAI,GAAG,EAAE,GAAG,KAAK,EAAE,GAAG,OAAO,EAAE,CAAC;IACtC,MAAM,MAAM,GAAG,IAAI,eAAe,CAAC,EAAE,IAAI,EAAE,IAAI,CAAC,IAAI,EAAE,CAAC,CAAC;IACxD,KAAK,MAAM,CAAC,GAAG,EAAE,KAAK,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC;QACzC,KAAK,EAAE,IAAI,CAAC,KAAK;QACjB,IAAI,EAAE,IAAI,CAAC,IAAI;QACf,KAAK,EAAE,IAAI,CAAC,KAAK;QACjB,CAAC,EAAE,IAAI,CAAC,KAAK;QACb,IAAI,EAAE,IAAI,CAAC,IAAI;QACf,MAAM,EAAE,IAAI,CAAC,MAAM;KACnB,CAAC,EAAE,CAAC;QACJ,IAAI,KAAK,EAAE,CAAC;YACX,MAAM,CAAC,GAAG,CAAC,GAAG,EAAE,KAAK,CAAC,CAAC;QACxB,CAAC;IACF,CAAC;IACD,OAAO,gBAAgB,MAAM,GAAG,IAAI,CAAC,CAAC,CAAC,IAAI,IAAI,EAAE,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC;AAC1D,CAAC;AACD,MAAM,UAAU,WAAW,CAAC,KAAyB;IACpD,OAAO,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,SAAS,KAAK,EAAE,CAAC;AAC3D,CAAC"}
+{"version":3,"file":"state.js","sourceRoot":"","sources":["../../../src/server/views/state.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,WAAW,IAAI,MAAM,EAAE,OAAO,IAAI,SAAS,EAAE,OAAO,IAAI,KAAK,EAAE,KAAK,IAAI,SAAS,EAAE,MAAM,yBAAyB,CAAC;AAC5H,MAAM,CAAC,MAAM,KAAK,GAAG,SAAS,CAAC;AAE/B,MAAM,UAAU,OAAO,CAAC,GAAW;IAClC,OAAO,SAAS,CAAC,GAAG,CAAC,CAAC;AACvB,CAAC;AACD,MAAM,UAAU,OAAO,CAAC,KAAY,EAAE,OAAO,GAAmB,EAAE,EAAE,IAAI,GAAG,EAAE;IAC5E,OAAO,KAAK,CAAC,KAAK,EAAE,OAAO,EAAE,IAAI,CAAC,CAAC;AACpC,CAAC;AACD,MAAM,UAAU,WAAW,CAAC,KAAyB;IACpD,OAAO,MAAM,CAAC,KAAK,CAAC,CAAC;AACtB,CAAC"}

package/docs/delivery/attention-examples.md

@@ -9,13 +9,13 @@ attention:
   - id: keyboard-review
     kind: review
     state: open
-    response_from: [marvin]
+    response_from: [maintainer]
     reason: Review the recorded keyboard evidence before continuing.
     unblocks: [work.search#keyboard]
   - id: matching-decision
     kind: decision
     state: open
-    response_from: [marvin]
+    response_from: [maintainer]
     reason: Choose literal matching or fuzzy matching for the next checkpoint.
     unblocks: [decision.search-matching]
 ```
@@ -61,8 +61,8 @@ The overview groups decisions, reviews and blockers with visible counts, then or
 
 ## Ambiguity and quiet examples
 
-- `status: in-review` with `owner: marvin` and no attention list: no request.
-- `next_action: Ask Marvin`, a finished run, or repeated edits: no request.
+- `status: in-review` with `owner: maintainer` and no attention list: no request.
+- `next_action: Ask Maintainer`, a finished run, or repeated edits: no request.
 - Two `keyboard-review` records on one item: neither wins; show a source issue.
 - Two items with the same ID: do not assign either item's requests.
 - `unblocks: [missing.id]`: show a source issue outside the actionable queue; keep the request readable in its original file.

package/docs/delivery/browser-acceptance.md

@@ -26,8 +26,8 @@ Open the printed URL in a real browser. Record the browser/version, viewport, ac
 2. Reload, press Tab, then Enter on **Skip to content**. Focus moves to the main content. Tab through Files, Theme, Density, folder summaries, and file links; focus must be visible. Open a nested document and check its file location.
 3. Select Dark and Compact, collapse Files, then reload and open another file. All three choices persist. Select Light with the operating system in dark mode; code colors and diagrams follow Light. Return to System and switch the system scheme; diagrams redraw. Changing density alone must not redraw them.
 4. Open `notes/flow & details.md`. Wait for the real diagram and open Review notes. Append a paragraph to that file in the printed fixture folder. The paragraph appears, details stay open, and the unchanged diagram stays drawn.
-5. In a fresh browser context at 390 × 844, verify Files starts collapsed, the board uses one column, and the page does not scroll horizontally. The top bar keeps Inbox with its count. Open Files: an overlay drawer contains the fixed Home, Inbox, Overview, Work, Changes and Diagnostics rows, and the project tree scrolls independently. Escape and an outside tap close the drawer and return focus to Files. Close it and open a document. Also check at 200% zoom.
-6. Disable JavaScript and reload. Content and navigation remain readable. With browser storage blocked, enable JavaScript and change appearance: controls work and explain that choices apply only to the current page.
+5. In a fresh browser context at 390 × 844, verify Files starts collapsed, the board uses one column, and the page does not scroll horizontally. The top bar keeps Today with its count. Open Files: an overlay drawer contains the fixed Today, Goals, Now, Library and System rows, and the project tree scrolls independently. Escape and an outside tap close the drawer and return focus to Files. Close it and open a document. Also check at 200% zoom.
+6. With browser storage blocked, change appearance: controls work and explain that choices apply only to the current page.
 
 The fixture includes duplicate headings, a missing link, long prose, an encoded filename, a diagram, details, and malformed example metadata. The additional `identityFixture()` supplies richer items, explicit references, and recorded claims. Performance timings from this fixture are observations, not established budgets or proof of the north star's usability targets.
 
@@ -38,7 +38,7 @@ The fixture includes duplicate headings, a missing link, long prose, an encoded
 3. Select text, open a content details block, and scroll down. Open another document, then use Back and Forward. Selection, details, and scroll restore. Reload the returned document and check tab-scoped reading state. Repeat after changing the theme on the other page; a cached diagram uses the current theme.
 4. Save a favorite, visit several documents, reload, and open Recent documents to use the reading-history dialog. Recents are unique and bounded. A second workspace must not inherit the first one's favorites. Block browser storage: controls work and display the notice.
 5. Delete a favorite's source file while another page is open. Its sidebar link remains visible with a missing label; following it explains the missing file. Remove a heading after copying its URL and check the missing-passage notice.
-6. Hold a page response in the browser's network tools, navigate elsewhere, then release it. The old response must not replace the new page. Simulate a failed navigation, restore network access, and retry the same link. Recheck desktop, mobile, keyboard, no-JavaScript rendering, and live updates of the active title.
+6. Hold a page response in the browser's network tools, navigate elsewhere, then release it. The old response must not replace the new page. Simulate a failed navigation, restore network access, and retry the same link. Recheck desktop, mobile, keyboard, live updates of the active title.
 
 ## Workspace search acceptance — step 03
 
@@ -46,7 +46,7 @@ The fixture includes duplicate headings, a missing link, long prose, an encoded
 2. Search the text under a second duplicate heading in an encoded filename. Use arrows then Enter; the result opens the correct heading. Escape restores focus to the control that opened the dialog. Check the focus trap, dark theme, and dialog/results scrolling at 390 × 844 without horizontal overflow.
 3. With the dialog open, edit/add/delete a Markdown file in the fixture folder. Results must update. Drop and reconnect the event stream; results reconcile.
 4. Hold an earlier search response, type a different query, then release it. The older results must not replace the newer query. Fail a request and use Search to retry. Unreadable files must disclose incomplete results.
-5. Clear the query and use workspace/sidebar/density/theme commands. Confirm native modified clicks on file results still open another tab. With JavaScript disabled, Search is disabled and documents remain readable.
+5. Clear the query and use workspace/sidebar/density/theme commands. Confirm native modified clicks on file results still open another tab.
 
 Search observations from a named machine may be recorded as a baseline; they are not an agreed performance budget or usability proof. A source-in-editor affordance needs an agreed local editor mechanism.
 
@@ -55,10 +55,10 @@ Search observations from a named machine may be recorded as a baseline; they are
 Add `identityFixture()` from `src/test-support/identityFixture.ts` to the large fixture.
 
 1. Open the legacy board: its 100 cards remain unchanged. Search an explicit ID, owner, and criterion phrase. Check source line labels, then use Enter to open an item/criterion. Criteria expand work details and receive keyboard focus, including when searching within the already active item.
-2. Inspect work details, relationship/source links, and original frontmatter. Missing fields say Not recorded. Evidence shows recorded revision/time/method and outcome with an explicit notice that the claim is not independently verified.
+2. Inspect work details, relationship/source links, and original frontmatter. Missing fields stay blank. Evidence shows recorded revision/time/method and outcome; its heading tooltip explains that the claim is not independently verified.
 3. Open content details and select prose. Rename the source file while its stable item URL is open; details, selection, and location remain. Edit the heading; its title updates. Navigate to its decision and use Back to restore details.
 4. Add a duplicate ID; the active item must become a conflict explanation with source choices. Remove the duplicate and recover. Delete the remaining source; its stable URL must show an explicit missing-item page.
-5. Read a malformed/unknown field and an unresolved reference. Prose and original metadata remain readable. Repeat item/criterion navigation at 390 × 844, in dark mode, and with JavaScript disabled. Check narrow overflow and page errors.
+5. Read a malformed/unknown field and an unresolved reference. Prose and original metadata remain readable. Repeat item/criterion navigation at 390 × 844, in dark mode. Check narrow overflow and page errors.
 
 ## Work board/detail acceptance — step 05
 
@@ -67,14 +67,14 @@ Add `viewsFixture()` from `src/test-support/viewsFixture.ts` to the large fixtur
 1. Confirm the legacy home still has 100 cards. Open Work and select Review work then Shared investigation. The same work.search ID appears in both with the source's recorded fields; counts exclude duplicates and undeclared members.
 2. Apply owner/status/text filters and sorting. Missing fields remain distinct from literal text. Open a card, follow its source/evidence link, then use Back. Reload its URL; board, filters, selected ID, and source pane must agree.
 3. Edit the selected item's status. Applied filters remain, even with no matching status; the detail explains it is outside the projection. Keep unsent text focused through that update. Delete its source; explain the missing selection. Duplicate an ID or membership and inspect source diagnostics, without silently selecting a winner or inflating counts. An unreadable index refuses counts.
-4. Repeat at 390 × 844, with dark theme and reduced motion. Real Mermaid in the pane must render; check overflow and errors. Disable JavaScript and submit GET filters/open detail through native links. Also run the table and saved-view checks below before assessing the combined projection.
+4. Repeat at 390 × 844, with dark theme and reduced motion. Real Mermaid in the pane must render; check overflow and errors. Also run the table and saved-view checks below before assessing the combined projection.
 
 ## Table and saved-view acceptance — step 05
 
 1. Use the same richer fixture. Switch Board/Table with an item selected and filters/sorting applied. IDs, counts, source fields, and selected detail agree. Use Back and reload the table URL; selected context remains. Missing sort fields stay last and missing cells remain explicit.
 2. Save a named table view, reload, choose it, and Open. Applied board/filters/sort/ layout return without retaining item selection or unsent filter edits. Save the same name in a different layout and confirm it updates rather than doubles. Remove one or Clear all. Another workspace must not inherit these names.
 3. Save 10 views. An eleventh name must request removal/update instead of silently evicting one. Malformed stored JSON recovers on a successful save; external or executable saved URLs are ignored and names render as text. Block browser storage: in-memory saving/opening/removal still works with an explicit notice.
-4. Edit a selected item's status, then delete it. The table/counts update while applied filters, focused unsent input, and selection explanations remain. Verify real Mermaid, compact density, 390 × 844/dark/reduced motion without page overflow, and readable no-JavaScript table/filter/detail navigation. Saved-view controls remain disabled without JavaScript.
+4. Edit a selected item's status, then delete it. The table/counts update while applied filters, focused unsent input, and selection explanations remain. Verify real Mermaid, compact density, 390 × 844/dark/reduced motion without page overflow, and keyboard table/filter/detail navigation.
 
 ## Reasoning and evidence acceptance — step 06
 
@@ -84,48 +84,21 @@ Add `reasoningFixture()` from `src/test-support/reasoningFixture.ts` to the larg
 2. Open work.search#keyboard. It lists claims from both its own source and the result file; passage has no recorded evidence. Open the result's record link: its source details expand and the exact evidence record receives focus. Origin file/line, old revision/time, method and recorded outcome are visible; no claim says independently verified or human accepted.
 3. Follow its evidence source to the plain evidence file and inspect Referenced by. Metadata/Markdown backlinks reach their explicit sources, including the encoded review filename. Follow that file's rationale link. The missing local Markdown record remains visible and leads to an explanatory missing page.
 4. Edit the result's criterion reference, delete the evidence source, then remove the result. Claim associations/backlinks reconcile; missing sources/claims remain explicit. Duplicate IDs or unreadable files must prevent validated criterion association and disclose partial references.
-5. Repeat record navigation at 390 × 844/dark/reduced motion and verify overflow, errors, and real Mermaid. Disable JavaScript and follow result → plan → decision natively. Existing legacy home cards remain unchanged.
+5. Repeat record navigation at 390 × 844/dark/reduced motion and verify overflow, errors, and real Mermaid. Existing legacy home cards remain unchanged.
 
 ## Explicit attention acceptance — step 07
 
-Use `attentionFixture()` alongside `workspaceFixture()` with the 100-card legacy home; add a Mermaid diagram to the keyboard task. Open Overview from the legacy home and verify three requests: the review and decision on `request.search`, and the fixture blocker. `ordinary.review` has status/owner/action but no request; `prior-review` is explicitly closed and must not enter the queue.
-
-1. Read why each request appears, its response labels and target links. Open the keyboard review: focus the exact record and expand its source context. Reload, follow its criterion claims and real Mermaid, then Back twice. The overview's issue disclosure remains open. Follow the decision into options/rationale.
-2. Repeat at 1440 × 1000 and 390 × 844, dark theme and reduced motion. Verify no page overflow and native request/criterion navigation with JavaScript disabled. Chromium opens the ancestor details for a fragment target natively.
-3. Close the review/decision in their source; only the blocker remains. Rename the blocker file with spaces and `&`; its identity and encoded source link survive. Delete the criterion's item; the remaining request leaves the queue with an unresolved source issue. No source issue becomes a quiet workspace.
-4. HTTP regressions cover invalid/duplicate/missing identities and requests, unreadable source files, malformed YAML, stable restart and genuine quiet states. Unreadable indexes return 503 and withhold counts/classification.
-
-For the proposed 30-second orientation target, ask a representative reader to identify the judgment requested from them and what it would unblock before opening the details, recording elapsed time and feedback. Then ask them to follow its rationale/evidence. Automated fixture behavior cannot establish this user acceptance; record the exercise separately in the roadmap.
-
-## Explicit change baseline acceptance — step 08
-
-Use the same 100-card legacy home plus attention/reasoning fixture.
-
-1. Open Changes: first visit has no history. Start remembering, then edit recorded status, an attention state and decision Markdown; add a file, move a unique-ID item, and rename a plain file. The view explains changes with current links and escaped remembered/current text. A plain rename is removal/addition; identity moves match only a unique ID. No edit implies authorship or accepted evidence.
-2. Keep the baseline unchanged through live updates, source navigation, Back and reload. Open a remembered-source disclosure and retain it through live edits and Back. Mark seen replaces the baseline; Clear removes it and reload stays off. Touching unchanged source must not create a content change.
-3. Inject an expired record, then open ordinary Markdown: the record is removed without silently rebaselining. Invalid/future/unsupported records establish no comparison. Another workspace key stays untouched. Block storage: explicitly marked history works for this page with a visible persistence limitation.
-4. Repeat at 1440 × 1000 and 390 × 844 with dark theme/reduced motion and check page overflow/errors. Old source containing script/image Markdown is plain text. Disable JavaScript: retention controls are disabled with an explanation, and native Work/source navigation remains available.
-5. HTTP regressions refuse an incomplete observation and a complete oversized workspace without deletion counts or partial snapshots. Schema regressions exercise exact UTF-8 limits, corrupt/unsupported records and unsafe/duplicate paths. Source-comparison fixtures cover ambiguous IDs and unknown frontmatter.
-
-These checks establish comparison behavior, not the separate representative-user orientation target for step 07.
+Use `attentionFixture()` with the workspace fixture. Open Today and inspect the human asks, then follow their source answer cards, criteria and evidence. Repeat at 1440px and 390px with dark theme and reduced motion. Close a request in its source and verify it leaves Today. Source problems must not create asks or imply acceptance. Representative-reader orientation remains a separate exercise recorded in the roadmap.
 
 ## Linked reference directory acceptance
 
-1. Symlink the main checkout's `docs` directory into the workspace as `repo-docs`. Open `/repo-docs/framework/README.md`, follow its relative roadmap link and return with Back. Read the same files with JavaScript disabled.
-2. Include a temporary external reference directory containing nested Markdown. Choose its nested file as `--home`: `/` retains the requested logical alias and resolves relative links. Open a source disclosure, edit the physical reference file and retain the disclosure through live refresh and navigation/Back. Search must find the edited source through its workspace-relative URL.
+1. Symlink the main checkout's `docs` directory into the workspace as `repo-docs`. Open `/repo-docs/framework/README.md`, follow its relative roadmap link and return with Back.
+2. Include a temporary external reference directory containing nested Markdown. Choose its nested file as `--home`: Workspace notes retains the requested logical alias and resolves relative links. Open a source disclosure, edit the physical reference file and retain the disclosure through live refresh and navigation/Back. Search must find the edited source through its workspace-relative URL.
 3. Add another directory link while the server runs, then retarget it to a different reference folder. Its navigation and reads catch up, obsolete paths disappear, and later edits of the new target refresh the active page.
 4. Repeat at 1440 × 1000 and 390 × 844, including dark theme/reduced motion. Check overflow and browser errors. Native HTTP regressions separately cover cycles/ancestor traversal, broken links, hidden/dependency entries, escaping file links, internal aliases, external add/rename/delete and watcher recovery.
 
 Links explicitly include trusted reference directories; the server never writes those sources. A target missing when the watch was built needs a server restart once restored. Multiple aliases remain separate paths and existing duplicate-ID rules apply. These checks establish reference reading; run the native live/orientation checks for invalidation and pause/resume.
 
-## Explicit observation overlap acceptance
-
-1. Start with two Markdown sources. Hold an actual HTTP `observe` response after it captures the first source revision, then edit that physical source and let its native watcher/SSE page refresh finish. Release the response: Mark seen retains the captured revision and comparison reports the subsequent change. A later explicit Mark seen replaces that baseline and reports no changes.
-2. Hold another observation, then Clear from a second tab sharing this workspace and browser storage. Release the old response. Both tabs stay without history; the cancelled observation must not restore the deleted baseline.
-3. Check ordinary marking at 390 × 844 with dark theme/reduced motion, page overflow and browser errors. DOM regressions separately force the overlap before the HTTP observation begins and assert cancellation by another tab's storage event. Keep the existing expiry, size and blocked-storage checks.
-
-These checks preserve explicit observation semantics; they do not establish an atomic filesystem snapshot, source mutation or verified acceptance. Run the native lifecycle checks separately.
-
 ## Native live/orientation acceptance — step 09
 
 Use the large workspace plus `viewsFixture()` and a nested home at `/`.
@@ -134,9 +107,8 @@ Use the large workspace plus `viewsFixture()` and a nested home at `/`.
 2. Open details and a real Mermaid drawing. Edit another passage: unchanged details, drawing, selected work URL and focused/unsubmitted filters remain. Changed reading blocks receive a brief outline without animation or scrolling.
 3. Pause, edit the nested home and wait for a pending count. The displayed source stays retained; resume catches up. The 256+ bound counts hints, not source edits.
 4. Go offline and edit, then reconnect. Retain visible source with a failure/down disclosure until required reads settle; connection availability alone is not freshness. Separately stop the native HTTP server with a subscription active.
-5. Mark seen, update source, and verify the original baseline stays unchanged. Clear while paused; expired history must also disclose unknown history while paused. Never cancel explicit observation through background invalidation.
-6. Navigate away and use browser Back. Record whether pageshow is persisted and any CDP bfcache refusal reasons; no-store can require a fresh document. Verify persisted-pageshow registry recreation separately with the DOM regression.
-7. Repeat at 390 × 844 with dark/reduced-motion settings and JavaScript disabled. Links still perform GET navigation; Pause is disabled without JavaScript. Verify browser actions have changed no source files.
+5. Navigate away and use browser Back. Record whether pageshow is persisted and any CDP bfcache refusal reasons; no-store can require a fresh document. Verify persisted-pageshow registry recreation separately with the DOM regression.
+6. Repeat at 390 × 844 with dark/reduced-motion settings. Verify keyboard navigation and Pause updates. Verify browser actions have changed no source files.
 
 Physical tab transitions and Capacitor remain separate evidence. Fixtures do not establish the step 07 representative-reader timing or a multi-tab capacity budget.
 
@@ -144,4 +116,4 @@ Physical tab transitions and Capacitor remain separate evidence. Fixtures do not
 
 Reference a source-relative PNG/JPEG/GIF/WebP in a nested home and an evidence record. Inspect embedded images and local image links by keyboard; choose gallery images and return focus with Escape. Replace an image while paused, then resume; check the image reloads and open reading details survive. An earlier preview must disclose source updates and require reopening before saving. Try a missing image, malformed path, escaping link and oversized attachment.
 
-Inspect a large Mermaid diagram, choose Actual size and zoom, scroll on a narrow screen, enter desktop fullscreen and return to the source. Save the current SVG locally; also test an invalid diagram and an unavailable fullscreen environment. With JavaScript disabled, local images and diagram source remain readable. Record actual results and limits in the [roadmap](../roadmap.md). Physical mobile fullscreen and representative-reader timing require their own evidence.
+Inspect a large Mermaid diagram, choose Actual size and zoom, scroll on a narrow screen, enter desktop fullscreen and return to the source. Save the current SVG locally; also test an invalid diagram and an unavailable fullscreen environment. Record actual results and limits in the [roadmap](../roadmap.md). Physical mobile fullscreen and representative-reader timing require their own evidence.

package/docs/delivery/decision-write-examples.md

@@ -72,7 +72,7 @@ The existing CLI wait returns that one response, including typed answers, readab
 
 ## Changed context and superseding direction
 
-A source edit or move does not silently carry selections into another context. The UI preserves human text, clears choices and retains a copy of earlier answers for recovery. Drafts retain the existing 30-day/2-MiB browser-local workspace policy. An edit during a pending save remains a separate unsaved draft with its own identity.
+A source edit or move does not silently carry selections into another context. The UI preserves human text, clears choices and retains a copy of earlier answers for recovery. Drafts use effect-form’s seven-day/256-KiB browser-local per-draft policy. An edit during a pending save remains a separate unsaved draft with its own identity.
 
 An optional `supersedes` identity explicitly links a new response to an existing response for the same item's request, including an earlier source revision. This creates another immutable record rather than editing history. The UI qualifies old contexts and links superseding direction; it never infers task status, closes attention, claims criterion acceptance or launches an agent. Missing/moved source requires reviewing and registering the available context; historical records remain readable through their registered question identity. Ambiguous or malformed history is unknown, not an empty answer list. This includes syntactically damaged or unterminated frontmatter in `responses/`, even when the parser cannot recover its record kind. Ordinary malformed Markdown outside that record namespace does not establish a response or block feedback reads.
 

package/docs/delivery/handoff-examples.md

@@ -20,7 +20,7 @@ handoff:
   reviewed_revision: 691e2b8c3ca54cd66afa1533e9917cbef69e8a13a5bb79275abf65a101ee6dde
   prepared_at: 1791319869349
   goal: Fix keyboard focus
-  constraints: Preserve no-JavaScript links and local-only operation.
+  constraints: Preserve keyboard navigation and local-only operation.
   next_action: Inspect the current source and report browser evidence.
 ---
 ---
@@ -53,7 +53,7 @@ These fields belong inside the record's `handoff` mapping. Recipient and `by` ar
 
 Same-ID preparation retries preserve raw receipt bytes and extra metadata, even if the original source disappears. Different direction or a moved/duplicate record identity is a conflict. Initial preparation checks the reviewed source revision and path. Later reads qualify earlier or unavailable context and retain saved history. Malformed or ambiguous history stays unavailable; task status does not supply a missing receipt.
 
-Browser drafts share the existing 30-day/2-MiB workspace store. Clearing workspace drafts clears response and handoff drafts together, without deleting saved records. There is no special acknowledgment command, editor lock or universal transaction with unrelated editors.
+Browser drafts use effect-form persistence with a seven-day lifetime and 256 KiB limit per draft. Clearing the current draft restores its form’s initial values without deleting saved records or other drafts. There is no special acknowledgment command, editor lock or universal transaction with unrelated editors.
 
 ## Native integration
 

package/docs/delivery/reading-review.md

@@ -4,7 +4,7 @@ Use this investigation to assess the combined reading experience, rather than ac
 
 ## Read the actual project
 
-Serve the package's north star, roadmap and delivery requirements through an explicit reference-directory link. Read them at desktop and narrow viewports in light/dark themes and reduced motion. Follow the source relationships without JavaScript, then repeat with native navigation and real Mermaid enabled.
+Serve the package's north star, roadmap and delivery requirements through an explicit reference-directory link. Read them at desktop and narrow viewports in light/dark themes and reduced motion. Follow source relationships with native navigation and real Mermaid enabled.
 
 Return to changed notes as a representative reader. Find the next judgment without coaching, explain what it unblocks, then follow its rationale and evidence. Record the elapsed orientation time and confusing moments separately from technical checks. A working queue cannot prove that a person understands its contents.
 

package/docs/delivery/response-write-examples.md

@@ -21,7 +21,7 @@ A source change/rename during drafting preserves the text and shows the revision
 
 Publication runs on Linux and macOS with supported hard links/fsync; see the README for the macOS path-based limits. Read-only operation remains available elsewhere. New files publish without replacement; same-ID retries reconcile exact content. Moved/duplicated/conflicting identities, permission failures and changed/symlinked write boundaries are rejected. After a post-publication failure, an uncertain result retains the draft. Reconcile saved identity/content and directory synchronization before confirming a retry.
 
-Browser drafts are separate from Mark seen: one 2 MiB bound per workspace/origin, 30 days after edit, explicit clearing and expiry/storage failure disclosure. Saved source has no implicit retention deletion. A 48-hour unanswered deadline starts at durable registration; rearming/page visits do not reset it. It returns a distinct nonzero unanswered result, leaves the request intact, and permits a late reply. Service outages never establish that a person left it unanswered.
+Browser drafts are separate from Mark seen: effect-form persistence keyed by workspace, item and request, a 256 KiB bound per draft, seven days after edit and explicit current-form clearing. Saved source has no implicit retention deletion. A 48-hour unanswered deadline starts at durable registration; rearming/page visits do not reset it. It returns a distinct nonzero unanswered result, leaves the request intact, and permits a late reply. Service outages never establish that a person left it unanswered.
 
 Implementation, acceptance and handoff decisions belong in the [roadmap](../roadmap.md). The [ownership boundary](./source-editing-examples.md) keeps ordinary project editing with agents; a passive question wait is a reader for an existing harness.
 
@@ -29,4 +29,4 @@ Implementation, acceptance and handoff decisions belong in the [roadmap](../road
 
 Run `pnpm ready` for native types, regressions, the real local PostgreSQL suites and packed consumers. Start the production CLI against a disposable folder with an explicit attention request and `--responses`. Open Respond, enter a draft, reload, and modify the proposal externally. The draft must survive and require a new preview. Start concurrent `wait <item>/<request> --revision <hash>` commands; restart the server at the same port, kill and reattach one waiter, then record a reply. Every successful stdout result must name the same question generation and attributable reply. Repeating the wait must not consume it. Compare the original source bytes and inspect the independent Markdown records.
 
-Delay a successful response acknowledgment while typing another draft. Release it and reload: the later text must remain under a fresh response identity. Check narrow dark/reduced-motion layout and saved reply reading without JavaScript. For resources, sample `/proc/<pid>/smaps_rollup`, CPU ticks and descriptors for 20 registered idle waiters over five seconds, without concurrent repository handoff. Report PSS separately from summed RSS; neither a short idle observation nor an edited test deadline proves a 48-hour soak or automatic harness wakeup.
+Delay a successful response acknowledgment while typing another draft. Release it and reload: the later text must remain under a fresh response identity. Check narrow dark/reduced-motion layout and saved reply reading. For resources, sample `/proc/<pid>/smaps_rollup`, CPU ticks and descriptors for 20 registered idle waiters over five seconds, without concurrent repository handoff. Report PSS separately from summed RSS; neither a short idle observation nor an edited test deadline proves a 48-hour soak or automatic harness wakeup.

package/docs/delivery/result-review-examples.md

@@ -73,7 +73,7 @@ The open `review` attention request explicitly asks for judgment. Its two `verdi
 
 ## Review beside the source
 
-Open **Review returned result** on the report, or `/_board/result?item=result.keyboard`. A uniquely identified readable result uses both the ordinary GET page and the existing native page query. The report status is shown separately from its linked task's status. Neither report status nor a handoff receipt verifies execution or authorizes a merge.
+Open **Review returned result** on the report, or `/_board/result?item=result.keyboard`. A uniquely identified readable result uses the ordinary GET route and the typed native `result` query. The report status is shown separately from its linked task's status. Neither report status nor a handoff receipt verifies execution or authorizes a merge. [Result tests](../../src/server/results/result.spec.ts) cover HTTP reads, typed result queries, missing evidence, ambiguous identities and feedback pinned to exact report bytes and paths.
 
 The page lists explicitly linked criteria, this result's claims, missing provenance, report/limitations and recorded human feedback. An unresolved or duplicate identity does not choose a convenient source. A missing local Markdown evidence source remains disclosed. Report and feedback context use the safe Markdown reader; exact reviewed source remains available separately.
 

package/docs/delivery/source-examples.md

@@ -45,7 +45,7 @@ relationships:
 Use deterministic local matching first. Keep Markdown authoritative.
 ```
 
-Every top-level field is optional. Missing values show as **Not recorded** in work details. `owner` records responsibility, without claiming authorship. `status` and `next_action` are explicit source text; no status vocabulary or transition rules are inferred.
+Every top-level field is optional. Missing values stay blank in work details. `owner` records responsibility, without claiming authorship. `status` and `next_action` are explicit source text; no status vocabulary or transition rules are inferred.
 
 | Field | Source shape |
 | --- | --- |
@@ -104,7 +104,7 @@ evidence:
     outcome: passed
 ```
 
-This example deliberately has no revision or observation time; they remain **Not recorded**. Supply real values when available. Relative source links resolve from the file containing the record. HTTP(S) sources are ordinary links; executable URL schemes stay plain text. Local image sources use the contained PNG/JPEG/GIF/WebP attachment route described in the README; other non-Markdown assets are not served.
+This example deliberately has no revision or observation time; they remain blank. Supply real values when available. Relative source links resolve from the file containing the record. HTTP(S) sources are ordinary links; executable URL schemes stay plain text. Local image sources use the contained PNG/JPEG/GIF/WebP attachment route described in the README; other non-Markdown assets are not served.
 
 Records are labeled **Source claims — not independently verified**. A recorded outcome, test link, agent run completion, or proposed decision does not establish verified acceptance. Work Board neither runs checks nor verifies freshness here.
 

package/docs/delivery/visual-document-examples.md

@@ -22,7 +22,7 @@ Source: [Reader acceptance](../roadmap.md)
 :::
 ```
 
-`unit` is required and nonblank. `value` is a finite number, `unknown`, or omitted. An unknown or omitted value displays “Not recorded”, never zero. Preserve a source paragraph beginning `Source:` with a Markdown link. Source links identify provenance; their existence or statements are not verified by the component.
+`unit` is required and nonblank. `value` is a finite number, `unknown`, or omitted. An unknown or omitted value renders nothing. A progress tally renders only when both counts are known. Preserve a source paragraph beginning `Source:` with a Markdown link. Source links identify provenance; their existence or statements are not verified by the component.
 
 ### Progress
 
@@ -71,4 +71,4 @@ Use GitHub's five alert markers: NOTE, TIP, IMPORTANT, WARNING and CAUTION. Unkn
 - Inline/leaf visual forms are unsupported. Inline directives retain their literal source; unsupported leaf forms show source and a diagnostic. Unclosed or malformed syntax follows the established directive parser's reading rules.
 - A component is limited to 64 KiB of source. Nested visual directives are unsupported; original source remains visible.
 - Render fixed semantic elements on the server. No author-supplied JavaScript, JSX, executable MDX, templates, queries, plugin loading or remote data fetching.
-- Preserve headings, local links, search/backlinks, print text alternatives, native update ownership and the explicit Mark seen baseline. No source writes, new D1 fields, YAML visual fences or acceptance inference.
+- Preserve headings, local links, search/backlinks, print text alternatives, native update ownership. No source writes, new D1 fields, YAML visual fences or acceptance inference.

package/docs/delivery/wave1.md

@@ -27,19 +27,14 @@ The [delivery plan](./README.md) explains gates and verification. These steps de
 **Outcome:** a result leads to its criteria, plan, decision, and supporting files. Render decision options, rationale, backlinks, dependencies, and criterion-level evidence. Show origin, checked revision, and observed time where explicitly provided. Missing evidence and an agent's unsupported claim remain distinct from verified results. Begin with readable links; inline asset previews arrive in 10. **Depends on:** 04–05. **Accept:** the sample result reaches its source rationale in two navigation steps; broken links and evidence for an old revision stay visible.
 
 
-## 07 An attention-first overview
+## 07 Human attention on Today
 
 **Outcome:** returning users can identify the next judgment without reading a log. Derive queues for explicit decision requests, blockers, and review requests. Each entry names why it appears, whose response is needed, and what it unblocks. Use simple visible ordering and link directly to 05/06's context. Include quiet and empty states. Do not treat file churn, heartbeat, or a finished agent run as progress. **Depends on:** 05–06. **Accept:** representative users can find the intended next judgment within the proposed 30-second target; ambiguous items stay unclassified.
 
 
-## 08 What changed since I last looked
-
-**Outcome:** readers distinguish meaningful changes from an unchanged busy process. Track local last-viewed markers and compare retained source revisions for explicit field/content changes. Show additions, removals, changed decisions, and evidence updates with source links. Define bounded retention and clearing before retaining snapshots. If history is unavailable, say so; modification time is not a diff. **Depends on:** 04 and 07. **Accept:** a returning view summarizes a known sequence of edits correctly; a first visit, cleared storage, or renamed source never invents history or authorship. No durable event journal is required.
-
-
 ## 09 Live updates that preserve orientation
 
-**Outcome:** the workspace stays current without disturbing active reading. Use changed paths to invalidate affected documents, derived views, search results, and backlinks. Keep navigation updates when files are added/deleted. Add pause, pending-change count, restrained highlighting, and resume. Recover with a full reconciliation after reconnect or uncertain watcher state; never trust a path-only optimization when events may have been missed. **Depends on:** 05–08. **Accept:** unrelated edits avoid full active-document rerenders; focused controls, open details, and diagrams survive relevant changes; paused and reconnecting states catch up without claiming stale data is current.
+**Outcome:** the workspace stays current without disturbing active reading. Use changed paths to invalidate affected documents, derived views, search results, and backlinks. Keep navigation updates when files are added/deleted. Add pause, pending-change count, restrained highlighting, and resume. Recover with a full reconciliation after reconnect or uncertain watcher state; never trust a path-only optimization when events may have been missed. **Depends on:** 05–07. **Accept:** unrelated edits avoid full active-document rerenders; focused controls, open details, and diagrams survive relevant changes; paused and reconnecting states catch up without claiming stale data is current.
 
 
 ## 10 Local visual evidence
@@ -56,7 +51,7 @@ The [delivery plan](./README.md) explains gates and verification. These steps de
 
 **Outcome:** a new user can begin locally and read useful project and agent reports. Provide copyable Markdown templates for a project, investigation, and agent result; useful empty-state instructions; and preserve basic browser print readability. Reports are ordinary source documents read through normal Work Board views, with links to plans, decisions and recorded criterion-level evidence. No report format creates verified acceptance or a new execution/handoff protocol.
 
-Document export is outside product scope: external shareable artifacts, portable snapshots and meeting packets have no demonstrated Work Board use case. Do not build HTML/PDF/ZIP packet generation, export previews, selection manifests, or a deferred export feature in another wave. Native browser printing remains a reading affordance, not a PDF service or artifact builder. An `init` CLI command still needs a separate API decision; copyable templates do not write source files. **Depends on:** 07 and 10–11. **Accept:** start from an empty folder, use the copyable templates through an existing editor/agent tool, and inspect the resulting project, investigation and result in ordinary Work Board views. Unknown outcomes and recorded evidence remain distinct from verified acceptance; the viewer does not create source files or mark history seen implicitly.
+Document export is outside product scope: external shareable artifacts, portable snapshots and meeting packets have no demonstrated Work Board use case. Do not build HTML/PDF/ZIP packet generation, export previews, selection manifests, or a deferred export feature in another wave. Native browser printing remains a reading affordance, not a PDF service or artifact builder. An `init` CLI command still needs a separate API decision; copyable templates do not write source files. **Depends on:** 07 and 10–11. **Accept:** start from an empty folder, use the copyable templates through an existing editor/agent tool, and inspect the resulting project, investigation and result in ordinary Work Board views. Unknown outcomes and recorded evidence remain distinct from verified acceptance; the viewer does not create source files.
 
 
 ## 13 Prove the complete reading workflow

package/docs/north-star.md

@@ -2,7 +2,9 @@
 
 Work Board is a local, file-backed workspace for a person and their agents to understand work and exchange direction. Open it to know what is happening, what changed, what needs judgment, and where the evidence lives. Close it without losing the work: the meaningful content remains readable in project files.
 
-The [roadmap](roadmap.md) owns implementation status, acceptance gaps and open maintainer decisions. The [README](../README.md) teaches current use. The [experience design](experience.md) and [interactive prototype](mockups/index.html) illustrate the product direction with fictional data. The [delivery requirements](delivery/README.md) define bounded steps and how to verify them, without keeping a second status list.
+The [roadmap](roadmap.md) owns implementation status, acceptance gaps and open maintainer decisions. The [README](../README.md) teaches current use. The [delivery requirements](delivery/README.md) define bounded steps and how to verify them, without keeping a second status list.
+
+Today is the first screen. It puts the human’s live asks and answers beside compact goal progress. In progress names the work Fleet holds, its stage and its recorded PR; the preview stays short and links to Now for the full view. Goal cards show the next action in at most two lines and done work against all linked work, with criteria and evidence behind a closed disclosure. Goals shows active goals, Now shows current work, Library finds documents and recently changed files, and System shows provider limits and names the running or waiting Fleet work with stage and PR. Configured home Markdown remains reachable as Workspace notes. Narrow screens read summary, human asks, in-progress work and goals in order; wide screens put goals beside the asks and in-progress work.
 
 ## The problem
 
@@ -20,6 +22,8 @@ A handoff preserves reviewed direction in another readable file. A copied pointe
 
 Returned work needs the same discipline. An authored result and its evidence are claims to inspect. Human direction belongs to the exact report bytes and source path that prompted it; a later edit must not inherit an earlier acceptance. A report iteration can receive human acceptance while a criterion still lacks evidence. The board must keep those facts visible rather than compute a convenient overall success state.
 
+Goal progress shows the goals query's done, in progress and planned counts and its goal-specific open-ask count, including zero. Fleet-held stages override authored status for both goal and criterion counts; released stages fall back to authored status. Deferred and unrecorded work contribute to planned progress. Open asks use the attention projection's eligible active rows, including its grouping and resolved or parked exclusions. Criteria show their progress split with linked work and recorded evidence. Untargeted criteria keep their text without an extra label, and missing evidence stays quiet. Closed projects retain the same goal and criterion counts while staying outside active-goal navigation. Lifecycle completion never establishes criterion acceptance. The goal page puts progress immediately below the item header, before open answer cards. Criteria, linked work and authored prose follow, with an outline rail for reading. Each implementing item appears once under a nonempty In progress, Planned, Done (collapsed) or Deferred group with one state chip and its recorded PR. The chip shows the held Fleet stage or the authored status; missing status and PR stay blank. Progress is never a computed overall success state or completion percentage.
+
 ## What good looks like
 
 - **Readable source.** A folder and one command are enough to begin. Plain Markdown remains useful; metadata is optional; no hidden database holds the only meaningful copy of work.