Archived
Everything between the engine and an app: server discovery, the account service, the file API, and a session that ties them together. Recovery codes and share links move into the engine, and both agree with the browser character for character — the vectors file now carries codes generated by the JavaScript implementation, including one containing a Q, because folding Q is the mistake that once corrupted a third of all codes. `filesctl` exists so the cryptography can be exercised without an app, a simulator, or a person tapping. `smoke` registers, signs in fresh so the stored record has to actually open, uploads across four chunks, reads the name back, compares bytes, and checks a password-protected link is refused without its password. Verified against the Android engine as well: one uploads, the other downloads, and the digests match. Registration now sends the identity with the account rather than after it, and a session with no identity for this product enrols one instead of refusing — which is what an account created before Files existed needs. MIT, matching the server. CI runs the suite on a Linux Swift image, which is the point of keeping the crypto in a package rather than in app code.