dotemacs/docs, branch main

docs(spec): flip keybinding-console-safety DOING to READY

2026-07-21T12:07:51+00:00

The DOING came from a legacy status retrofit with no build tasks ever decomposed, and the primary work has not started: the key-translation layer is still live and the M-S- bindings are still global. READY is the honest state, design settled and awaiting decomposition.

fix(agenda): spawn the agenda frame tiled, not compositor-fullscreen

2026-07-20T20:38:23+00:00

I dropped (fullscreen . fullboth) from the spawned frame so a tiling WM places it side by side with the working frame. "Fullscreen" was the wrong word for the intent: a normal frame at its full tiled position, not one covering the whole output. The engage-routing and focus logic are unchanged and matter more now, since a task opens in the adjacent working pane.

feat(agenda): add S- dedicated fullscreen agenda frame

2026-07-20T19:23:38+00:00

I added a standing agenda surface in its own fullscreen frame of the daemon, placeable on its own workspace while the working frames stay untouched. S- spawns, raises, or closes it. The force-rescan moves to C-M-. It shows a today-anchored seven-day view and refreshes every five minutes through org-agenda-redo, so the now-line and synced events stay current without re-scanning the file list. A default-deny minor mode keeps it read-only: only navigation, the engage keys (routed to the working frame), and the frame's own controls are allowed. A failed redo falls back to the last-good snapshot with cloned markers, so the frame is never blank or unrestricted. I made it a frame of the daemon rather than a second process, so it shares the live state (calendar-sync, edits, the now-line). There's no startup auto-open, and the Hyprland-managed-window variant is a vNext once this proves out.

docs(spec): redesign org-agenda spec to a fullscreen frame, mark READY

2026-07-20T14:54:43+00:00

Craig redirected the right-side dock to a dedicated fullscreen frame of the daemon. I resolved all 8 decisions, reworked the design, alternatives, phases, and acceptance criteria to match, and flipped DRAFT to READY on the spec-review gate. One non-blocking finding: the frame view needs its own custom-command entry.

docs: fix broken file: links in theme-studio and ai-kb specs

2026-07-20T12:25:31+00:00

feat: add workflow font profiles

2026-07-20T02:10:40+00:00

I replaced the mixed Fontaine presets with seven named profiles that persist across restarts. The mode line, echo area, and minibuffer stay in Berkeley Mono. Nov applies the shared Reading profile inside each EPUB buffer without changing the global selection.

docs: add org-agenda dock-mode spec (draft)

2026-07-18T15:32:18+00:00

A right-side full-height agenda dock: side-window display ignoring the 0.75 below-selected rule, a dock-scoped 5-min redo, and jump-to-task that opens in the working window. Four design decisions stay open (dock width, composite view shape, focus-on-open, auto-open default).

refactor(signal): retire the in-Emacs signel client to the archive

2026-07-14T06:12:21+00:00

Agents drive Signal via signal-cli and signal-mcp, so the interactive client earns no keep. I moved signal-config.el and its seven test files to archive/ per the pasture convention, dropped the require from init.el, removed the dashboard's Signal launcher (row sizes now 5 4 3 2, tests updated), and unregistered the C-; M prefix from the running daemon. The ~/code/signel fork repo is untouched. The spec record stays IMPLEMENTED with a retirement history line, and the messenger-unification draft carries a premise-shift note.

docs(specs): retire the gloss spec, close signal-client as implemented

2026-07-14T06:02:21+00:00

The gloss spec described a repo scaffold and implementation that shipped months ago (the package lives at its own repo and gloss-config.el already wires it in) — the file was a stale artifact, deleted on Craig's call. signal-client flips to IMPLEMENTED: v1 is in daily use, and the messenger-unification spec designates the smoke project as the ground-up successor, so further client work happens there.

docs(spec): reconcile init-load-graph to the shipped LSP decision

2026-07-11T03:52:03+00:00

The spec owned the LSP and tree-sitter decisions but still recommended consolidating under prog-lsp. That inverted what shipped: prog-lsp was dead code nothing required, so the fix folded it into prog-general and deleted it. Update the programming target, module table, and ownership note to record prog-general as the sole LSP owner and tree-sitter gated to 'prompt. The keyword stays DOING for the remaining load-graph work.