After a directory rename: scripts, history and Linux permissions
Why moving code into frontend/backend also requires checking build entry points, old working copies and the Maven wrapper executable bit.
6 min read
Engineering log · 31 October 2026
What changes when a project is ready to share?
Four notes from the latest directory migration, mobile adapter, upload queue and release verifier.
The connection between these changes
A path tells a script where to run. A token tells a response which session it belongs to. A generation tells an upload whether it still owns the page. A digest tells a release checker whether the files changed. These mechanisms answer different questions, but all require making an implicit assumption explicit.
A useful review question is: which assumption becomes false after an account switch, a directory move or a new build? It is easier to design a check after naming the specific failure.
Four notes from the code
Mobile API contracts: what to check after HTTP succeeds
Use HTML error pages, empty responses and stale-session 401s to examine the platform adapter and the limits of simulated tests.
6 min read
Photo upload queues: retries and account changes
Separate selected files from ready media, follow the four upload states and handle callbacks that arrive after ownership changes.
6 min read
Release integrity: do the delivered files match what was checked?
Follow VERSION, SHA256SUMS and ZIP contents to understand what version checks, file inventories and digests actually establish.
6 min read
Useful follow-up work
- Add runtime checks for important API payloads, measure preview memory on real devices, and verify the release process on the intended deployment host.
- Keep report dates and versions together. The new case distinguishes v1.2.1 business checks from the v1.2.2 file-mode repair.
Compiled from public sources with AI-assisted drafting and translation. The date marks this review; linked release records retain their original scope.