WIP: Sign in to Commons with a Laboratorium account #41

Draft
ClaudiuSchuster wants to merge 11 commits from oss-oo/native-human-ui-20261024 into oss-oo/native-human-backend-20261024
Owner

Adds the Commons browser flow for signing in with a Laboratorium account, choosing an existing or new Commons profile, returning to personal needs, offers and work, and managing this browser's sessions. Public pages stay readable anonymously. Contribution is an explicit choice; before profile creation or linking, the page explains which name and account handle become public.

This UI remains stacked on #40 and uses the frozen v2 API contract. It clears private state across account changes/navigation and preserves uncertain-write recovery without replaying authentication proofs. The accepted Observatory avatar is preserved. Workshop proposals still have their separate private-receipt recovery path; the personal overview does not promise an absent proposal-owner listing.

Adds an operator-only real-browser acceptance mode using an isolated Native Core, unchanged Commons runtime with local SQLite, two exact HTTPS authorities and one owned Chromium process. The intended journey covers real login/consent, explicit profile creation, a pending private Participation card with native authorship, logout, a fresh browser context, finding the same card, duplicate refusal and anonymous non-disclosure. Source and tool manifests are explicit; there is no fake API/cookie/callback injection in this native mode.

Validation:

  • Earlier isolated browser UI fixtures passed 12 cases plus two disclosure cases; those use a fake API and remain clearly separated.
  • Current source checks include 47 Python cases normally and under -O, 34 Node contracts, provider-metadata cases and repository/Site/avatar checks. Independent review additionally exercises 28 safe offline cleanup/process/endpoint countercases.
  • The review found and closed premature host-fetch restoration during shutdown and stale CDP process/endpoint ownership. Isolation now lasts through handler drain; control remains bound to the same running process/starttime/listener and frozen WebSocket endpoint.
  • Native42 and Browser119 packets are byte-bound to this exact source. All 34 runtime inputs equal reviewed backend 0454dc47c43040145f2b45c43964529fd80d1583. That runtime separately passed the pure Native V8 Core/provider gate; it is not relabelled as a browser-engine or D1 product result.

The actual Native Browser V2 run of this exact head passes all 10 cases in Chrome 151 against isolated Core M602 and the unchanged Commons runtime. It exercises real login/consent, explicit profile choice, native author attribution, one pending Participation, anonymous non-disclosure, logout/revocation, a fresh browser context returning to the same identity and card, duplicate refusal, and the retained Observatory avatar. Two real token exchanges occurred; only one contribution was created. Untrusted TLS was rejected, and no bridge or Site script errors occurred.

Root independently re-read the completed invocation, all 119 unchanged source files and four packet files, and verified removal of the fixture's containers, network, volumes, database files, browser profiles and ephemeral credentials. This browser fixture uses local SQLite for Commons: Human graph migration, actual D1 Worker Binding and release/deployment remain separate gates. The PR stays draft until the required combined acceptance is complete.

Source head: 5fb9f586d7e41bf7353a7dbd4b540f3457870ca2
Tree: fd22f0917d9aaedc5b1865f7ad1aff76ac77e2de

Adds the Commons browser flow for signing in with a Laboratorium account, choosing an existing or new Commons profile, returning to personal needs, offers and work, and managing this browser's sessions. Public pages stay readable anonymously. Contribution is an explicit choice; before profile creation or linking, the page explains which name and account handle become public. This UI remains stacked on #40 and uses the frozen v2 API contract. It clears private state across account changes/navigation and preserves uncertain-write recovery without replaying authentication proofs. The accepted Observatory avatar is preserved. Workshop proposals still have their separate private-receipt recovery path; the personal overview does not promise an absent proposal-owner listing. Adds an operator-only real-browser acceptance mode using an isolated Native Core, unchanged Commons runtime with local SQLite, two exact HTTPS authorities and one owned Chromium process. The intended journey covers real login/consent, explicit profile creation, a pending private Participation card with native authorship, logout, a fresh browser context, finding the same card, duplicate refusal and anonymous non-disclosure. Source and tool manifests are explicit; there is no fake API/cookie/callback injection in this native mode. Validation: - Earlier isolated browser UI fixtures passed 12 cases plus two disclosure cases; those use a fake API and remain clearly separated. - Current source checks include 47 Python cases normally and under -O, 34 Node contracts, provider-metadata cases and repository/Site/avatar checks. Independent review additionally exercises 28 safe offline cleanup/process/endpoint countercases. - The review found and closed premature host-fetch restoration during shutdown and stale CDP process/endpoint ownership. Isolation now lasts through handler drain; control remains bound to the same running process/starttime/listener and frozen WebSocket endpoint. - Native42 and Browser119 packets are byte-bound to this exact source. All 34 runtime inputs equal reviewed backend `0454dc47c43040145f2b45c43964529fd80d1583`. That runtime separately passed the pure Native V8 Core/provider gate; it is not relabelled as a browser-engine or D1 product result. The actual Native Browser V2 run of this exact head passes all 10 cases in Chrome 151 against isolated Core M602 and the unchanged Commons runtime. It exercises real login/consent, explicit profile choice, native author attribution, one pending Participation, anonymous non-disclosure, logout/revocation, a fresh browser context returning to the same identity and card, duplicate refusal, and the retained Observatory avatar. Two real token exchanges occurred; only one contribution was created. Untrusted TLS was rejected, and no bridge or Site script errors occurred. Root independently re-read the completed invocation, all 119 unchanged source files and four packet files, and verified removal of the fixture's containers, network, volumes, database files, browser profiles and ephemeral credentials. This browser fixture uses local SQLite for Commons: Human graph migration, actual D1 Worker Binding and release/deployment remain separate gates. The PR stays draft until the required combined acceptance is complete. Source head: `5fb9f586d7e41bf7353a7dbd4b540f3457870ca2` Tree: `fd22f0917d9aaedc5b1865f7ad1aff76ac77e2de`
fix(commons): select native submit and pinpoint sign-in failures
All checks were successful
Repository checks / repository-baseline (pull_request) Successful in 25m31s
5fb9f586d7
All checks were successful
Repository checks / repository-baseline (pull_request) Successful in 25m31s
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin oss-oo/native-human-ui-20261024:oss-oo/native-human-ui-20261024
git switch oss-oo/native-human-ui-20261024

Merge

Merge the changes and update on Forgejo.
git switch oss-oo/native-human-backend-20261024
git merge --no-ff oss-oo/native-human-ui-20261024
git switch oss-oo/native-human-ui-20261024
git rebase oss-oo/native-human-backend-20261024
git switch oss-oo/native-human-backend-20261024
git merge --ff-only oss-oo/native-human-ui-20261024
git switch oss-oo/native-human-ui-20261024
git rebase oss-oo/native-human-backend-20261024
git switch oss-oo/native-human-backend-20261024
git merge --no-ff oss-oo/native-human-ui-20261024
git switch oss-oo/native-human-backend-20261024
git merge --squash oss-oo/native-human-ui-20261024
git switch oss-oo/native-human-backend-20261024
git merge --ff-only oss-oo/native-human-ui-20261024
git switch oss-oo/native-human-backend-20261024
git merge oss-oo/native-human-ui-20261024
git push origin oss-oo/native-human-backend-20261024
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
OSS-Singularity/website!41
No description provided.