This repository has been archived on 2026-11-14. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
Paul HittandClaude Opus 5 7abe9c0ab2 Remove Flamenet Files, and delete accounts outright
Files was folded into the messenger, so this repository is the account
service and nothing else. The file server, its web client, its tenant
schemas and the documentation for all of it are gone.

Removed: EnclaveServer and its routes, EnclaveAccess, EnclaveCrypto, the
browser client under client/, the Files spec and vectors, the tenant SQL
under sql/, the web build and the node CI job, and the Leaf dependency
that only ever rendered the file server's pages. The Dockerfile built
EnclaveServer and shipped Public/ and Resources/; it now builds the
account service alone.

Nothing was lost. Every table in the production Files database was empty
when this was written: no nodes, no blobs, no identities, no tenants.
flamenetfiles.com, www.flamenetfiles.com and files.flamenet.io were
served by that stack and now answer 404; the compose file, the env and a
schema dump are on the box under /srv/prod/backups/, and the two docker
volumes were kept rather than pruned.

The service now issues pseudonyms for one product. `050_retire_files.sql`
deletes the `files` rows and replaces the CHECK constraint rather than
dropping it, so a container still being drained cannot write one back.
Every account had a `files` pseudonym and none had a `files` identity,
which is why there is no key material to migrate: the row was bookkeeping
for a product nobody enrolled in.

That also settles the delete endpoint added on this branch. It was built
around keeping a shared account alive while another product still held an
identity, and with one product that rule can never fire. `AccountRemoval`
and its five tests are gone, the response no longer reports which of two
outcomes happened, and a delete simply removes the account. None of it
had shipped, so there is no wire compatibility to keep.

Verified: the suites pass, the live delete script passes against a real
Postgres and a running service, and the image builds and boots to its
"DATABASE_URL is required" refusal, which is the account service and not
a file server.

`flamenet/files/auth/v1` stays as the authentication context string. It
is a wire constant baked into every stored verifier, not a product name,
and changing it would lock out every existing account. Said so in
ARCHITECTURE.md so nobody tidies it later.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-21 17:30:55 -04:00

51 lines
2.3 KiB
YAML

# 🔴 **This repository had no CI at all until 2026-09-06.**
#
# Both open merge requests showed `pipeline: None` — not failed, not skipped,
# never run — because there was nothing to run them. Every merge into the
# service that holds people's files, and now signs their sessions, went in on
# somebody's word that the tests passed locally.
#
# ⚠️ Two suites, and they answer different questions. `swift test` proves the
# lattice, the SQL and the accounts kit.
# modules the browser actually runs. TESTING.md's table is worth reading before
# trusting either to mean more than it does — neither says whether a route or a
# button is wired to any of it. The integration scripts do, and they need a live
# stack, so they stay manual.
stages: [test]
server:
stage: test
image: swift:6.1-noble
rules:
- if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
- if: '$CI_COMMIT_BRANCH == "main"'
script:
- swift test 2>&1 | tee swift-test.log
- |
# 🔴 **awk, not python3 — `swift:6.1-noble` HAS NO PYTHON.** The first
# version of this gate was written in python, the suite passed, and the
# job died `python3: command not found` after a twelve-minute build. That
# image also has no curl, xxd or jq; it is a documented trap in this
# account and this is the fourth time it has been walked into.
#
# 🔴 **Assert on the LOG and on a COUNT, not on the exit status.** This
# package builds three test bundles, so a target that silently stopped
# being built would take its tests with it while the rest still reported
# a clean run. Verified against real Linux output — the two platforms
# format the run differently, and a gate checked only on a Mac can read
# zero on the machine it actually runs on.
awk '
/\.xctest.*passed/ { pending = 1; next }
pending && match($0, /Executed [0-9]+ tests/) {
n = substr($0, RSTART + 9, RLENGTH - 15); total += n + 0; pending = 0
}
match($0, /with [0-9]+ failure/) {
f = substr($0, RSTART + 5, RLENGTH - 13); fails += f + 0
}
END {
printf "GATE: %d server tests executed, %d failures\n", total, fails
if (total < 68) { print "GATE: too few tests ran; a target is missing"; exit 1 }
exit (fails > 0)
}' swift-test.log
timeout: 30m