Commit Graph
133 Commits
Author SHA1 Message Date
istos 68ee681c18 board: 33 → in-progress (istos) 2026-07-31 11:51:50 +02:00
istos bca3f3055e board: 32 → done (istos) 2026-07-31 11:51:49 +02:00
Ronald AshriandGitHub 80c58195ee Merge pull request #27 from 12vectors/task/32-serve-bench-12vectors-com-from-a-worker
32 — Serve bench.12vectors.com from a Cloudflare Worker
2026-07-31 11:51:41 +02:00
istos 25b55d5734 board: 32 PR opened (istos) 2026-07-31 11:49:17 +02:00
istos 0ff6457cae board: 32 → review (istos) 2026-07-31 11:49:09 +02:00
istosandClaude Opus 5 6c06583109 site: serve bench.12vectors.com from a Cloudflare Worker
site/wrangler.jsonc puts site/dist/ behind bench.12vectors.com as static
assets. No `main`: the site is files, and a Worker with no script is the
cheapest correct way to serve them.

  html_handling      force-trailing-slash, so /x redirects to /x/ — the
                     url the pages link and rel=canonical names. One
                     page, one address; no url ends in .html.
  not_found_handling 404-page, so an unknown path gets dist/404.html
                     with a 404 status rather than the landing page
                     with a 200.
  routes             bench.12vectors.com as a custom domain. Cloudflare
                     takes the hostname at the zone level and makes the
                     DNS record; nothing else on 12vectors.com moves.

