# Development log — Queue North Website ``` Status: Current Owner: _null Last reviewed: 2026-08-18 Governs: the dated record of what happened Review trigger: Nothing. This file is appended to, never revised. ``` ## How to use this Newest first. **One entry per work session**, written before you stop — that is step 6 of `docs/WORK_CYCLE.md`, and the two lines it insists on are `Next action` and `Blockers`. Those two are not decoration. The next session starts by reading the top of this file, and a session that ended without saying what came next hands the one after it a re-derivation instead of a starting point — which is where drift enters. Neither line competes with anything: the live next action is the field on the project at privacyllc.dev and the live blockers are issues in the tracker, while these say what both were **at this date**. A record of then never disagrees with a record of now. **Append-only by convention.** Correcting an old entry rewrites the record of what was known at the time, which is the one thing this file is for. If an entry turns out to be wrong, add a later entry saying so; do not edit the first. Note the Review trigger above says "nothing", deliberately. A dated log cannot rot the way a description of current state can — the entries were true when written and stay true. It is exempt from review for the same reason a receipt is. ## Where the entries below came from Everything from `v0.7.1` down predates this repository adopting the template, and arrived from two root-level files that were merged here on 2026-08-18 — the gitignored `HISTORY.md` (a version-by-version changelog) and the gitignored `DEVELOPMENT_LOG.md` (an agent-activity log). Both are reproduced **verbatim**. They are kept as two blocks rather than interleaved by date, deliberately. The changelog carries three duplicated version headings — two `v0.5.2`, two `v0.5.3` and two `v0.5.4`, written by different agents on the same day — so merging the two streams into one date order would have required choosing an order the record does not actually support. Two labelled blocks say what is known; one merged sequence would have implied more. ## Entries ### 2026-08-18 — queuenorth.com confirmed as the permanent origin, and a wrong runbook claim corrected `_null` answered the one question left open by the adoption: **queuenorth.com is the permanent public origin**, with `qn.isnull.dev` kept as a second ingress. **The answer exposed a mistake made earlier the same day.** The first draft of `docs/OPERATIONS.md` said queuenorth.com "is not this deployment — it is the customer's own domain and is not served by this container. Do not diagnose against it." That was written from a DNS lookup and an assumption, and it was wrong in the worst direction a runbook can be wrong: it sent whoever read it away from the production host during an incident. What is actually true, established by request rather than inference: both hostnames serve the identical bundle and this server's own `/api/health` shape; `24.41.108.95` is this network's own public IP; `queuenorth.com` reaches the container through nginx-proxy-manager on thor/exodus and `qn.isnull.dev` reaches it through Cloudflare. **Two front doors, one container, and no non-production environment** — restarting it restarts the customer's live site whatever the `-dev` in its name suggests. The correction is written into `OPERATIONS.md` as a correction, with the wrong sentence quoted, rather than silently replaced. Same for the QA Round 0 table, which gained the production observations as extra rows instead of having its originals rewritten. **The deploy path is no longer a gap.** Adoption left it explicitly undone — "how nebula moves to a new image is not written down anywhere". It is a **Portainer stack, id 58 on nebula**, file at `/data/compose/58/docker-compose.yml`, found by reading the container's own compose labels. `OPERATIONS.md` now carries it, including the sentence that matters most: that stack file is a separate copy from this repository's `docker-compose.yml` and the two have already drifted. That drift is #212 and it is exactly one character — line 21 of the stack file has `CORS_ORIGIN=https://queuenorth.com/` with a trailing slash. Left in place deliberately: nothing is broken today (the forms are same-origin, and the slash makes the header match no origin, so it fails closed), and fixing it means recreating the container and taking both front doors down together. It belongs in the next deploy that happens for another reason. `scripts/deploy.py` was declined at adoption because none of this was known. It is built for exactly this shape and is worth taking next time. - **Closed:** none. #212 stays open — the repository half is done and the production half is one line in Portainer. - **Next action:** Unchanged — start `Batch 10 — Accessibility WCAG 2.1 AA` with #189, walking the pages keyboard-only at 320px before fixing anything. Fold the #212 one-character fix into whatever deploy happens next rather than restarting production for it. - **Blockers:** None on this work. Six issues remain blocked on the site owner (#68, #110, #162, #213 in Batch 13; #69, #70 in Batch 14), two of which are unsubstantiated claims live on the public site since May. ### 2026-08-18 — Adopted the project template Merged `~/.openclaw/Projects/Template` into this repository. It was the worked example in that template's own README — *"every one of the 205 in the repository that had never adopted the convention"* — and the numbers matched exactly: 205 issues, zero milestones, severity labels spelled `P0 Critical` / `P1 High` / `P2 Medium`, and privacyllc.dev reporting the project as **not adopted** rather than as 87% complete. **The repository was made private first.** Six documents were gitignored with the comment *"never commit"*, and committing them into a public tree was not the same decision as committing them at all. `null/fruit-fall` is already private and reports normally, so nothing was lost by it. That is what made `Exempt:` lines unnecessary — this project exempts nothing. **What moved.** `FUTURE.md` was the markdown backlog and is gone; every open item in it was already an issue, so nothing needed migrating into the tracker and only its reasoning survives, in `BATCH_LEDGER.md`. `HISTORY.md` and the old `DEVELOPMENT_LOG.md` are the two blocks below this one, verbatim, zero lines lost. `PROJECT.md`, `STRUCTURE.md`, `BUILD_SUMMARY.md` and `SCRIPTS.md` were absorbed and deleted. Four tracked documents moved into `docs/` as git renames. **What was kept because this project earned it:** the five-agent pipeline, the design system in `OVERHAUL_PLAN.md`, the positioning argument in `REDESIGN_REVIEW.md`, and `REQUIREMENTS.md` whole including its change policy. **What was deleted from the template because it does not apply here:** QA pass I (no money moves), the authorisation checklist group and the session-token row (no accounts, no sessions anywhere in the product), and one *(precautionary)* paragraph in `SECURITY.md` about holding credentials on behalf of users. That last one is a precautionary rule dropped deliberately and it is named in `DOC_TRUST_MAP.md` so nobody has to guess whether it was an oversight. **Ten scripts, configured rather than copied.** `backup.sh`'s ENGINE block was rewritten for SQLite and `restore-check.sh` was rewritten outright — the template's is `pg_restore` and `psql` end to end with no seam to configure. Three guards in `scripts/verify.d/`, because `verify.sh` detects nothing in a project with no test runner and would otherwise exit 2. **Every guard was proven to fail before being trusted**, per `GUARDS.md` §1. The one worth naming: `secrets.sh` was pointed at the real historical leak replayed out of commit `033bdf6`, and caught all three Zoho tokens. **What it proved.** Two things that were not known this morning: 1. **The lead database is restorable.** `backup.sh` took a verified snapshot from the running container and `restore-check.sh` replayed it from SQL into a scratch database — 2 tables, 3 rows, under a second. Before today nothing had ever backed it up and nothing had ever restored it. 2. **Three defects, found by the tooling on the way in.** `zoho-setup.md` told admins to edit `server/zoho/`, a directory that has never existed in any commit; `README.md`'s route list still advertised `/8x8`, removed at `0.6.6`, and omitted `/privacy-policy`; and `check-env.sh` found `CORS_ORIGIN` naming a host the site is not served from, with a trailing slash, drifted from what `docker-compose.yml` commits. The first two were fixed in the same commit. The third is filed, because choosing the right origin is not mine to decide. **Four issues filed and no more.** Every open issue is a denominator. A test suite was deliberately *not* filed for — nobody has decided to build one, and inventing that work would make every percentage wrong in one direction. It is recorded as a standing gap in `ClaudeQACoverage.md` instead. - **Closed:** none. Nothing was finished today that was open before it; the work was structural. The 178 already-closed issues were assigned to `Batch 00 — Pre-convention history`, which was then closed as the batch that shipped. - **Next action:** Start `Batch 10 — Accessibility WCAG 2.1 AA`, with #189 (missing focus rings on all link elements) first — it is the widest of the six and the only one that affects every page. All six were found by reading markup rather than by testing, so begin by walking the home, services and contact pages keyboard-only at 320px and confirm the six are the whole list before fixing any of them. - **Blockers:** None blocking this work. Five issues are blocked on the site owner and cannot move without them — #68, #110, #162 and #213 in `Batch 13`, and #69 and #70 in `Batch 14`. Two of those, #108 and #110, are live claims on the site the business may not be able to substantiate, which is a credibility exposure rather than an engineering one and has been open since May. --- ## From `HISTORY.md` — the version changelog, verbatim > Migrated 2026-08-18. Newest first, as written. Not edited. ## v0.7.1 — Low-Priority Fixes (6 issues, batches 10.0–10.2) — 2026-05-18 ### Batch 10.0: Backend Cleanup (Neo) - **#128:** Removed React Query dependency (~45KB bundle savings) — replaced with simple async fetch - **#127:** Added HTTP→HTTPS redirect middleware for production (x-forwarded-proto) - **#129:** Added CSP connectSrc comment documenting Zoho server-to-server calls ### Batch 10.1: Image Optimization & UX (Scarlett) - **#97:** Converted 5 large PNGs to WebP (95-96% size reduction each, total ~11MB → ~511KB) - **#130:** Added loading spinner animation to Contact and Support form submit buttons ### Batch 10.2: Accessibility (Scarlett + Ripley) - **#101:** Added aria-labels to interactive elements across Header, Footer, MobileNav, Home, Contact, Support - Fixed JSX template literal syntax bug where aria-label and className both used `${}` on same element - Fixed Footer.jsx template literal aria-labels that would render as literal text - Fixed Home.jsx duplicated aria-label text fragment ## v0.7.0 — Audit Bug Fixes (44 issues, batches 9.0–9.9) — 2026-05-18 ### Batch 9.0: Backend Security (Neo) - **#120:** Added UNIQUE constraint on leads.email + migration script - **#121:** Fixed Docker healthcheck — process.exit(1) on DB failure instead of always returning 200 - **#123:** Removed world-writable chmodSync on SQLite DB file ### Batch 9.1: UI Fixes (Scarlett) - **#104:** Header CTA visibility — changed from invisible navy-on-navy to cyan-on-navy - **#89:** Added ScrollToTop component for route navigation - **#88:** Created 404 NotFound page with catch-all route ### Batch 9.2: UI Fixes (Scarlett) - **#91:** 8x8 white logo visibility on Trust Bar — added `brightness-0 invert` CSS filter - **#94:** Industries page now uses dynamic icons instead of hardcoded building SVG - **#125:** Added Building2 fallback for missing industry icons - **#92:** Industry cards use homeDesc with fallback text - **#93:** Removed redundant shortDesc from Home page service cards ### Batch 9.3: Navigation Fixes (Scarlett) - **#109:** Desktop nav now has hover dropdown menus for Services and Industries - **#102:** Replaced all `