k0-board 0.6.0 → 0.7.0

package/.claude/skills/k0-ultracode/SKILL.md

@@ -240,12 +240,12 @@ the Log records as merged is ever done twice.
 
 ## 10. Close
 
-To the user, in his language, and nothing after it:
+To the user, in his language — the two headings too — and nothing after it:
 
-**Cosa ho fatto** — what is different now, story by story: whether the tests were green, what the
+**What I did** — what is different now, story by story: whether the tests were green, what the
 fresh pair of eyes said, how the counter-check came out.
 
-**Cosa resta a te** — the assumptions taken alone, so he can overturn any of them with
+**What is left for you** — the assumptions taken alone, so he can overturn any of them with
 `/k0-discuss`; the assignments left out and what they needed; whatever the repairs did not fix; and
 that the stories are sitting in `Review` waiting for him to press `Done`, which is his and nobody
 else's.

package/CHANGELOG.md

@@ -6,6 +6,34 @@ All notable changes to this project are documented here. The format follows
 
 ## [Unreleased]
 
+
+## [0.7.0]
+
+k0 gets a public home at k0-board.com, where you can read what it does and ask for an early-access
+account, and asking now sends you an email that says you are on the list. On your own machine, the
+terminals k0 opens keep a margin at the edge of the screen in every mode again, Driving included.
+
+### Added
+
+- **k0-board.com has a home page.** What k0 does, how to start, the plans it is heading for —
+  nothing is charged during early access — and a form to ask for an account, which says you are on
+  the list the moment you send it. Privacy and terms pages say plainly what is stored and where. It
+  follows the light or dark setting of your system, and reads on a phone.
+- **Asking for early access sends an email.** The person who asked gets a line saying they are on the
+  list, and whoever runs k0 is told — about that, and about anybody who signs in and is waiting to be
+  let in. Mail to the address on the site reaches a person. Tried for real: the notice and a
+  forwarded message both arrived.
+
+### Changed
+
+- **Terminals keep a margin in every mode, Driving included.** A terminal k0 opens or rearranges
+  takes 90% of the free screen, centred, so there is always a strip at the edge to click on. Driving
+  still makes the text large, but no longer stretches the window across the whole screen.
+- **The last Italian leftovers are gone.** The board no longer answers to `#nuovo` (`#new` still
+  opens a new story), and a document's title is read from `title` or `name` only, no longer from
+  `titolo` or `nome`.
+
+
 ## [0.6.0]
 
 k0 gets an account and a cloud. The board still runs on your machine and keeps working with no
@@ -761,7 +789,8 @@ here is everything that had to change for it to be somebody else's tool as well.
 - The personal fixtures k0 grew up on. `test/clean.test.mjs` now fails the build if any of them
   come back.
 
-[Unreleased]: https://github.com/alessio-ragni/k0-board/compare/v0.6.0...HEAD
+[Unreleased]: https://github.com/alessio-ragni/k0-board/compare/v0.7.0...HEAD
+[0.7.0]: https://github.com/alessio-ragni/k0-board/compare/v0.6.0...v0.7.0
 [0.6.0]: https://github.com/alessio-ragni/k0-board/compare/v0.5.0...v0.6.0
 [0.5.0]: https://github.com/alessio-ragni/k0-board/compare/v0.4.0...v0.5.0
 [0.4.0]: https://github.com/alessio-ragni/k0-board/compare/v0.3.0...v0.4.0

package/README.md

@@ -346,8 +346,8 @@ are still one counter for the whole board rather than one per repository, kept o
   work and check keep a task per step — so without it they would be asking for a tool that is not
   there.
 
-  The window is born **centred on the screen you are using**, at 86% of the free space: the same
-  margin on all four sides, never under a menu bar or a dock. Open more than one and they stack
+  The window is born **centred on the screen you are using**, at 90% of the free space, in every mode:
+  the same margin on all four sides, never under a menu bar or a dock. Open more than one and they stack
   in the middle — double click brings the one underneath back.
 
   **If the screen changes** — you plug a monitor in or out, or change resolution — the windows put
@@ -1521,7 +1521,7 @@ one again does nothing — you leave a mode, you do not switch it off.
 | two **z** | **Sleep** | sleeps as it normally would | goes off | normal |
 | a **palm tree** | **Away** | does not sleep, not even with the lid closed | may sleep and lock | normal |
 | a **nerd face** with glasses | **Nerd** | does not sleep | **stays on** | normal |
-| a **car** | **Driving** | does not sleep | **stays on** | **large**: the text here and in the terminals, and the terminals fill the screen |
+| a **car** | **Driving** | does not sleep | **stays on** | **large**: the text here and in the terminals |
 
 The four icons do not describe the machine: they describe **where you are**. Asleep, away, at the
 desk, watching from across the room. That is where the order comes from, and it is why the second
