PR #33487 real-environment verification, 2026-11-15 Main: f2839735ef; PR: ec917bb3bfeecd39d0c19c96a730e86921a5e3fa Linux, real Forgejo 13 Docker service, real fj v0.7.0, Chrome via repo Playwright. No mocked executable, API, fixture or demo data. $ fj --host http://127.0.0.1:3300 whoami currently signed into maria-verify [host 127.0.0.1:3300] $ fj --host https://127.0.0.1:3300 whoami Error: error sending request for url (https://127.0.0.1:3300/api/v1/user?) Caused by: 0: client error (Connect) 1: received corrupt message of type InvalidContentType Main Settings > Source control: Could not verify Forgejo / Gitea. Could not reach https://127.0.0.1:3300 to verify the fj login. The original unauthenticated message no longer reproduces on current main; #34777 already changed transport failures to unknown. PR authenticated WebSocket API, same server service as the web client: server.discoverSourceControl => { "status": "unknown", "account": { "_tag": "None" }, "host": { "_tag": "Some", "value": "127.0.0.1:3300" }, "detail": { "_tag": "Some", "value": "fj has credentials for this host, but it did not answer over HTTPS. fj stores no scheme; HTTP-only servers are used through a project with an explicit http:// remote." } } Standalone discovery packet capture (loopback tcp port 3300): 11 packets, one TCP connection, TLS ClientHello then plaintext HTTP error; zero plaintext GET requests and no HTTP retry. { "tag": "sourceControl.lookupRepository", "payload": { "provider": "forgejo", "repository": "http://127.0.0.1:3300/maria-verify/http-auth-verification", "cwd": "/home/user/verification-repo" }, "result": { "_tag": "Success", "value": { "provider": "forgejo", "nameWithOwner": "maria-verify/http-auth-verification", "url": "http://127.0.0.1:3300/maria-verify/http-auth-verification.git", "sshUrl": "ssh://git@localhost/maria-verify/http-auth-verification.git" } } } { "tag": "sourceControl.lookupRepository", "payload": { "provider": "forgejo", "repository": "http://127.0.0.1:3300/maria-verify/http-auth-verification", "cwd": "/home/user/verification-repo" }, "result": { "_tag": "Failure", "cause": [ { "_tag": "Fail", "error": { "_tag": "SourceControlRepositoryError", "provider": "forgejo", "operation": "lookupRepository", "detail": "The source control operation could not be completed.", "cause": { "name": "SourceControlProviderError", "message": "Source control provider forgejo failed in getRepositoryCloneUrls: Authenticate this server with `fj auth login`, `fj auth add-token`, or `tea login add`.", "cause": { "name": "ForgejoCliError", "message": "" } } } } ] } } { "tag": "pullRequests.list", "payload": { "state": "open", "projectId": "d6c0c107-a09e-433a-ad7c-03eec2561788", "limit": 10 }, "result": { "_tag": "Success", "value": { "viewers": { "127.0.0.1:3300": "maria-verify" }, "providers": [ { "host": "127.0.0.1:3300", "kind": "forgejo", "searchesOnHost": false, "actions": [ "merge", "close", "reopen", "update-branch" ], "projectCount": 1, "configured": true, "detail": null } ], "entries": [], "errors": [], "truncated": false, "nextCursors": {} } } } Rejected-token check: real fj credentials replaced through fj auth logout/add-token; explicit HTTP lookup failed with authentication guidance. Real token restored and HTTP lookup succeeded again. Both app instances: project added through Add project > Local folder, thread created with Codex gpt-6.1-sol through web composer. Real provider read README.md and answered first heading # http-auth-verification. PR persisted run.updated status completed and model gpt-6.1-sol. No source edits. Blacksmith: vp test run packages/source-control-forgejo/src/server/ForgejoSourceControlProvider.test.ts => 51/51 passed. Existing head CI: 33 successful, 0 failing, 0 pending. Not exercised: native desktop/mobile, macOS/Windows, TLS-enabled Forgejo, tea CLI, remote relay/tunnel. Recording shows final settings and completed real turn; it is not a provider latency benchmark.