Home

October 21 update — build prerequisite resolved: #69 is fixed through merged source PR #70 and staging-controller PR #1. Declared Ruby 3.3.9 and frozen dependencies preserve patched ZIP. Exact-source staging, source CI and native production Pages pass; production is 2f7bb8a13e7f36678014d533b70ed19a4f6c54cc. John delegated technical review/merge while retaining branches, PRs, checks and rollback.

Browser-exclusion PR #67 includes the prerequisite. Candidate e7200fc passed frozen CI and live staging controls/persistence/consent/keyboard checks in 39679279467. No feature release or private Worker deployment is claimed. Saved staging 4fd49e45ea77bd59ed82ebb6b539e705a9b6c4de was restored and verified in 39679563070. Worker coordination and full network/narrow/device acceptance remain. #68 retains its 6–10 hour estimate. Current release notes. Earlier blocker records below are history.

johnapaz.com development wiki

This wiki records the requirements, decisions, development history, and operating context for johnapaz.com. It supports contributors, AI sessions, and future writing about how the site was built.

V2 launched — October 2, 2026

V2 is live on johnapaz.com from the renamed main branch. V2 launch records content, source and deployment evidence, staging/CI checks, recovery, and remaining work. Earlier production holds are superseded by John’s explicit launch authorization.

Admin and next release — October 21, 2026

The initial owner dashboard shipped October 14 (#62): protected sign-in, separate live production/staging analytics, and Operational health/build-revision widgets were verified. John reports it is working. Broader acceptance stays in #31.

PR #67 implements browser analytics exclusion (#66) on feat/66-exclude-own-traffic, with an untracked preferences page, Undo and separate consent handling. This is in review, not a release. Historical visits remain in reports. Release notes and version convention records proposed v2.0.1 — Cleaner analytics, preserving v2.1.0 — Mentoring.

A protected staging deployment of the admin code/backend is tracked in #68, estimated at 6–10 engineering hours (typically 1–2 working days once access is ready). The live dashboard already reports staging data; independent admin deployment is the gap.

Start here

Page	What it contains
Roadmap	Phases, timeline, dependencies, and completion criteria
V2 requirements	Current product and design requirements, exact approved copy, and open questions
Decision log	Decisions, rationale, alternatives, and superseded choices
Architecture and configuration	Verified implementation facts and configuration references
Development workflow	Contributor and AI session protocol, staging, review, and release
Development journal	Dated outcomes, experiments, evidence, and session handoffs

Live issue backlog · Source repository

How to use this record

Issues track actionable work and its live status. The wiki records context and rationale. Source files hold executable configuration. Link between them rather than maintaining competing copies of task lists or settings.

Read the relevant pages and linked issues at the start of a session. Preserve exact approved copy and distinguish proposed, accepted, and superseded decisions. Check actual source and service settings before treating configuration notes as current. Record material outcomes and the next step before ending a session.

The wiki is public: record configuration locations and ownership without credentials or private session transcripts.