WIP: Add native human backend and isolated provider acceptance harness #40

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

Implements the disabled backend for native human sign-in, explicit legacy-account linking and browser sessions on the prepared identity-human schema. One-time OIDC/PKCE flows use a maintained, reproducibly bundled client. Successful completion and resource writes check identity, revocation and session state inside the same database transaction, preserving existing actor identities and contribution graphs.

Adds the explicit eleven-module offline code profile and an isolated Native Core/provider acceptance harness. The provider adapter verifies RS256/JWKS, nonce, exact issuer/client/subject, effective scopes through maintained-library introspection, and authenticated native self lookup. The frozen browser HTTP/API and schema contracts remain unchanged. Runtime schema admission now separates the one exactly observed D1 provider table from a complete application metadata fingerprint, including implicit indexes. Unexpected tables, indexes, provider definitions or lineage remain rejected. This PR stays stacked on #38; browser UI delivery is separate.

Validation:

  • Independent backend/runtime and harness source review passed. Current harness checks pass: 31 Python cases normally and under -O, 24 Node cases, syntax, diff and frozen-source checks.
  • The actual isolated Native V8 run on this harness 5db46e9f46b87601ef984840c292f6604d6f38f2 and reviewed runtime baseline 0454dc47c43040145f2b45c43964529fd80d1583 passes all 12 cases against the separately built and audited Core image from 602bedc4ab1047c3db634da3fd1be4e86c15e712, including its integrated OAuth Basic form-decoding correction. Image: sha256:df7bffe5396d99cb6d54911511891bb5176eadab01147158e726df5dd53d929e.
  • Native checks cover discovery and account/application setup, PKCE/RS256 and exact int64 identity, minimal scopes and private/limited visibility, single-use callback and nonce rejection, a lost successful exchange without replay, session guards, logout/revocation, rejection of old broad grants and foreign-client tokens, and application revocation.
  • Root independently checked the completed invocation, unchanged 41-file source packet and removal of the fixture's containers, network, database files and ephemeral credentials. The Commons database side of this fixture uses local SQLite; this is not a D1 or browser-engine result.

The current source CI passed. The provider-metadata change also has independent source acceptance: 53 targeted cases, 135 existing Identity/Session/Business cases and 12 countercases passed; the same new test on the previous actor source fails in the five expected places. Native V8 independently confirms the complete updated runtime against the real isolated Core. Historical V7 remains a separate receipt for its earlier source.

The real D1 REST transaction rehearsal is covered separately by #42. Full Human graph migration, Worker Binding behavior, the complete real-browser journey, and release/deployment remain open gates. Production Core and Commons remain unchanged; no production provider registration, database migration or activation is claimed.

Source head: 5db46e9f46b87601ef984840c292f6604d6f38f2
Tree: 93c84cf5d444ed05925b2c5c130913f0ae3359a6

Implements the disabled backend for native human sign-in, explicit legacy-account linking and browser sessions on the prepared identity-human schema. One-time OIDC/PKCE flows use a maintained, reproducibly bundled client. Successful completion and resource writes check identity, revocation and session state inside the same database transaction, preserving existing actor identities and contribution graphs. Adds the explicit eleven-module offline code profile and an isolated Native Core/provider acceptance harness. The provider adapter verifies RS256/JWKS, nonce, exact issuer/client/subject, effective scopes through maintained-library introspection, and authenticated native self lookup. The frozen browser HTTP/API and schema contracts remain unchanged. Runtime schema admission now separates the one exactly observed D1 provider table from a complete application metadata fingerprint, including implicit indexes. Unexpected tables, indexes, provider definitions or lineage remain rejected. This PR stays stacked on #38; browser UI delivery is separate. Validation: - Independent backend/runtime and harness source review passed. Current harness checks pass: 31 Python cases normally and under `-O`, 24 Node cases, syntax, diff and frozen-source checks. - The actual isolated Native V8 run on this harness `5db46e9f46b87601ef984840c292f6604d6f38f2` and reviewed runtime baseline `0454dc47c43040145f2b45c43964529fd80d1583` passes all 12 cases against the separately built and audited Core image from `602bedc4ab1047c3db634da3fd1be4e86c15e712`, including its integrated OAuth Basic form-decoding correction. Image: `sha256:df7bffe5396d99cb6d54911511891bb5176eadab01147158e726df5dd53d929e`. - Native checks cover discovery and account/application setup, PKCE/RS256 and exact int64 identity, minimal scopes and private/limited visibility, single-use callback and nonce rejection, a lost successful exchange without replay, session guards, logout/revocation, rejection of old broad grants and foreign-client tokens, and application revocation. - Root independently checked the completed invocation, unchanged 41-file source packet and removal of the fixture's containers, network, database files and ephemeral credentials. The Commons database side of this fixture uses local SQLite; this is not a D1 or browser-engine result. The [current source CI](https://oss-oo.io/OSS-Singularity/website/actions/runs/125) passed. The provider-metadata change also has independent source acceptance: 53 targeted cases, 135 existing Identity/Session/Business cases and 12 countercases passed; the same new test on the previous actor source fails in the five expected places. Native V8 independently confirms the complete updated runtime against the real isolated Core. Historical V7 remains a separate receipt for its earlier source. The real D1 REST transaction rehearsal is covered separately by #42. Full Human graph migration, Worker Binding behavior, the complete real-browser journey, and release/deployment remain open gates. Production Core and Commons remain unchanged; no production provider registration, database migration or activation is claimed. Source head: `5db46e9f46b87601ef984840c292f6604d6f38f2` Tree: `93c84cf5d444ed05925b2c5c130913f0ae3359a6`
ClaudiuSchuster changed title from WIP: Add native human sign-in and atomic browser sessions to WIP: Add native human backend and isolated provider acceptance harness 2026-10-25 01:07:19 +00:00
test(commons): sanitize first native token failure diagnostics
All checks were successful
Repository checks / repository-baseline (pull_request) Successful in 25m32s
8d5f5a60d8
test(commons): pin audited native Human Core candidate
All checks were successful
Repository checks / repository-baseline (pull_request) Successful in 25m20s
4996edb20e
fix(commons): admit exact D1 provider schema metadata
All checks were successful
Repository checks / repository-baseline (pull_request) Successful in 10m7s
0454dc47c4
test(commons): bind native fixture to admitted backend baseline
All checks were successful
Repository checks / repository-baseline (pull_request) Successful in 9m43s
5db46e9f46
All checks were successful
Repository checks / repository-baseline (pull_request) Successful in 9m43s
This pull request is marked as a work in progress.
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-backend-20261024:oss-oo/native-human-backend-20261024
git switch oss-oo/native-human-backend-20261024

Merge

Merge the changes and update on Forgejo.
git switch oss-oo/native-human-schema-20261024
git merge --no-ff oss-oo/native-human-backend-20261024
git switch oss-oo/native-human-backend-20261024
git rebase oss-oo/native-human-schema-20261024
git switch oss-oo/native-human-schema-20261024
git merge --ff-only oss-oo/native-human-backend-20261024
git switch oss-oo/native-human-backend-20261024
git rebase oss-oo/native-human-schema-20261024
git switch oss-oo/native-human-schema-20261024
git merge --no-ff oss-oo/native-human-backend-20261024
git switch oss-oo/native-human-schema-20261024
git merge --squash oss-oo/native-human-backend-20261024
git switch oss-oo/native-human-schema-20261024
git merge --ff-only oss-oo/native-human-backend-20261024
git switch oss-oo/native-human-schema-20261024
git merge oss-oo/native-human-backend-20261024
git push origin oss-oo/native-human-schema-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!40
No description provided.