trevato/forge-upstream
Public: anyone can read this; nobody can change it.
A software forge you can read in an afternoon and mold by hand.
- An app's terminal that runs without a cell ends with everything it started, on a hangup or its own exit
- The crew reads two words written in one millisecond in the order they were written
- A step that runs without a cell ends with everything it started, on a cancel, a timeout, or its own exit
- An app that runs without a cell stops with everything it started, and leaves no child running once it has gone
- The signup tool says what invite does now: an open invite link lets a person in, spent with the account
- Pack transfers at once follow the host's memory, so a 512 MiB cell does not run sixteen pushes and their hooks past its limit
- The quickstart says to run --first-admin beside the started forge, and shows spawning a child and making its admin from the same terminal
- A fresh forge's first account follows the signup setting and the Turnstile check like any other, now that no sign-up makes the admin.
- A preview builds on the droplet runner, as the release does: vxrail's push of the ~450 MB layer dies at the registry ingress (499)
- No sign-up makes the site admin, not even a forge's first account: only the operator's first-admin code, a claim or a seed makes one
- A fork's second proposal waits for the fork to follow its parent before landing more work, so it no longer races the follow on a slow machine
- The ceiling-reserve test's account says its origin, so main type-checks again now that createUser takes one
- The chart can set FORGE_TRUSTED_PROXIES and FORGE_CLIENT_IP_HEADER from optional values, unset by default.
- A run reserves its share of the account's daily ceiling when it starts, so runs started together cannot overshoot it.
- Each og card's cold-render budget is 300 ms on the machine it was set on, scaled by how much slower the plain card renders on this one
- Tests that start a notifier close it, so its pager does not outlive the test and log errors into the next file's counts
- An invite link opens signup once while signup is invite: the form, the passkey door and the API take its token, and the account and the invite's use are one write
- The ring's 31-day test holds its 5 s budget scaled to this machine, measured against plain inserts of the same points
- A hosted child keeps its parent's scheme and port: a child of http://forge.lan:8080 is http://kid--forge.lan:8080, not https://kid--forge.lan
- The OpenID configuration lists only the scopes the forge grants, and the MCP signup tool says what the setting does
- Archive and Wake are each one conditional write that acts only when it moved the repository, and a Wake asked during an Archive's stop starts production after that stop
- The hollow audit fits a 512 MiB check runner: it collects each file's syntax tree as it goes, and the command's test runs in its own process