@@ -1569,17 +1569,22 @@ they reorder by urgency, reddest to the left. On a screen you glance at, two or
 visible at a time and the most urgent one has to come to you. Full screen you have them all in
 front of you already, and a board that reshuffles itself while you work only loses your place.
 
-**The windows grow with the text.** In Driving a terminal takes the whole free screen; leave
-Driving and it goes back to the usual 86% centred, with the text back at the profile's size. It is
-one gesture and not two, and it lands on the terminals **already open**, not only on the ones you
-open next.
+**The windows keep their margin.** In every mode, Driving included, a terminal takes 90% of the
+free screen, centred, with the same strip left free on all four sides — that strip is where you
+click to reach whatever is behind it. Driving changes the text, not the share: switch it on and the
+terminals get 22 point text and are put back at 90% centred; switch it off and the text goes back
+to the profile's size. It is one gesture and not two, and it lands on the terminals **already
+open**, not only on the ones you open next.
+
+For a while Driving took the whole free screen instead, which left nothing at the edge to click on;
+the margin is worth more than the last tenth of the screen.
 
 It used to be the opposite, and the reason is worth keeping in mind: Terminal.app holds rows and
 columns when the font changes and resizes the window to match — going from 12 to 22 turns a 700×500
 window into 1378×856, measured — so k0 read each window's own bounds first and put them back, and
 nothing moved. What that left behind was a window holding 22 point text in a box measured for 12.
-Half a gesture is worse than none, so the size of the text and the size of the window now travel
-together, and the price is said plainly: **a window you had dragged onto another screen comes back
+Half a gesture is worse than none, so the text is set first and the window put back at its share
+right after, and the price is said plainly: **a window you had dragged onto another screen comes back
 to the middle of the main one.**
 
 **All of them, every time.** k0 asks Terminal once for the windows it has open and changes those
@@ -1849,8 +1854,10 @@ web/             the four pages (html, css, js served exactly as they are)
 supabase/        k0 Cloud's own side: migrations/ is its database (accounts, workspaces, the
                  rows of every board, the counter), config.toml its sign-in settings. The secrets
                  are in ~/.config/k0-cloud/.env, never in the repository
-site/            k0-board.com: static pages, no build. app/ is the read-only web board and the
-                 page where accounts are approved — both coming with the site
+site/            k0-board.com: static pages, no build, deployed as they are. index.html is the
+                 home page with the early-access form (waitlist.js), privacy, terms and 404
+                 beside it, one site.css; app/ is the read-only web board and the page where
+                 accounts are approved
 docs/
   database.md    the shape of the database as it is now, table by table, column by column
   method.md      why a decision has to be an object, what a round of questions is for, and
@@ -1860,6 +1867,11 @@ test/            npm test — Node's own runner, no framework. See docs/testing.
   harness.mjs    check(label, got, want), and the sections the labels are grouped under
 ```
 
+
+Two small pieces live outside the app because they run in the cloud, not on your machine:
+`supabase/functions/notify` sends the emails k0 Cloud sends (an early-access request, an account
+waiting to be let in), and `infra/mail-forward` forwards mail sent to the site's contact address.
+Neither ships in the npm package. Where each one runs and how it is put online: `docs/cloud.md`.
 ### How the board reaches the cloud
 
 The board's rules live on the machine, in SQLite, and they stay there: states, decisions, rounds,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "k0-board",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "description": "A board of sticky notes that drives your Claude Code sessions",
   "keywords": [
     "claude-code",

package/platform/darwin/terminal.js

@@ -17,8 +17,11 @@ const PBPASTE = () => which('pbpaste', ['/usr/bin/pbpaste'])
 /** Escape for an AppleScript string literal. */
 const asq = (s) => String(s).replace(/\\/g, '\\\\').replace(/"/g, '\\"')
 
-/** How much of the free screen area a window takes unless somebody asks for more. */
-const COVERAGE = 0.86
+/**
+ * How much of the free screen area a window takes, in every mode: the rest is margin, and the
+ * margin is where you click to reach whatever is behind it.
+ */
+const COVERAGE = 0.9
 
 /**
  * How long a pass over the open windows may take. The five seconds `run` gives every other
@@ -28,9 +31,6 @@ const COVERAGE = 0.86
  */
 const PASS_TIMEOUT = 20000
 
-/** In driving mode the terminal has to be readable from across the room. */
-export const DRIVING_FONT_SIZE = 22
-
 /**
  * The profile's font size, asked once and then remembered. It is what we go back to when
  * driving mode is switched off; hard-coding a 12 here would be right today and wrong the
@@ -51,8 +51,7 @@ export async function defaultFontSize() {
  * same for all of them: otherwise the first time a monitor is unplugged every window would
  * change size for no reason.
  *
- * `coverage` is how much of the free area the window takes: the usual share, or all of it when
- * the mode wants windows readable from across the room.
+ * `coverage` is how much of the free area the window takes; left out, it is the usual share.
  *
  * Leaves `x1`, `y1`, `w` and `h` behind, which is what `bounds` needs.
  */

package/platform/shared/tmux.js

@@ -36,8 +36,8 @@ const EMULATORS = [
   { bin: 'xterm', args: (cmd) => ['-e', ...cmd] },
 ]
 
-/** How much of the work area a window takes unless the mode asks for more. */
-const COVERAGE = 0.86
+/** How much of the work area a window takes, in every mode: the rest is margin. */
+const COVERAGE = 0.9
 
 /**
  * Which emulator to open. `K0_TERMINAL` wins, because no list of ours will ever cover every

package/platform/win32/terminal.js

@@ -26,8 +26,8 @@ import { ps, psJson, psq } from './powershell.js'
 const WT = () => which('wt')
 const POWERSHELL_BIN = () => which('pwsh') || which('powershell')
 
-/** How much of the work area a window takes unless the mode asks for more. */
-const COVERAGE = 0.86
+/** How much of the work area a window takes, in every mode: the rest is margin. */
+const COVERAGE = 0.9
 
 /** The user32 declarations every window operation here needs, added once per PowerShell run. */
 const USER32 = `

