Changelog
A reverse-chronological record of every shipped change that touches
business-logic code or user-facing behaviour. Each entry is its own page —
authored by the developer (with the docs-update skill’s
help) and reviewed in the same PR as the code change.
Entries live under docs/app/changelog/entries/
as one file each, so two branches adding entries never touch the same file.
See the docs-automation spec
for how entries are maintained, and the covers: / owns: convention
for how /business-logic/ pages declare which code they document.
Rusty no longer mentions the Member Directory to members who can't use it, and answers sign-in and skill sign-off questions.
TUN-960PR #1058Three checks the Monday review agent can't run itself, because it has no database access.
TUN-961PR #1060Tools › Weekly Review now has tabs by topic with plain names, email and SMS side by side, per-app request and error figures, website and app traffic, and an Ask Rusty tab. Admin's server errors now reach Datadog with a level.
TUN-959PR #1056The weekly review email now leads with what to look at and shows each figure as this week against last, and it no longer flags jobs that didn't exist for the whole week.
TUN-954PR #1052The weekly review now flags a connector's real errors only. Wrong PINs, which are members mistyping at check-in, get their own unflagged row.
TUN-954PR #1053The Monday email is now a short summary written by Claude with six headline figures and a link to a new admin page that holds every figure. Errors and the mobile app are now covered, and refused emails are counted properly.
TUN-921PR #1055A Monday email on last week's platform health — services, connectors, analytics tracking and business pulse — compared with the week before. Accordion rejections are now stored per reason.
TUN-954The admin dashboard's analytics now read the unified web, iOS and Android GA4 property, 528361126, instead of the GA_PROPERTY_ID env var, which pointed at an old property locally.
TUN-958Real member details and credentials are gone from api/bruno and the docs generated from it. A new CI check keeps them out, and an unused admin file listing 399 members is deleted.
TUN-945member_deleted is now member_deletion_log, with a reason for each delete. members_inactivated is now member_currency_deactivation_log.
TUN-862Tunnels gain owner (corporate, franchisee, third party) and POS (Convergence, FuseMetrix, Tunn3l, unknown), filled from ops' list of iFLY network tunnels. The admin tunnel form can set both, and now its time zone too.
TUN-942The weekly level advancements email now lists only members whose home tunnel is one of 31 US iFLY tunnels, and says which. The admin report still shows every tunnel, now paginated, and a new index on logbook approval dates makes it about 100 times faster.
TUN-914The level advancements report is emailed every Monday at midnight PST, with the results in the body and as a CSV. Recipients are managed in admin under Tools › Scheduled Emails. The same mechanism can send any other report weekly or monthly.
TUN-940Reports › Members › Level Advancements lists instructors and trainers who completed a full level in a date range, with their home tunnel. It defaults to last Monday–Sunday in Pacific time. Report tabs can now be linked to with ?tab=.
TUN-939www now logs like the API: one JSON line per event with a real level, a request log line per request, and errors that keep their stack. Unknown pages answer 404 instead of 200.
TUN-919About 270 API error paths now leave through one helper that logs http.server_error and answers a generic 500, passing the error on to the existing Sentry, Jira and email handling.
TUN-918The name typed into a member directory search, and the sender's name on the directory contact form, are now masked in the request log; push.no_tokens moves to debug.
TUN-917A connector batch refused because its signature did not match now logs connector.signature_rejected and posts to #iba-alerts, after Accordion batches with accented names were found to have been refused silently since go-live.
TUN-915A flyer currency reminder that failed to send on our side is now retried rather than recorded as sent; a failed password reset is reported as itself; Ask Rusty questions and positional SQL values are kept out of logs; Accordion rejections are logged.
TUN-908PR #1019The Accordion connector accepts an optional Instructors array of IBA numbers on each booking and stores it, so the auditing team can later find an instructor's flights and review the video.
TUN-904The per-request log line now has event http.request and a message like POST /api/auth/login 200, and is kept under 15,000 characters so Docker never splits it into unparsed fragments.
TUN-903PR #1016Fourteen Datadog monitors that post to #iba-alerts, a stripe_webhook.processed line for the Stripe silence check, and a fix for log fields named status, which Datadog was reading as the log level.
TUN-903PR #1018Nothing a scheduled job logged ever reached Datadog. Job log lines are now forwarded, each failed health check logs health.check_failed, and a new check fails when no Accordion booking has been stored for 26 hours.
TUN-903PR #1015Accordion batches containing an accented name were refused as unsigned because we checked the signature against our own re-encoding of the body. Signatures are now checked against the raw bytes, and a body that isn't valid JSON gets a JSON 400 and a warn log instead of an HTML page and a stray stack trace.
TUN-903PR #1017Request logs, error reports and connector history were storing passcodes, security answers and member PINs in plain text, plus member emails, names and messages, the logger was dropping error details, and several failures logged nothing. Secrets are now redacted everywhere, personal data is masked or redacted in logs, every log call is one JSON line with the full error, and SMS, Redis, password-reset and currency-cron failures are logged.
TUN-903PR #1013The payment webhook accepted any request, so a forged payment could activate a membership, and failures were silently dropped. Stripe events now need a valid signature, each payment is applied once, and failures return 500 so Stripe retries.
TUN-902Sign-up and the profile email/phone change always replied 'code sent', even when the email failed, and a code sent to one address could verify another. Both flows now share one verification service that reports failures honestly and binds each code to its address.
TUN-901The unauthenticated sign-up verification endpoints acted on any member named in the request, and verification codes doubled as login codes. Both are fixed; passcodes are now scoped by purpose.
TUN-900A failed passcode email always said the member's provider rejected it, including during our own outage. Failures now say whose fault they were, and only auth flows unlock the fallback options.
TUN-898Production ran Node 20.11.1, end-of-life since April 2026 and behind its own dependencies. admin, assistant, www and api now run Node 22, rolled out one app at a time.
TUN-897PR #98439 dynamic imports used import assertions, which Node 22 removed. The shared lang middleware was one of them, so every API request would have returned 500 after the upgrade.
TUN-897PR #983Six JSON imports in the email and passcode services still used import assertions. On Node 22 every email the API sent failed, including login passcodes and booking confirmations.
TUN-897PR #987Ask Rusty can now search the text of every reference document and flight tutorial in English, Spanish and French, and links the page its answer came from. It also knows the flyer currency rules.
TUN-854PR #961About 4% of questions got a blank reply after the assistant spent its tool calls hunting for skill ids. It now gets the ids up front, always writes a final answer, and logs any empty answer as a failure.
TUN-880PR #950An over-long member number made the contact form's insert fail, and the email to IBA was never sent. The form now validates, cleans up the member number, and sends the email even if saving fails.
TNBUGS-1862PR #951getRedisValue opened with a bare return null, so every cache read across the app returned null since 29 August. Writes kept working, which is why nothing alerted.
TUN-876PR #942GitHub ran the daily jobs 4-6 hours late every day and dropped three quarters of the hourly slots. A Cloudflare Worker takes over the timer, and op_cron_logs finally records what each run actually changed.
TUN-874PR #941Accordion's daily batch of completed flights by IBA members at US iFLY tunnels is now received, validated and stored.
TUN-856PR #929npm run lint in api/ had never worked — eslint was undeclared, so npx fetched a version the pinned Node cannot run. Behind it sat 57 errors, two of them real.
TUN-875PR #940Answers are stored hashed, so the editor shows every box blank. The writer read a blank as 'remove this', so a member who changed one answer lost the two they had left alone.
TUN-873PR #938A failed 2FA response only said what to do next when the email bounced, and 'has security questions' meant 'has a row' — so members were shown a door that would not open. Both are closed, and the fallback is now instrumented.
TUN-873PR #937A member with no verified phone whose passcode email bounces was stuck with 'contact support'. They can now answer their security questions to sign in directly — no password reset — but only in a short window after a real bounce.
TUN-870The login screen used to say a code had been sent to a named address while it bounced. It now reports the failure, explains the likely cause, and offers SMS where the member has a verified phone.
TUN-867PR #932Twelve logger.info and logger.warn calls recorded fields that never arrived — the event turned up with its label and nothing else. A winston detail split each one across two lines.
TUN-868PR #933The presence probe proved the signature header survives the proxy — 6,291 calls, no misses. What it could not prove is that our copy of the URL reproduces Mandrill's digest, so the webhook now computes and compares one, and acts on nothing.
TUN-859PR #931app.locals held its boot-time copy of the faqs, skills, news and tunnels keys for the life of the process, so CMS saves rebuilt Redis and the site did not change. It now re-reads once a copy ages out.
TUN-855The last v1 caller migrated to POST /get-member, so the legacy endpoint and its parallel controller/service/repository/model stack are gone. The old per-vendor tables are dropped in a follow-up deploy.
TUN-793PR #905A wall-clock gate that the droplet's crontab satisfied but GitHub's scheduler never does left one check skipped for two weeks. Alerting moves to Slack, skips now expire, and op_health_checks gets a retention sweep.
TUN-845PR #903The OpenAI Assistants API shuts down on 26 August. Ask Rusty now runs on Claude Sonnet 5, answers from live database content instead of a hardcoded PDF list, and gates every source through a single access resolver.
TUN-788PR #901Tunn3l joins FuseMetrix and Convergence as a booking-system integration, and the per-vendor connector tables are consolidated into one set discriminated by a vendor column.
TUN-661PR #744executeQuery now retries deadlocked statements up to 3 times with backoff, so concurrent approve-manually requests no longer surface a 500.
TUN-817PR #868Removed the transitional dual-tag so the website tags only the unified GA4 property, retiring the legacy property and GTM container.
TUN-801Server-side GA4 purchase events now capture the real GA client_id/session_id client-side so purchases join the member's web session.
PR #765The 2FA passcode SMS appends an Apple domain-bound code line so iOS autofill pins to the exact current passcode instead of a stale one.
TNBUGS-1732The /book page now reports the member's Convergence discount tier to GA4, so app-driven bookings can be measured by tier.
TUN-798PR #753role_id 11 and 12 are now always required to enable 2FA, independent of instructor currency — previously they were never prompted.
PR #686Removed a dead dialing-code lookup so the 2FA SMS recipient number is built directly from the stored members.country value.
TNBUGS-1729PR #664Fixes a concurrency race that left members without an earned parent skill, via serialised locking, sequential UIs, and a reconciliation cron.
TNBUGS-1728PR #648The API now applies schema/data changes through a tracked, forward-only migration runner with CI and deploy-time guardrails.
PR #650Tooling that keeps business-logic docs in sync with code — the docs-update skill, a frontmatter convention, and deterministic drift safety nets.