Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
| Comment: | Register asks again for an approved login, printing the approve link
Intent: let a login an admin approved be asked again for other letters with one more press, as the maintainer expected register to do (ocx-console post 13dfe73616). Collect refused a code other than the approved one with a text register took as a failure, so no link was printed (bootstrap-qcow2 post 774683323c). Expression: collect now refuses another code as "approved for another code, and for this one it is not approved yet", so register prints the approve link for its new code. Approve already sets a login it made with exactly the letters asked and a new password. docs/invite.md says to ask for the whole set of letters and that the old password stops working. docs/interfaces.md says the same, and the done row leaves docs/backlog.md. The admin's press stays the only protection, as it is for a first ask. Demonstrates: spec/ocx/logins_spec.cr, "registers from the asker's own machine": from a new file, the link asks goi24; once pressed, the login holds exactly goi24 with a new password, and the old one no longer signs in. crystal run ci.cr is green: 713 examples, 0 failures, coverage 100.0%. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TUH8KKBs1b4wzoSCq6zh7U |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | connector-oauth |
| Files: | files | file ages | folders |
| SHA3-256: |
05ad8112985e9541e0c5b24da2392eb0 |
| User & Date: | x86-1-session 2026-11-09 05:45:28.909 |
|
2026-11-09
| ||
| 11:29 |
Pin the client and server builds to BQ2's seed with ARM and AArch64
Intent: let x86-1's client be rebuilt from BQ2's seed whose LLVM targets X86, ARM and AArch64, which Glint needs to build for ARM, as the maintainer asked (ocx-console post 688e1532c9, relayed in ollama post b28a74c516). Expression: ocx-rootfs/build-rootfs.cr's SEED names bq2-seed-x86_64-0b99a242bf.tar.gz, sha256 0c93201ba563033f8100a436e9e7a6283b931263c4b753f8cf5e5c5d11d122c4, as BQ2 reported it (bootstrap-qcow2 post b337765b1c). The seed is not on the server yet, so the builder puts it in DOWNLOADS under that name; fetch refuses any other content. Demonstrates: ocx-rootfs/build-rootfs.cr compiles (crystal build --no-codegen ocx-rootfs/build-rootfs.cr). crystal run ci.cr ran 713 examples with 0 failures, but went over its 180 s limit (262 s) while the host's load was 17 on 8 CPUs. The build from this seed is shown when it is run on x86-1's host. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TUH8KKBs1b4wzoSCq6zh7U check-in: af38773c64 user: x86-1-session tags: connector-oauth | |
| 05:45 |
Register asks again for an approved login, printing the approve link
Intent: let a login an admin approved be asked again for other letters with one more press, as the maintainer expected register to do (ocx-console post 13dfe73616). Collect refused a code other than the approved one with a text register took as a failure, so no link was printed (bootstrap-qcow2 post 774683323c). Expression: collect now refuses another code as "approved for another code, and for this one it is not approved yet", so register prints the approve link for its new code. Approve already sets a login it made with exactly the letters asked and a new password. docs/invite.md says to ask for the whole set of letters and that the old password stops working. docs/interfaces.md says the same, and the done row leaves docs/backlog.md. The admin's press stays the only protection, as it is for a first ask. Demonstrates: spec/ocx/logins_spec.cr, "registers from the asker's own machine": from a new file, the link asks goi24; once pressed, the login holds exactly goi24 with a new password, and the old one no longer signs in. crystal run ci.cr is green: 713 examples, 0 failures, coverage 100.0%. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TUH8KKBs1b4wzoSCq6zh7U check-in: 05ad811298 user: x86-1-session tags: connector-oauth | |
|
2026-11-08
| ||
| 18:21 |
A run from R alone may share under any name; y is the protection
Intent: the maintainer decided that a share needs no name rule: "if it is in uv, it should be replaceable ... anyone with y can write it—that is our one and only protection from it being overwritten in real life. don't produce machinery that can't work." (ocx-console post 7085f98c83, relayed in ollama forum post 98286416a9). So each architecture's BQ2 seed can be one file, replaced at each build. Expression: Bounds.wider no longer refuses a share whose name lacks $$run$$; its other rules stand, ends_with_parent among them. HISTORY.md decision 133 amends decisions 107 and 132; protocol v2's refusal 1 drops the clause. The rule itself is written into Parsimony in README.md, with no guard spec, since none can check it (ollama forum post b4cb02763c: the maintainer repeated "don't make machinery that can't work" of a spec for it). Demonstrates: spec/ocx/decisions_spec.cr: a run from R alone sharing under builds/$$run$$/x, ocx2-release.tar, seed/x86_64.qcow2 or $$process_user$$run$$ starts. crystal run ci.cr: 713 examples, coverage 100.0%; its three failures, two the known rcvfrom lock (ticket 00817df826) and one a compiler's stdin read, pass rerun. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TUH8KKBs1b4wzoSCq6zh7U check-in: afd3df339f user: x86-1-session tags: connector-oauth | |