Changeblog

Performed a structural and methodological cleanup of the Darius studies. Finalized a three-page structure for the Darius material. Created a single disambiguation hub at darius.php. Separated the study into two profile pages for distinct historical figures. Completed a historical-context study for Darius, King of Persia. Treated this figure as an administrative and chronological authority. Integrated archaeological and scholarly background without apologetic framing. Established a prosopographical method for disambiguation decisions. Applied the rule of evidence first and identities later. Began the Darius the Mede page with a text-driven profile from Daniel alone. Postponed identification theories until chronology and narrative role are clear. Maintained strict scope control throughout the study. Prevented premature harmonization by enforcing methodological boundaries.

Separated site-wide search into two PHP pages with distinct responsibilities. Assigned full verse discovery to one page and reference-only lists to another. Removed multiple search modes from a single shared page. Eliminated state leakage and unpredictable behavior caused by mixed concerns. Defined a clear boundary between verse text search and reference construction. Made whole-word matching the default search behavior. Implemented whole-word matching using database word boundaries. Prevented unintended matches such as “Peter” matching “trumpeters.” Retained substring matching behind an explicit user-controlled checkbox. Preserved checkbox state across paginated results. Corrected schema mismatches caused by incorrect column references. Removed hard-coded LIKE queries that bypassed user intent. Fixed pagination links that dropped active search state. Generated pagination URLs from computed state rather than inherited parameters. Eliminated intermittent behavior caused by missing query flags. Ensured search pages post to themselves deterministically. Standardized search_full.php to return verse text with links. Standardized search_refs.php to return reference-only links for footnotes. Improved consistency and predictability across both search pages. Aligned search behavior with the project goal of maintainable, low-entropy code.

Implemented a database-backed contact system to replace obfuscated email addresses. Added a user-facing contact form with validation. Stored messages directly in the contact_messages table. Recorded sender IP address and user agent with each message. Added optional sender name and contact details. Created an admin inbox for reviewing contact messages. Displayed an unread message count in the admin inbox. Added filters for all, unread, and read messages. Enabled actions to mark messages read or unread. Enabled message deletion and admin notes. Integrated unread message counts into the admin dashboard. Displayed a “Read Messages” link when unread messages exist. Applied existing site styling without adding new colors or overrides. Used correct terminology for links and buttons. Provided a controlled contact method without relying on email delivery.

Added support for Psalm superscriptions by storing them as verse 0 entries. Preserved canonical verse numbering without renumbering inspired text. Separated superscriptions that had been incorrectly prepended to verse 1. Restored verse 1 to its original and complete form. Verified that Psalms without superscriptions match the historical count. Confirmed data consistency rather than data loss. Updated chapter.php to render superscriptions as italicized, unnumbered text. Preserved anchor stability and footnote compatibility. Added singular labeling for individual Psalm chapters. Improved textual precision by distinguishing “Psalm” from “Psalms.” Established a script-assisted CSV-to-SQL workflow for inserting verse 0 records. Inserted missing superscriptions without altering existing verse data.

Renamed the back-button class to back-tapper to correct misleading UI terminology. Aligned navigation language with actual HTML behavior. Reinforced the principle that words must reflect reality. Updated canonical CSS before deploying any dependent pages. Deployed corrected PHP pages incrementally to the live server. Used visible styling breakage to identify files still needing upload. Prioritized correctness and deployment certainty over speed.

Audited zerubbabel.php and chapter.php as canonical working examples. Used these pages as living references for DB-free and DB-connected patterns. Applied JavaScript cache-busting consistently across public pages. Corrected include paths for subdirectory files in admin and bios sections. Eliminated silent menu failures caused by incorrect include paths. Removed local h() definitions and centralized output escaping in helpers.php. Converted admin database pages to use db.php exclusively. Removed direct references to private database configuration files. Affirmed support for forward links and missing nodes. Relied on a navigable 404 page to handle missing content. Removed canon.php to eliminate competing sources of truth. Enforced canon through code examples and established practice.

Standardized verse-level navigation from bridge pages into the Scripture layer. Added a shared helper, vlink(), to generate verse links at render time. Removed the need to build fragment identifiers by hand. Preserved clear, verse-level intent without embedding link logic in page content. Refactored the Olive Tree bridge page to use inline verse links. Embedded links directly in the narrative instead of using reference lists. Kept Scripture centralized in the chapter view. Established a consistent, database-free pattern for all bridge pages. Bridge pages now reference verses cleanly and without tight coupling.

Addressed long-term project viability by formalizing internal documentation roles. Drafted replacements for project_briefing.txt and todo.txt. Separated project orientation and invariants from execution and task tracking. Defined the briefing document as onboarding for new chat sessions or collaborators. Recorded architectural rules, non-negotiables, and scope decisions in the briefing. Refocused todo.txt as an execution queue that changes frequently as work progresses. Removed explanatory material from todo.txt. Resolved confusion between system definition and next-step execution. Established a stable foundation for future maintenance or collaboration. Documented intent and constraints in text files rather than relying on memory. Improved readiness for incremental growth without architectural drift.

Performed a stylesheet cleanup and corrected mobile layout issues. Spent a full session auditing and simplifying styles.css. Removed legacy and unused CSS that had accumulated over time. Eliminated obsolete selectors, redundant rules, and unnecessary styling. Restored a predictable cascade and reduced overall complexity. Added targeted mobile adjustments using media queries. Corrected double-padding and cramped layouts on small screens. Ensured content cards align cleanly on mobile while preserving desktop layout. Updated the Changeblog page to use a dark background with light content cards. Improved visual consistency and readability across devices. Focused on subtraction, clarity, and long-term maintainability.

Created a Zechariah footnote and attached it to 43 verses using the Footnote to Verse Tool. Used preview and confirm steps to apply the attachments in bulk. Verified that footnote markers render and link correctly in chapter view. Confirmed the footnote appears in the chapter footer. Spot-checked behavior in Zechariah chapter 1. Scheduled cleanup of the Zechariah disambiguation page for the next work session.