package/server/launcher.js

@@ -100,25 +100,23 @@ export async function renameLive(story) {
 /** In driving mode the terminal has to be readable from across the room. */
 const DRIVING_FONT_SIZE = 22
 
-/** And a window worth glancing at from there takes the whole screen, not its usual share of it. */
-const DRIVING_COVERAGE = 1
-
-/** How big the text has to be right now: it depends only on the mode in force. */
+/**
+ * How big the text has to be right now: it depends only on the mode in force. The window does
+ * not: it keeps its usual share of the screen in every mode, because the margin around it is
+ * where you click to get past it.
+ */
 const fontSize = () => (isDriving() ? Promise.resolve(DRIVING_FONT_SIZE) : terminal.defaultFontSize())
 
-/** And how much screen the window takes. Undefined means "your usual share", whatever it is. */
-const coverage = () => (isDriving() ? DRIVING_COVERAGE : undefined)
-
 /**
  * Puts every window k0 owns the way the mode in force wants it, text and size in one gesture.
  * It runs on every mode change and once more at startup, which is what repairs the windows a
  * server restart left behind at the wrong size.
  */
 export async function applyModeToWindows(handles) {
-  return terminal.applyMode(handles, { fontSize: await fontSize(), coverage: coverage() })
+  return terminal.applyMode(handles, { fontSize: await fontSize() })
 }
 
-export const relayoutWindows = (handles) => terminal.relayout(handles, { coverage: coverage() })
+export const relayoutWindows = (handles) => terminal.relayout(handles)
 export const setWindowTitle = (handle, title) => terminal.setTitle(handle, title)
 export const focusWindow = (handle, title) => terminal.focus(handle, title)
 export const closeTerminal = ({ winId, pid }) => terminal.close({ handle: winId, pid })
@@ -209,7 +207,7 @@ export async function launch({ story, sessionId, mode = 'start' }) {
   if (autoSend) args.push(story.prompt.trim())
 
   const command = terminal.buildCommand({ cwd: story.project_path, bin, args, env: SESSION_ENV })
-  const winId = await terminal.open({ command, title: name, fontSize: await fontSize(), coverage: coverage() })
+  const winId = await terminal.open({ command, title: name, fontSize: await fontSize() })
   const up = await waitForSession(sessionId)
 
   if (autoSend) return { name, up, winId, pasted: true, autoSent: true }

package/web/board.js

@@ -2077,7 +2077,7 @@ async function boot() {
   whileVisible(refresh, 1000, 4000)
 
   // A direct link: k0 opened with the new story already in front of you.
-  if (location.hash === '#new' || location.hash === '#nuovo') openEditor(null)
+  if (location.hash === '#new') openEditor(null)
   // And the other direct link, the one the Usage page makes: a session's story, already open.
   const wanted = /^#story-(\d+)$/.exec(location.hash)
   if (wanted) {

package/web/files.js

@@ -956,7 +956,7 @@ function plate(data) {
   </div>`
 }
 
-const TITLE_KEYS = new Set(['title', 'titolo', 'name', 'nome'])
+const TITLE_KEYS = new Set(['title', 'name'])
 
 /**
  * Hand a path to the file manager. The same call for a file and for a folder: which of the two