coulomb/railiance-apps
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Correct composed validation scope and retain the initial fixture skip
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a14bfc-9643-7872-aa12-98326dcf25e7
This commit is contained in:
tegwick 2026-10-18 12:21:03 +02:00
parent a927ec8cc8
commit ab3cf5cdc5
2 changed files with 9 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
workplans/RAPPS-WP-0016-forgejo-netkingdom-login.md
View file

@ -316,8 +316,10 @@ Mandatory owner application-tenant/current-token admission, ID-token purpose,
exact signed RS256 at_hash, current status before/after the PDP, and signed
identity/assurance/authentication-time/tenant-provenance joins refuse substitution
and stale authority. The latest focused callback/identity suite passes 91 results
without skips; the selected four composed packages passed 114 results with one
optional PostgreSQL test skipped before the additional owner-tenant regression.
without skips; the final selected four composed packages pass 116 results without
skips. The earlier 114-pass run skipped the private file-replacement check because
its reused fixture directory was exhausted; a fresh private/read-only fixture
restores that check. The original skip is retained, not PostgreSQL evidence.
The actual HTTP PKCE/discovery/UserInfo/status/revocation and Forgejo provider /
callback pass five fresh consumer processes: two current grants accepted, mixed
pair/revoked original/suspended human refused. The original verifier and issuer