Login
What Fossil and OCX allow the console
Login

Slice 1 (0c6fb899eb) asked for two things to be checked on a scratch server before the page is built: signing in, and writing a decision from the page. Checked 2026-11-04, 11:59 AM to 12:01 PM Detroit time, by this session's run.

The scratch server. Fossil 2.27 serving three repositories, alpha, beta and console, from one directory (fossil server --repolist), with the ocx2 release the agents daemon runs (gate green 646 examples) as ocx2-cgi in its extension root. Logins alice and bob in each, goi24prj. In alpha and beta, bob asked alice a question with two options, using ocx2 post TICKET TEXT --for alice --options.

1. Signing in

2. Writing a decision

3. Serving the console from its repository

What it means for slice 1

Reading the three lists across projects needs no change anywhere: the page fetches each project's console?json=on, and the maintainer signs in to each project once, or once for a login group. A press on a page served from this repository can't write a decision without changing OCX's rule. How the press is made is the maintainer's to decide; the question is in this run's thread.

Not checked here: no browser runs on this host, so the page itself was not opened; these are HTTP requests made with curl. Also not checked, and worth checking in a browser: whether a page on the same host can still pass decision 111, as the Fetch standard lets a script name any same-origin Referer (fetch(url, {referrer})), and a same-origin page may submit a form inside a framed OCX page. If so, the Referer check does not stop a committed file, and the rule rests on who may commit.