Relay 0.32: merge the release branch into main, with the badge column carried onto the new write path #256
Assignees
extant2000git
Clear assignees
extant2000git
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: extant2000/flamenet-relay#256
Reference in New Issue
Block a user
Closes the relay side of the 0.32 unification. Replaces #243, which cannot merge: wave 2 landed on main while that branch sat, and the two sides rewrote the same send path.
The resolution that mattered
Wave 2 extracted the envelope write, the in-process wake and the APNs push into
Delivery.write. This branch still had the inline version, plus one thing wave 2 knew nothing about: theannouncedcolumn, which is what the iPhone badge counts.The extraction is kept.
Delivery.Itemgainsannounced, defaulting false exactly asEnvelope.initdoes, andDelivery.insertwrites it. Without that, the model, the migration andbadgeCountwould all have merged cleanly and every badge would have read zero, because nothing on the surviving path ever set the column. The submit route passes!silent; a federated deposit passes false, since nothing announced it.The rest
docs/CONFIGURATION.mdtakes the union: main listed six outbound connections with the setting that enables each, this branch added the Today fetch and dropped the other five. Seven are listed now.PostgresMigrationTestskeeps both sides' tests, with theLockedRowsactor left last in the file..e2e-refmoves tod0274ca0, the current flamenet-e2e main. The old pin was310c315, a branch head that was not on main at all.The generated pages were regenerated, not resolved
check-doc-pages.pyreported spec, audit, engine and self-hosting all stale against their sources, so three of the eight conflicts were in files nobody should edit by hand.Scripts/build-doc-pages.shran against the new pin and all nine pages now match their sources.That also fixes the spec page's section numbers. flamenet-e2e moved anonymous reads and contact links to §8.13 and §8.14 to make room for the push token and the Today file at §8.11 and §8.12, so every reference on the old page pointed at the wrong section. Eight more were renumbered by hand in
Wire,RoutesAnonymous,RoutesDiscovery,ContactLinkPageTestsandAnonymousReadsTests; the remaining 8.11 and 8.12 references are about push and the Today file and are correct.Verification
swift buildis clean on Swift 6.4 here.swift testcould not be run locally: the Swift frontend crashed withfatalErrorcompiling the test module, with only warnings printed, which is a macOS toolchain problem rather than a source one. Theswiftjob in CI compiles and runs the suite on Linux, and that is what should be read here.🤖 Generated with Claude Code
GET /today.json (§8.11) serves one public, signed file, the same bytes for everybody. It comes from FN_TODAY_FILE, read again when the file changes, or from FN_TODAY_SOURCE, fetched every 15 minutes give or take a minute, with a 10 second deadline over the whole answer and a 512 KB cap. Nothing is served until it verifies against a key in FN_TODAY_KEYS (kid = first eight hex characters of the key's SHA-256), and a file that fails the check never replaces the last one that passed. FN_TODAY_CACHE keeps that copy across a restart. 404 {"error":"not_offered"} with no source set, 503 while nothing has verified. A 200 is the bytes unchanged as application/json, public for 900 seconds, with the quoted SHA-256 of those bytes as the ETag, so every client gets the same one; If-None-Match gets a 304. The route reads no credential, cookie or query, writes no log line per request, and adds no table. Documented in docs/CONFIGURATION.md, docs/API.md and .env.example. The flamenet.io builder's dev-signed sample is a test fixture; the dev key's private half is not in the repository. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>