site/root/_headers carries the response policy. HTML revalidates on
every view, so a deploy is visible on the next reload without anyone
clearing a cache; /static/* is kept for a year and never re-checked,
which is safe because the stylesheet and icon urls carry a hash of their
contents. The general rule is written first and the specific one second,
so a host that merged the two instead of overriding would still land on
max-age=0 — the safe side. Alongside it the baseline a public page owes:
nosniff, a referrer policy, a year of HSTS without preload,
X-Frame-Options, and a default-src 'none' CSP that makes "no analytics,
no third-party anything" something the browser enforces rather than
something a test asserted once.

Deploys are run by hand, as releases already are — no Cloudflare token
in repository secrets, no first deploy pipeline. site/README.md names
the account, the Worker, the route and the four-command sequence, plus
the four things to check after a deploy that no test here can reach.

The tests cover everything before Cloudflare: that the config says what
the site needs, that the build writes the files it names, and that
wrangler.jsonc, pages.json and README.md cannot drift apart about which
domain this is. A live response is not among them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 11:47:12 +02:00
istosandClaude Opus 5 ad639a33d3 site: a 404 page, a root/ tree, and stamped asset urls
Three things the build owed the host before the site could have an
address, all of them visible in site/dist/ rather than in a deploy
script.

A 404 page. Cloudflare's not-found handling serves a literal 404.html
from the root of the assets directory, so a route may now name an .html
file instead of ending in "/" — the one that does is /404.html, a normal
manifest entry with its own layout. It is the site's design and the
site's nav, with a way back to the landing page, a noindex and no
canonical. A null section keeps it off the nav it renders.

site/root/, copied verbatim to the TOP of the build the way static/ is
copied to a subdirectory of it. _headers is what it holds; the host
reads that file from the root and nowhere else. A file in root/ that a
route would also write stops the build rather than letting one silently
win.

Stamped urls for the stylesheet and the icon: the templates link them
through $stylesheet and $icon, which carry a ?v=<hash> of the file's own
contents. Nothing in static/ is renamed, so the tree and the /static/*
glob stay as they were — but the url changes when the file does, which
is what will make a year-long immutable cache safe.

Tests ask the builder where a route lands rather than keeping their own
copy of the rule.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 11:46:56 +02:00
istos 6828bd8c19 board: 32 → in-progress (istos) 2026-07-31 11:34:06 +02:00
istos a36242e4fe board: 31 → done (istos) 2026-07-31 11:33:32 +02:00
Ronald AshriandGitHub 6088035356 Merge pull request #26 from 12vectors/task/31-minisite-skeleton-and-build
31 — Stand up site/ and generate its pages from the repo's own markdown
2026-07-31 11:33:25 +02:00
istos 1b5cd1495f board: 31 PR opened (istos) 2026-07-31 11:32:34 +02:00
istos 1a55dc46df board: 31 → review (istos) 2026-07-31 11:31:50 +02:00
istosandClaude Opus 5 1f8a98eb5f tests: cover the site build, and say out loud that site/ never ships
The generated site's whole value is that drift is loud, so the tests
are mostly about drift: a heading renamed in AGENTS.md must fail the
build naming the route and the heading, a slice emptied to its heading
must fail rather than emit a page, and a heading inside a code fence
must never match — AGENTS.md fences a task template whose first line is
'# Task title', and matching that would slice the document in half.

Alongside: link rewriting (GitHub blob, link_routes overrides, dead and
escaping links refused), manifest validation, the output-directory
guard, and the acceptance criterion that no built page fetches anything
third-party — mechanised as 'every rel that opens a connection is
same-origin', with rel=canonical excluded because it is a statement,
not a fetch.

The release artifact test now asserts site/ is absent from bench.tar.gz.
The manifest already excludes it by saying nothing about it, but
correct-by-omission is exactly what a future manifest edit undoes
silently.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 11:30:43 +02:00
istosandClaude Opus 5 62caafe157 site: a minisite generated from the repo's own markdown
bench has no public page. site/ is the machinery for one: a manifest,
a generator, two layouts from the turn-2 docs design, and the Daylight
half of the board's own token set.

Nothing here is transcribed. Every page body is a heading slice of a
file that already documents bench, and site/pages.json is the only
place that mapping is written down — the IA is editorial judgement, so
it lives in one readable file rather than in a directory convention.

The point is the failure: a from/to heading the source no longer
contains stops the build naming the route, the file and the heading,
and every page renders before the output directory is touched, so a
drifting rebuild leaves the last good build standing instead of
replacing it with an empty one. Repo-relative links come out as site
routes or GitHub links; a dead one stops the build too.

Rendering is markdown-it-py, pinned in site/requirements.txt. The
stdlib-only law binds manager/core/ — the tool people install — and
site/ is neither shipped nor installed, so a hand-rolled parser would
have been risk spent in the wrong place on a document that leans on
fenced code, nested lists and inline code throughout.

Templates are string.Template: $name substitutes and a literal dollar
doubles, because str.format's braces collide with every line of CSS.

Fonts are self-hosted and same-origin: no page bench serves may need a
request to a third party to be read. fetch-fonts.py downloads the seven
woff2 files once; until they are there the build says which are missing
and the pages fall back to the system stack.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 11:30:34 +02:00
istos eafd1ad546 board: 31 → in-progress (istos) 2026-07-31 11:12:41 +02:00
istos 66c6ce0165 board: 30 → done (istos) 2026-07-31 11:12:41 +02:00
Ronald AshriandGitHub ebe33eef87 Merge pull request #25 from 12vectors/task/30-docs-design-on-true-bench-content
30 — Re-cut the docs design on content bench actually has
2026-07-31 11:12:33 +02:00
istos 7dc336d33f board: 30 PR opened (istos) 2026-07-31 11:10:18 +02:00
istos e304829a26 board: 30 → review (istos) 2026-07-31 11:10:09 +02:00
istos 66f06b96b9 docs design: turn 2 of Bench Docs on real bench content
Turn 1 of the docs design wrapped three good layouts around invented
content — a bench.toml, a brew-installed CLI, "lanes", a handoff rule
engine, port 7331, PAS-411 cards. None of it exists. Turn 2 holds all
three layouts and replaces every word, label and code block with the
product AGENTS.md, README.md and manager/core/.env.example describe.

  1b Dockside — hero terminal is the real install one-liner, the real
    first-run questions and the real board.py startup lines on 26071.
    The six doors are install, the five stages, agents on the board,
    PRs & review, team mode, the three-layer law.
  1a Harbour — the article is "Claiming a card": what each move writes
    to **Assignee:**, the two local/.env keys that turn it on, and the
    board: <n> → <stage> (<name>) commit it makes.
  1c Logbook — the CLI reference is now a settings reference, with
    BOARD_SYNC as the shown key and the board's own activity log (real
    event strings from sync.py, agents.py and github.py) in the pinned
    console.

The design project's write path needs an interactive permission grant,
which a headless run cannot answer, so the finished file lands here as
reference/bench-docs-design-turn2.dc.html for a human to upload as
"Bench Docs.dc.html". The card scoped itself to the design project with
no repo files changed; this one file is the deviation, and a git rm
undoes it once the upload has happened.
2026-07-31 11:09:42 +02:00
istos 163e705e45 board: 30 → in-progress (istos) 2026-07-31 10:59:20 +02:00
istos 1161552f8b board: 29 → done (istos) 2026-07-31 10:27:52 +02:00
Ronald AshriandGitHub 098f83fc3b Merge pull request #24 from 12vectors/task/29-first-run-writes-local-env
29 — A first run writes local/.env, asking the questions it can't guess
2026-07-31 10:27:44 +02:00
istos 086f1bd76f board: 29 PR opened (istos) 2026-07-31 07:56:33 +02:00
istos 6cb7fc7eee board: 29 → review (istos) 2026-07-31 07:56:24 +02:00
istosandClaude Opus 5 635205486b A first run writes local/.env, asking what it cannot guess
A project could run bench for months without a manager/local/.env:
everything fell back to core/.env.example, so the two settings that
change what bench is — claim-on-move and syncing through origin/main —
were invisible to anyone who had not read that file.

install.py now writes it on a first run. It asks three questions no
default can be right about (solo or team, which agent adapter, the
project's test command) and writes core/.env.example with the answers
substituted into their lines, comments and all keys intact — so the
written file is where the project reads what else it can change.

- Runs after first_boot_clean: .env is one of the two things the
  first-boot guard reads, so writing it earlier would skip the clean.
- Never asks without a terminal on stdin. install.py sits on the path
  of start.sh, update.sh and every hook, so no TTY prints one line and
  carries on rather than blocking a board start on an invisible prompt.
  --dry-run reports the questions and writes nothing.
- An existing .env is never touched; --setup is the only way back to
  the questions, pre-filling from the current file and rewriting it in
  place, so start.sh's fallback BOARD_PORT line survives.
- Bare Enter takes every default (the result is the example verbatim,
  i.e. today's behaviour exactly); Ctrl-D skips the rest.

start.sh needed no change — it already calls install.py before the port
dance, which is the right order. Tests drive the interactive runs over a
real pty and the non-interactive ones with /dev/null on stdin.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 07:55:57 +02:00
istos 96fcae7d8c board: 29 → in-progress (istos) 2026-07-31 07:45:15 +02:00
istos 8ab97398a5 board: 10 → done (istos) 2026-07-30 15:10:59 +02:00
Ronald AshriandGitHub b06d030fd3 Merge pull request #23 from 12vectors/task/10-review-launches-die-on-multiedit-deny-rule
10 — Review launches die at startup: MultiEdit deny rule names a tool that no longer exists
2026-07-30 15:10:55 +02:00
istos c9fbf17775 board: 10 PR opened (istos) 2026-07-30 15:10:23 +02:00
istos 152bbdd7f3 board: 10 → review (istos) 2026-07-30 14:34:51 +02:00
istosandClaude Opus 5 47779a35bc Assert the review launch's flag list whole, and say why it moves
The MultiEdit deny rule was already dropped in the hotfix; this is task
10's follow-up half — the guard that catches the next fossil.

The claude adapter's review branch spells "cannot edit files" in the
vendor's own tool names, and that roster moves: a rule naming a tool the
installed CLI does not have is refused at startup, so the launch dies
before the agent speaks. Membership assertions could not see that
happening, so the stub-binary test now asserts each mode's flag list
literally (settings payload elided) — a deny name added or renamed shows
up as a diff a reviewer must re-verify against the installed CLI. The
run script carries the same warning where the list actually lives.

The helper drops a leaked AGENT_MODEL, since --model would otherwise
appear in an argv now compared whole; test_agent_model.py owns that flag.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-30 14:34:19 +02:00
istos 3fed71246c board: 25 → to-do (istos) 2026-07-30 14:26:50 +02:00
istos 1f1cf3cc74 board: 28 → to-do (istos) 2026-07-30 14:26:45 +02:00
istos 63ddfe4b95 board: 27 → to-do (istos) 2026-07-30 14:26:43 +02:00
istos f2bd570f59 board: 10 → in-progress (istos) 2026-07-30 14:26:41 +02:00
istosandClaude Fable 5 ae9f10e3d0 Cards 27, 28: update offers to commit itself; a pinned port stays pinned
Both from the first downstream 0.2 update report: the vendored diff
left as homework in a clean-main workflow, and the TIME_WAIT port hop
that rewrote an explicit BOARD_PORT pin.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-30 14:25:14 +02:00
istosandClaude Fable 5 a5dd0ac565 Version 0.2-alpha
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
v0.2-alpha
2026-07-30 14:15:14 +02:00
istos f64afcfd92 board: 11 → done (istos) 2026-07-30 14:13:20 +02:00
Ronald AshriandGitHub 8d1e84819d Merge pull request #22 from 12vectors/task/11-failed-agent-runs-must-be-visible
11 — A failed agent run must leave a visible trace on the card
2026-07-30 14:13:11 +02:00
istosandClaude Fable 5 c2cf1e92c0 Card 26: forge adapters — core stops speaking GitHub
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-30 14:12:06 +02:00
istos 780cdf97f4 board: 11 PR opened (istos) 2026-07-30 13:11:03 +02:00
istos 55a5d2a781 board: 11 → review (istos) 2026-07-30 13:10:55 +02:00
istosandClaude Opus 5 d94b6ee423 A failed run is a state the card wears
An agent that exits non-zero was the least-handled outcome on the board:
one ticker line that scrolled away, a card that looked exactly as it did
before the launch, and the log's contents — usually the whole story — left
on disk. Three launches died in an API outage and the board said nothing a
person would notice.

So the outcome is recorded on the run: exit code, ended-at, and the
cleaned tail of its log as the excerpt (a launch that died before the
agent spoke says so rather than showing blank). From that the card takes
the alarm border and a `run failed` pill, with the excerpt on hover and in
full in the card sheet; a toast fires, because failures are rare and
actionable; and the ticker line stays, now naming what the log ended on.

Every headless kind lands in _finish, so work, act-pr, PR review and the
relevance check are all covered. The state is scoped to the run and the
stage: the next launch supersedes it, and the watcher drops it when the
card moves, so nothing follows a card into review/.

The way is cleared for the relaunch too: a failed run with no commits has
its worktree and empty branch removed — the reasoning a decline already
uses — so ▸ start work works without a hand `git worktree remove`. A
failed run with commits keeps its worktree.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-30 13:10:26 +02:00
istos 3693b66574 board: 11 → in-progress (istos) 2026-07-30 12:54:59 +02:00
istos 829a764870 board: 21 → done (istos) 2026-07-30 12:51:35 +02:00
Ronald AshriandGitHub 64ad311267 Merge pull request #20 from 12vectors/task/21-shebang-means-executable
21 — A shebang means executable: fix the shipped modes and test the invariant
2026-07-30 12:51:27 +02:00
istos eb29af4977 board: 24 → done (istos) 2026-07-30 12:51:17 +02:00
Ronald AshriandGitHub 5eed46d963 Merge pull request #21 from 12vectors/task/24-model-chip-beside-the-agent-name
24 — A model chip beside every agent name
2026-07-30 12:51:12 +02:00
istos 663552f5db board: 24 PR opened (istos) 2026-07-30 12:05:02 +02:00