This is a changelog page¹.

WCAG 2.5.3 (Label in Name): a control's accessible name must contain its
visible text, or a voice-control user who says what they see ("click
Changelog") gets nothing. Lighthouse flagged the sidebar on every page
and the homepage music link; a scan of the built site found the same
pattern elsewhere.

• Sidebar nav links: drop the descriptive aria-labels ("Project release

history and recent changes" for "Changelog") so the visible name is
the accessible name. The collapsed sidebar hides the text with
max-width/opacity, so it stays in the accessibility tree. The
ariaLabel navigation field is now unused and removed.

• Terminal trigger: the decorative prompt chrome (user@host, box

drawing, visit counter) is aria-hidden and the "Open terminal" label
is dropped; the name is the visible greeting plus "open terminal".

• Homepage "chip musician", the success page guestbook link and two

in-post links: drop the mismatched aria-labels.

• Project cards: "view source of <repo> on GitHub".


• Terminal dock chip: "restore signal: reopen the terminal".


• Music theme button: the label starts with the visible flavor and is

updated whenever the flavor changes.

fetchJson passed payload.error straight to new Error(). The music API
returns a string there, but error bodies from anything in front of it
(a static server, a proxy, a platform error page) can carry an object,
and the playlists panel then read "[object Object]".

Use the existing text() helper so only a non-empty string message is
shown, falling back to "Request failed: <status>".

Verified in the browser: with the API unavailable, the panel now reads
"Request failed: 404".

The music player boots on every page load, closed. Its ASCII visualizer
mount appended 12 rows of 32 spans straight into the live page and then
started the idle animation, which the caller stopped again on the next
line because the player was hidden. Under Lighthouse's 4x CPU throttle
the mount cost ~360 ms on every page, most of it style invalidation
from the live appends.

• Build the grid in a DocumentFragment and insert it once.


• mount() starts whichever loop the current visibility calls for, and

the player sets visibility before mounting, so a closed player starts
no loop at all.

Mount now costs ~2 ms at 4x throttle. Opening the player still renders
the 12x32 grid and animates. New jsdom tests cover the single
insertion, no loop while hidden, the idle loop when visible, and the
reduced-motion static frame; the first two fail on the old code.

Lighthouse named the post hero (PreviewImage) as the LCP element on blog
posts and the guestbook, yet it was loading="lazy": the browser holds
lazy images back until layout, so the page's main image started late. It
also always served the 1254px original (296 KiB) into a box at most
816px wide, 372px on a phone.

• PreviewImage is always the first thing under the title, so it loads

eagerly with fetchpriority="high" and a 480/816/1632w srcset sized to
its 816px maximum (a phone now takes the 54 KiB 480w file).

• ContentCard takes a priority prop; the blog index and tag pages set it

on their first card, which is above the fold on mobile. Other cards
stay lazy. Card images get a 288/480/960w srcset for their 144px
desktop / full-width mobile size.

The service worker precached every built png/jpg/webp/html file: 440
entries, 98.7 MiB, downloaded in the background on a visitor's first
page view. 74 MiB were Astro's original full-size images, which no page
references (pages use the optimized webp; the originals exist for the
SSR image endpoint), 16 MiB were the manifest install screenshots, and
14 MiB were every HTML page including all tag pages. On mobile that is
real data cost, and it kept the network busy long after load (TTI).

• Precache the app shell only: bundled JS/CSS, the web fonts, favicons,

and the home, about, hello, now and offline pages. 63 entries, 1.8 MiB.

• Every other page is cached network-first as it is read, so visited

pages work offline and unvisited ones show the offline page. Only
plain 200s are stored, so redirects are never replayed from the cache.

• Admin, guestbook and search navigations stay network-only, never

cached.

• Images keep their existing runtime caches.


• The icomoon stylesheet is now runtime-cached with the fonts; offline

pages previously lost every icon because it was never cached.

• The /api/ rule was a regex tested against the full URL, so it never

matched; it now matches on the pathname.

Verified in Chrome against the built site: 62 precached entries on
install; /blog/ and /colophon/ cached once visited (not the /colophon
redirect itself); offline, visited and precached pages render with
fonts and icons, an unvisited page shows the offline page, and no
console errors.

0xProto ships as the Nerd Font Mono build: 11,161 code points, 10,396 of
them Nerd Font icons in the Private Use Areas, which made each weight
~1 MB as woff2. All three weights were preloaded at high priority, so
on Lighthouse's throttled mobile profile the page text swapped fonts
only after ~3 MB arrived: LCP 17.9 s on the homepage (95% "render
delay"), and the re-layout with an 11k-glyph font was the 1.3 s long
task behind most of the TBT. The site renders no Nerd Font icons.

• scripts/subset-fonts.mjs (npm run fonts:subset) splits each weight

into the text glyphs (50-58 KiB, all GSUB/GPOS features kept) and one
icons file (884 KiB). The icons @font-face declares the PUA
unicode-range, so a browser only fetches it for a page that renders an
icon glyph; nothing is lost.

• The full TTFs move to src/assets/fonts/0xProto (not served); the

Open Graph renderer reads them from there. The ttf fallbacks are
dropped from @font-face: every supported browser takes woff2.

• Italic is no longer preloaded.


• The OFL license is kept beside the served subsets, as the license

requires for modified versions.

• The service worker no longer precaches legacy ttf/eot/svg font files

or the icons file.

Verified: glyph coverage of each subset equals the source minus the
PUA (0 missing), the icons file holds exactly the 10,396 PUA glyphs,
OG images build, and the homepage renders 0xProto from the ~51 KiB
files with the icons file never requested.

Admin sessions are HMAC-signed cookies; Argon2 verifies the raw token
only at login. Logout used to delete the cookie in that one browser, so
a copied cookie stayed valid for up to 7 days and the only way to kill
it was rotating ADMIN_TOKEN_HASH (review item P1-11).

A single-row AdminSession table (migration 0003) holds a generation
number. Session cookies (now v2) are signed with the generation current
at login and are accepted only while it is unchanged. Logout increments
it, which revokes every outstanding session at once: with one moderator,
single log-out is sign-out-everywhere.

• Format, expiry and signature are checked before any I/O, so forged or

expired cookies never reach the database; a genuine one costs one
small read.

• The cookie signing key is derived from ADMIN_TOKEN_HASH with HKDF

instead of using the hash itself as the key. Rotating the hash still
revokes everything.

• Fails closed: if the generation cannot be read the request is not

authenticated and login reports "Could not start a session".

• Only a genuine session may revoke, so an anonymous logout POST (Origin

headers are spoofable outside a browser) cannot sign the moderator
out. A genuine session whose generation read failed still tries, and
a failed revocation is reported instead of shown as a clean logout.

• v1 cookies are rejected: one fresh login after deploy.

Deploy order: apply migration 0003 (npm run db:setup) before this code
goes live, or admin login fails closed until it is applied.

Verified: unit tests for every cookie edge case and the check order, a
real-libsql test for revoke/re-login/missing row, and an end-to-end run
on the isolated dev server: two browsers signed in, logout in one
signed out both, the copied cookie was rejected, an anonymous logout
POST revoked nothing, and logging in again worked.

The footnotes section sits after the site footer, outside the article,
so the prose wrap rule never reached it. A long unbroken URL in a
footnote (creativecommons.org/compatiblelicenses on the licensing note)
pushed the page 32px wider than a 390px screen.

The footnotes section now uses overflow-wrap: anywhere, which also
shrinks the min-content width of inline-block links. Footnote links
(not the back-references) flow inline so a wrapped URL keeps its
trailing punctuation on the same line, with box-decoration-break: clone
so the hover highlight covers each wrapped line.

Verified on the built site: all 20 footnote pages at 320, 390, 768 and
1300px have no element past the footnotes column and no horizontal
page overflow. Placement after the footer is unchanged.

This reverts commit 83fc50b4599646f8fc7867167ea0e6e7d20e98ce.

GFM footnotes are appended to the end of the MDX document. The posts
wrap their content in <ContentLayout>, so the footnotes section landed
after the layout as a direct child of <body>: below the site footer and
commit line, outside the article and its prose styles. Global CSS had
compensated with a sidebar offset, a max width and 12vh of bottom
padding. All 20 pages with footnotes were affected.

A rehype plugin (rehypeFootnotesIntoLayout) moves the footnotes section
to the end of the root-level layout element, so it renders at the end
of the post body. The footnote CSS drops the offset workaround and keeps
plain in-article spacing.

Links in prose are inline-block, which sizes to the unbroken word, so a
long URL (creativecommons.org/compatiblelicenses) ran past the column;
they now use overflow-wrap: anywhere.

Verified on the built site: all 20 pages have their footnotes inside
the article, before the footer, aligned with the post body at 390px and
1300px, and the licensing note's long link wraps without overflow.

Haunted creatures fly up to 200px out of their container. Absolutely
positioned, transformed boxes still count toward the scrollable
overflow of the page, so hovering a guestbook card near an edge grew
the document (at 390px wide the page went from 382px to 577px wide; on
desktop the last card lengthened it by 147px) and scrollbars flickered
in for the length of the flight.

The content column (.sidebar-content-offset) is now overflow: clip.
Creatures still drift out of their card across the page background and
are clipped only at the column's edges (viewport edge, sidebar, page
bottom). clip is not a scroll container, so position: sticky children
(header, floating TOC) keep working, and fixed overlays (search,
terminal, music player) are not clipped.

A crawl of every built page at 390px and 1300px found two elements that
overflowed the page and would now be clipped instead; both are fixed
here rather than hidden:

• palette view tabs overflowed by 4px at 390px: px-3 below sm


• long unbroken words or URLs in prose wrap (overflow-wrap: break-word

on article paragraphs and list items)

Verified in Chrome: no document growth with creatures in flight at
390px (first card) and 1300px (first and last card), creatures still
visible beyond the card, sticky TOC unchanged, and the crawl reports no
clipped content.

The palette views switch with CSS-only radios, with each label marked
role=tab. Keyboard users met four stops for one control (the checked
radio and all three labels), no tab exposed aria-selected, and the
panels were labelled by the unlabelled radios (P13-7).

New paletteTabs.ts upgrades the labels to real tabs: aria-selected and
a roving tabindex mirrored from the checked radio, Arrow keys (wrapping),
Home and End, Enter/Space. The radios still drive the CSS but leave the
Tab order and the a11y tree, and focus that lands on one (a label click
focuses it) moves to its tab. Selection syncs on the radio's change
event, since a label click checks the radio only after click listeners
run. Panels are labelled by the tabs. Without JavaScript the radios
remain the working control, so tab state is set by the script only.

The Enter/Space handler moves out of paletteCopy.ts.

Tests cover the initial state, arrows/Home/End, a label click and the
focus redirect. Verified in Chrome.

The search dialog is aria-modal, but closed it was only faded out
(opacity-0, pointer-events-none): its input and buttons stayed in the
Tab order and the accessibility tree, so keyboard users tabbed into an
invisible search. Open, Tab walked out into the page behind (P12-5).

• the modal is inert while closed; open/close toggle it, so the fade

transition is unchanged

• while open, Tab and Shift+Tab wrap inside the modal, and a Tab from

outside it (e.g. right after Ctrl+K) moves into it; focusables are
read per keypress because Pagefind adds result links

Verified in Chrome: 120 Tabs never reach the closed search; open with
results, Tab and Shift+Tab stay inside; Escape returns focus to the
opener.

The gender buttons showed the active gender with a class only, and the
save feedback was a floppy -> check icon flash (P11-11).

• gender buttons carry aria-pressed, set with the active class and on

bind

• each widget has a visually hidden role=status that announces "Avatar

saved" (cleared first so a repeat save re-announces, cleared after
3s; timers stop on abort)

Verified in Chrome: the tree reads "Female avatar [pressed]" and
"status: Avatar saved"; the widget layout is unchanged.

The layer tablist had no tabpanel, every tab was a Tab stop and arrow
keys did nothing (P11-10).

• tabs get ids, aria-controls and a roving tabindex (one Tab stop)


• the layer grid is a tabpanel labelled by the selected tab


• Arrow keys (wrapping), Home and End move and select


• one markActiveTab helper replaces the three copies of the tab sync;

gender resets follow the state manager's current layer (the first
configured layer) instead of a hard-coded index

Also fixes the last tab label ("Background") being clipped: the strip
overflowed its 388px column by 6px, and by 4px at 390px wide. Tab
min-width 3.65rem -> 3.5rem, and no gap at <=420px. Narrower screens
still scroll the strip, as designed.

Verified with the keyboard on /8biticon: arrows, End, wrap, Tab into
the panel, gender switch resets to Face.

Closing an entry action menu (Escape, or choosing an action) hid it
while focus was inside, dropping keyboard focus to <body>. The document
keydown handler also acted on every Escape on the page, and tabbing out
left the menu open (P11-4).

• a menu that holds focus hands it back to its trigger when it closes


• Escape and arrow keys are handled only while a menu is open


• focus moving out of an open menu closes it without stealing focus

Tests cover Escape, choosing an action, Escape with no menu open, and
tabbing away (three fail on the previous code). Verified with the
keyboard on the guestbook page.

isStreamLoading disabled play, stop, previous, next, shuffle, repeat and
the progress bar (and made their handlers return early) until play()
settled. On a stalled stream it never settles, so every control stayed
disabled and a focused control dropped keyboard focus (P8-7).

Remove the flag: each playTrack already supersedes the pending one
(playRequestId, and a new src aborts the old load), so next, previous
and stop can interrupt a stalled load.

Resuming (togglePlayback, restartTrack) now goes through resumePlayback,
which applies the same guard as playTrack: a play() rejected because a
newer request superseded it or pause() aborted it is not a failure.
Pausing a stalled resume used to replace "stream paused" with "playback
blocked".

Verified in Chrome with the stream request held open: controls stay
enabled, Next switches track and keeps focus, Stop pauses at 0:00,
pausing a stalled resume shows "stream paused" (the old catch showed
"playback blocked"), and normal playback is unchanged.

Eight posts used # for section headings, so they had several h1s
next to the post title (the page's h1), and the resume's Timeline and
Skills section titles were h1 elements.

Each affected post's heading levels are renumbered by rank, so its
first level becomes h2 and the rest follow in order (h1/h3/h4 become
h2/h3/h4, which also closes the skipped level). The TOC plugin nests by
relative level, so every TOC tree and its indentation are unchanged:
the built TOC markup is byte-identical for seven posts. In the eighth
(password security) the generated Footnotes h2 now sits at the top
level beside the lead section instead of under it, as in every other
post with footnotes. Timeline and Skills titles are h2.

Section headings in these posts render one size step smaller, matching
the posts that already started at h2. Also un-indents a closing code
fence in IcoMoon part 3 (four spaces is not a closing fence in
CommonMark).

Verified with a full build: every page has exactly one h1.

Text effects rewrite an element's text many times a second (scrambled
glyphs, cursors, half-typed words). Screen readers read those frames,
the aria-live sidebar greeting and terminal log announced them, and the
looping 404 typewriter heading never settled (P7-5, P9-4).

The engine now splits a host on its first animated playback into an
aria-hidden frame, which effects render into, and a visually hidden
label holding the stable text. The label is set once per transition
(to the destination text) and left alone when unchanged, so live
regions announce real text once. Reduced motion and non-DOM hosts keep
plain text. All settled-text writes and reads go through the surface,
so nothing reads frame + label as doubled text, and the glitch shimmer
(which runs on the frame) is still stopped when its host is cleared.

Consumers:

• terminal: log entries get their surface before entering the log so

they are announced once; the log is role=log; the presence header is
no longer a second live region; the font tag and ASCII art rows are
aria-hidden

• terminal atmosphere and music signal label reset before writing the

new text: cancelling a running effect restores that effect's own
target, which reverted the new text

• AsciiWidget art (404, about, sidebar egg) is aria-hidden


• the 404 burn skips screen-reader-only text, which still reports glyph

rects and would ink a second copy

• the label is user-select: none so copying a line pastes it once

Verified in Chrome: the accessibility tree reads clean text while the
frames scramble (404 heading and paragraph, sidebar, terminal log), the
layout is unchanged, the burn follows the visible glyphs and a copied
paragraph has no duplicate. New jsdom tests cover the surface,
transitions, reduced motion, reset, the looping typewriter, content
change, a lost label and the shimmer stop (fails without the
frame-keyed stop).

The two GitHub-backed pages disagreed: a failed repo list failed the
build, but a failed commit fetch shipped an empty changelog (or a
partial one when a later page failed), and failed language/contributor
lookups silently rendered cards with no languages and 0 contributors.

One policy now: GitHub data is complete or the build fails, so Netlify
keeps serving the last good deploy. Every request goes through
githubFetch, which retries transient failures first (network errors,
30s timeouts, 5xx, 429, and 403 secondary rate limits that send
Retry-After; 3 attempts, waits over 60s are not taken) and releases
the response body before retrying. A primary 403 rate limit resets in
up to an hour, so it fails fast. An empty repository's 204 still counts
as 0 contributors.

changelog.astro drops its unreachable error and empty states, and a
SOCIAL.repo that is not a GitHub URL now throws instead of rendering
nothing.

Verified with a production build against the real API (438 commits,
61 project cards) and the built page in Chrome.

Rows written by the SQL default (CURRENT_TIMESTAMP) store
"YYYY-MM-DD HH:MM:SS" while the app writes ISO 8601, so production
held two formats in every date column. Migration 0002 rewrites valid
legacy values to the exact toISOString shape (UTC kept) in Guestbook
timestamp/moderatedAt/adminNotifiedAt/copySentAt and the moderation
log's at column.

Only values with the legacy shape that also round-trip through
strftime are touched, so ISO values, NULLs and malformed text are left
alone rather than nulled (a NULL timestamp would fail NOT NULL and
roll the migration back). Re-running is a no-op.

Test covers the SQL default, mixed and malformed values, NULLs and the
log table on a database stopped before 0002.

Opening the floating (stuck) TOC grows it by ~450px and Chrome's scroll
anchoring scrolls the page down by the same amount to hold the reading
position. That scroll was handled before the asynchronous toggle event,
so the open-state flag still read "closed": the jump counted as a
deliberate scroll down and hid the TOC (translateY(-100%)), and the
toggle event ~100ms later showed it again.

Read details.open in the scroll handler instead of a flag updated on
toggle. Reproduced in Chrome (scroll down, scroll up to reveal, open):
style flipped hidden -> visible before; no transform change after, at
1440px and 390px, and scrolling down afterwards still hides it.

Add jsdom tests for the hide-on-scroll-down path and the anchoring jump
on open and close (the two new ones fail on the previous code).

• ContentLayout renders the post title as the h1 (was h2), so the

document outline starts with what the page is about

• the table of contents is a <nav> landmark labelled by its heading,

which is now an h2 (was the page's only h1), and is excluded from the
Pagefind index so search results stop matching TOC link text

• .content-title and .toc-title keep the previous sizes, line heights,

margins and colours: the visual hierarchy is unchanged, verified by
computed styles at 1280px and 390px

Decision P12-8 from the site review.

cd36ad3f deleted the dead #expand-content p selector together with the
rule body it shared with details > :nth-child(n + 2). The orphaned
selector then joined the following table rule, so every <details>
outside the TOC (meta, changelog, privacy policy, search, sidebar) lost
its warning left border and padding and rendered its content with the
table styles (block, 100% width, 1.5rem margins, 0.875rem text).

Restore the rule for the details selector alone. Verified on /meta and
/changelog: details content has the 1px warning border again.

• check _migrations for each file inside its write transaction instead

of once up front, so the check is serialized by the write lock

• test: two runs racing on one database apply each migration exactly

once (fails on the previous runner with "duplicate column name")

Two overlapping db:setup runs both saw 0001 as pending; the second hit
"duplicate column name" on ALTER TABLE and failed.

• store the guest's "send me a copy" opt-in as copyTheme (the site theme

the copy renders in), set only when an address was given; migration
0001 adds the column

• a copy is sent only while the entry is visible: on submit for entries

that went live, on approval in /admin for entries the classifier held;
sendEntryCopy refuses anything not visible

• deliverRequestedCopy claims copySentAt atomically before sending, so a

double-clicked Approve sends once; a failed send releases the claim so
a later approval retries

• the admin result line says whether the requested copy went out


• drop the pending/hidden variants of the copy email; every copy now

gets the view link plus the contact line

• store the anchored submission time as the entry timestamp, so the row

matches the classification windows and the email idempotency key

The recipient address is never verified. Copying held entries at submit
let anyone mail content the classifier already distrusted from this
domain to any inbox; the moderator now gates every such email.

Deploy order: run npm run db:setup against production before deploying.
Without the column, guestbook reads and inserts fail.

Decision P2-5 from the site review.

• add applyMigrations(client, dir): runs each db/migrations/NNNN_*.sql not

yet recorded, in filename order, inside a write transaction together
with its _migrations record, so a failure leaves neither half behind

• db:setup now uses it; tests and the real-DB guestbook suite build their

databases through the same path

• tests: apply-once idempotency, adopting a database created by the

baseline alone (production today), and rollback of a failed migration

The baseline is CREATE ... IF NOT EXISTS and could simply be re-run, but
schema changes such as ALTER TABLE ADD COLUMN cannot be repeated, so
applied files are now recorded instead of replayed.

• remove bearer-token auth: checkAdminAuth(cookies) is now a synchronous

check of the signed session cookie; the raw token is verified with
argon2 only by the /admin login form, which then sets that cookie

• update the middleware and both admin pages; tests now assert that a

session is the only credential and that checking it never runs argon2

Nothing used the Authorization: Bearer path, and every request carrying
that header cost an unthrottled argon2 verify (CPU amplification and an
unthrottled guessing endpoint next to the delayed login form).

Verified on an isolated dev server: the correct token sent as a Bearer
header now gets 303 -> /admin; form login + cookie still opens the
moderation page.

Decision P1-7 from the site review.

Dependency upgrades, the phased site-wide review and polish:

• security: admin auth bypass via percent-encoded paths, guestbook

input boundary (javascript: links, CSS injection, length caps), rate
limiting that never fired, music proxy limited to public playlists

• service worker no longer serves the offline page for slashless URLs


• accessibility: keyboard-operable nav drawer, customizer, avatar

generator, disclosures; focus handling in terminal and back-to-top

• soft-navigation leaks in text effects, offline page, avatar, search


• drafts excluded everywhere; SEO noindex/sitemap; privacy disclosures


• Netlify caching, Node 24, install flags; pre-push type check


• guestbook rainbow magical title and hearts

• housekeeping/site-polish: (78 commits)

feat(guestbook): rainbow magical title and rainbow haunted hearts
fix(guestbook): restore the space between "and" and "color faded text"
fix(offline, nav): retry recovery after a failed redirect; DOM-order tab trap
fix(music): keep the last good catalog when a miss refresh fails
fix(music): readable long titles under reduced motion
fix(404): only set up the 404 neofetch widget on the 404 page
fix(seo): anchor the sitemap filter to top-level paths
fix(music): ignore superseded play() results; pause visualizer when hidden
fix(avatar): release generator and guestbook listeners when leaving
fix(neofetch): only touch the brand name on the page with the widget
fix(search): one Ctrl+K handler, no ?q= on other pages, scoped shortcuts
fix(content): real modified dates, word counts and search date sort
fix(seo): keep utility and admin pages out of search engines
docs(privacy): disclose sessionStorage keys and the offline cache
fix(pages): restore spaces lost where prose wraps before inline tags
fix(offline): stop polling when leaving /offline
fix(styles): reduced motion for animations, focus and forced colors
fix(content): exclude drafts from every page, list, feed and index
fix(a11y): make the 8biticon share control a button
docs(privacy): disclose every way the avatar-state key gets written
...

• the Guestbook h2 uses the declarative magical text attributes

(data-magical-text, a 7-color rainbow in data-magical-text-colors,
heart adornment); the global registry in Layout activates it

• entry cards' Haunted heart creatures use the same rainbow palette

instead of primary/accent

Colors are literal hex values in the attributes, by choice.

The line wrapped before the faded-text span, so Astro's HTML
compression rendered "andcolor faded text". Add the {" "} idiom.

• /offline: if the redirect to the last page fails, reset the guard,

show offline again and restart polling; before, recovery stopped for
good at "Redirecting..." (eb40c6c2 removed the old retry path)

• mobile drawer Tab trap orders its stops by DOM position (the sidebar

precedes the header), so Tab from the hamburger no longer reaches the
header controls behind the scrim

Found by the final audit review. Verified: 50 mixed Tab/Shift+Tab
presses stay inside the open drawer.

isInPublicCatalog's early refresh replaced the cached catalog before the
load finished; a failed refresh then cleared the cache, so a transient
Navidrome error turned unknown-id 404s into 502s and dropped a valid
catalog. Load the refresh separately and only swap it in on success.

Found by the final audit review of d179b41f.

The global reduced-motion rule (cd36ad3f) ends the now-playing marquee
after one instant pass, which left long titles clipped with no way to
read them. Under reduced motion truncate with an ellipsis instead, and
put the full title in the viewport's title whenever it overflows.

Found by the final audit review.

The 404 page's astro:page-load listener outlives the page and set up
the neofetch widget on every later page, so after /404 -> /about the
About widget was bound twice (one dice click rendered twice, one setup
leaked). Return early unless [data-page-404] is present and tear down
on astro:before-swap. Completes 6ef56e6e (found by the final audit).

The filter matched any path segment, so /tags/meta/ (two entries use the
tag) was dropped from the sitemap, and any future tag named search, admin
or offline would be too. Anchor it to the first segment and add a test
with both kinds of path.

Found by the final audit review of 81b7f20b.

• tag each playTrack with a request id and ignore a settled play() from

an older request: switching tracks rejects the previous play() with
AbortError, whose catch/finally marked the new track paused and
"playback blocked" and re-enabled controls while it was still loading

• distinguish autoplay blocking (NotAllowedError) from a failed stream

instead of reporting both as "playback blocked"; AbortError is a no-op

• AsciiVisualizerController.setVisible(): no analyser rAF loop or idle

interval while the player is minimized, closed or never opened; the
loop resumes for the current playback state when shown again

Verified against the real Navidrome: two rapid track clicks leave the
second track playing; rAF calls ~234 per 2s with the player open and 0
while minimized with audio still playing.

• AvatarGenerator: destroy() removes the controller's window

avatar-state-change listener; called before re-init and on
astro:before-swap. Each /8biticon visit left a controller (with an
image cache of every layer) re-rendering on every sidebar avatar change

• guestbookAvatarWidget: abort its controller on astro:before-swap, not

only on the next guestbook init

• guestbookCustomizer: the outside-click document listener is tied to a

per-visit AbortController (it accumulated per visit, holding detached
panel refs)

Verified: /8biticon -> /guestbook -> /about with sidebar randomizes, no
errors; the customizer still opens and closes on outside click.

neofetch.ts is imported by /about but its astro:page-load listener runs
for the rest of the session: every later page reset #nav-brand-name to
"alex" (overriding the sidebar egg's name) and set up the /404 page's
neofetch widget a second time. Return early unless the neofetch widget
is on the page and is not the 404 page's own.

• only the /search page box mirrors its query in ?q=; typing in the

floating modal rewrote every page's URL (/blog/x/?q=foo), so a reload
or shared link re-ran the search in a hidden input

• FloatingSearch handles Ctrl/Cmd+K in one place: open when closed,

otherwise focus the input. The extra initSearchShortcut handler focused
the invisible modal input first, so openSearch recorded that hidden
input as the opener and closing put focus on it

• only refocus an opener that is still in the document


• /search binds its Ctrl+K and "/" shortcuts per visit, scoped to its own

box, and unbinds on swap; the module script runs once per session, so
its window.__*Cleanup pattern never ran and the handlers stayed on
every later page

Verified: Ctrl+K on /about opens the modal, typing keeps the URL clean,
Escape returns focus to the page; /search still updates ?q=; after
visiting /search, Ctrl+K on /about still opens the modal.

• pass updatedDate as dateModified, so article JSON-LD and

article:modified_time reflect edits (10 entries have updatedDate;
dateModified always equalled datePublished)

• pass the remark plugin's exact word count to the JSON-LD instead of

reading minutes x 200

• Pagefind date sort/meta read the date element itself:

data-pagefind-sort="date:{date}" was a quoted attribute, so the
literal "date:{date}" shipped and "sort by date" ordered by garbage;
the date meta also captured the reading time and description

Verified by build on /blog/2025-06-19-resume: sort value 2025-06-19,
dateModified 2026-03-17, wordCount 83.

• noindex /search, /404, /success, /offline, /admin and

/admin/guestbook (they rendered "index, follow")

• sitemap filter excludes /404, /success, /search, /offline, /meta,

/admin and /.well-known paths; /meta was noindex yet listed, and the
admin pages were listed too

Verified by build: those pages carry "noindex, nofollow"; the sitemap
has 85 URLs with none of them, content pages (/about, /verify) intact.

The privacy page said the only things written to the browser are twelve
localStorage values, "not sessionStorage", and the PrivacyPolicy summary
and DNT policy said the same. The site also writes two sessionStorage
values (nav-brand-visited, offline_last_page: the previous page's
address) and its service worker keeps the site's pages in Cache Storage.

Describe both on /privacy, in the PrivacyPolicy summary, and in new
SESSION STORAGE and OFFLINE CACHE sections of dnt-policy.txt.

Astro's HTML compression drops the newline between a word and an inline
tag on the next source line, so readers saw "andThe First Descendant"
(interests), "Coversalex@ ... andcontact@" (verify), "persist
withtheme-flavor" (palette) and "emphasis,search result mark" plus two
token lists on /style. Add the {" "} idiom at each wrap point.

Also drop the duplicated ogImage prop on /success and /search.

The /offline script discarded the teardowns returned by startPolling and
setupListeners. With soft navigation the module outlives the page, so
after leaving /offline the next successful poll (or an "online" event)
ran tryRedirectToLastPage and pulled the visitor away from whatever page
they had moved on to.

Set up on astro:page-load only when the offline page is present, tear
down polling, listeners and any pending redirect on astro:before-swap,
and redirect at most once per visit.

Verified: /offline -> soft nav to /about stays on /about; staying on
/offline still redirects once reachable.

• the global prefers-reduced-motion rule also ends CSS animations after

one near-instant pass (elements and pseudo-elements) and disables
smooth scrolling; it only covered transitions, so .faded-text, the
dice spin, share-notification slides and the honeypot shake still ran

• show a focus ring on the guestbook message textarea wrapper (the

textarea is outline: none and had no focus indicator at all)

• .faded-text falls back to plain system text under forced-colors (the

transparent fill stayed while the gradient was dropped: invisible)

• mobile nav scrim uses color-mix from black instead of an oklch literal


• delete dead CSS: .nav-avatar-controls, #ascii-404, #expand-content p,

and the unused glow-pulse / glow-pulse-accent keyframes

• add getPublishedEntries() in src/lib/content/published.ts, the only

reader of content collections; it drops entries with draft: true

• use it in all 9 places that called getCollection directly: post and

note pages, blog/notes/tag indexes, prev/next (ContentLayout), RSS
and OG images

• contract test: no source file outside the helper calls getCollection

The schema has a draft field, but nothing filtered on it: a draft would
have been built, listed, tagged, linked as prev/next, put in RSS, the
sitemap and the search index. No content is a draft today.

Verified by building with a planted draft: no page, no index/tag/OG/
sitemap entry.

It was an <a> with no href, so it could not be focused or activated by
keyboard, and the aria-label on its role-less wrapper was ignored. Use
<button type="button" aria-label="Share avatar"> (the existing .icon
styles already cover a button) and role="group" on the wrapper.

Verified: Tab reaches it, Enter shares (notification shows); unfocused
it looks as before.

The privacy page, the PrivacyPolicy summary and the machine-readable
DNT policy said avatar-state is written only by the /8biticon builder.
It is also written by the sidebar avatar's save button and by ticking
"Include avatar" on the guestbook form. State all three, and reassert
the DNT policy date.

• ?gender= that differs from the current gender now starts from that

gender's defaults; it kept the other gender's layer values, e.g. a
saved male clothes 62 on the female set (59 options), which failed to
load and was silently rejected when saved

• ?avatar= goes through parseAvatarState (integers in range, whole state

or nothing); "1.5-2-..." and "1e1" used to pass Number() and the range
check, producing 404 layer images and unsavable states

• look the linked entry up with getElementById(decodeURIComponent(...))

instead of querySelector(hash); /guestbook#entry-a/b is an invalid
selector, threw, and aborted the rest of the guestbook init (send-copy
toggle, theme capture, share notification)

• scroll to the linked entry without smooth scrolling, and mark it with

a static outline instead of the fading highlight, under
prefers-reduced-motion

Verified: /guestbook#entry-a/b loads with no errors; #entry-20 still
scrolls to and highlights the entry.

• radius, border color and border style options are now

<button aria-pressed> with names ("Radius 1rem", "Accent",
"Border dashed") in role="group" sets labelled by their headings;
they were click-only <div>s and colors were conveyed by color alone

• selectOption() keeps the .selected class and aria-pressed in sync for

clicks and for syncUI

• the hover preview also runs on focus/blur


• the pattern select and the width slider are labelled by their

headings; the slider exposes aria-valuetext ("1.5px")

• buttons drop UA chrome and get a focus-visible ring

Verified by keyboard: open the panel, Enter on a radius, color and
style updates aria-pressed and the submitted style JSON; the panel
looks as before.

The toggle was a clickable <h3>, so the guestbook customizer, the
privacy summary and the search tips could not be opened with a
keyboard. Keep the heading and put a full-width
<button aria-expanded aria-controls> inside it (disclosure pattern);
the body gets an id and aria-expanded follows the hidden state.

• render each layer choice as <button type="button" aria-pressed> with

a name ("Clothes 12"); they were click-only <div>s, so keyboard and
screen reader users could not pick any face, clothes, hair, eyes,
mouth or background (only Randomize worked)

• thumbnails and the number badge are aria-hidden (the button is named)


• move the inline hover/selected styles to avatar.css and add a

focus-visible ring; no scale on hover under prefers-reduced-motion

Verified: Tab to a choice, Enter selects it and moves aria-pressed;
the grid looks as before.

• size the canvas backing store by devicePixelRatio (capped at 2) and

draw in CSS pixels; it was innerWidth x innerHeight stretched by CSS,
so glyphs were blurry on 2x/3x displays

• skip no-op resizes: reassigning width/height cleared the rain on every

mobile URL-bar or window-drag resize event

• mark the canvas aria-hidden (decorative); reset the rAF id when tick

finds no canvas so the loop can restart

• starsBackground: drop a MutationObserver on data-flavor whose handler

only toggles data-stars-bg (flavor changes never affect it)

Verified at deviceScaleFactor 2: canvas 1600x1200 for an 800x600 view,
glyphs crisp.

• hauntedRegistry and magicalTextRegistry accept data-haunted-creature

and data-magical-text-adornment only when the kind exists, else the
default applies; an unknown value threw a TypeError in the controller
and aborted initialisation of every later element on the page

• mark the Haunted creature layer aria-hidden (some creature SVGs carry

no aria-hidden of their own)

• track bound elements and, on astro:after-swap, release every binding

whose element left the document: document listeners (resume,
route-enter, idle-return), IntersectionObservers, random-time timer
chains, and any effect still running (the looping 404 typewriter)

• register a cleanup for random-interval timers (they had none)


• never start an effect on a detached element (backstop)


• glitch shimmer: one pending timer instead of an ever-growing array, a

post-effect stop that clearActiveEffect and the next transition call
(the shimmer outlived its own resolve, so cancel() could not reach it
and a second glitch overlapped it), and it stops once detached

Before: every soft navigation left ~35 document listeners, 2 observers
and 3 self-rescheduling timer chains per page bound to detached nodes,
which kept playing effects on them; work grew with session length.

Verified: after /404 -> /about, the 8 swapped-out effect elements get
0 DOM writes over 8s (the persisted music label still animates).

• stop propagation when the input handles Escape: the document-level

handler also ran, so closing the completion menu (or leaving
fullscreen) minimized the whole terminal in the same keypress

• on minimize, move focus to the dock chip that restores the terminal

(or back to the opener) when focus was inside the window; hiding the
window used to drop focus to <body>. Only refocus an attached opener

• Backspace typed while focus is outside the input deletes one

grapheme, not one UTF-16 unit (it left half an emoji in the command)

• cap session command history at 100 and skip consecutive duplicates;

maxlength 256 on the input (echoed in full by the unknown-command
message)

Verified: Tab opens completions, Escape closes only the menu, a second
Escape minimizes with focus on the dock chip; "go😀" + Backspace from
the log leaves "go".

Verbose words were stripped from every input, so "search more" became a
bare "search" and "find details here" lost a word. After find, search or
lookup the rest is the query: only the explicit --verbose / -v flags
count as verbose there.

Keep an in-memory "visit recorded" flag next to the sessionStorage one.
With storage blocked (private mode, disabled site data) the session flag
always read false, so every soft navigation ran onNewVisit: the visit
count went up per page, last-visit was overwritten and the arrival
greeting replayed.

Verified with sessionStorage throwing: three soft navigations leave the
visit count unchanged.

The prompt mirror took the cell under the block cursor with
afterCaret[0], a UTF-16 unit: with the caret before an emoji it painted
a lone surrogate (and the rest started with the other half). Take the
first grapheme instead, for the input and for the completion ghost text.

• drop the substring tier of the last-resort matcher: "ix" (inside the

alias "fix") reset the terminal, and other fragments could close it
or clear history

• accept a prefix only when it is at least 2 characters and matches

exactly one command; ambiguous input falls through to the unknown
command message with suggestions instead of picking the first command
in registry order

• the typed-suggestion path already used prefixes, so the ghost

completion and Enter now agree

The helper text revealed on :focus-visible of the info icon, which has
no tabindex and can never take focus, so keyboard users on hover-capable
devices never saw it. Reveal it when the option's own control has
keyboard focus instead.

Verified: tabbing to an option shows its description.

• move the bullet after the commit link inside its conditional, so

builds without COMMIT_REF (local, GitHub Pages mirror) no longer start
the line with "•"

• give the icon-only Astro link an accessible name ("Built with Astro")

and hide the decorative icons from assistive tech

• intermediate segments link only to sections listed in navigation.ts;

others render as text. /.well-known/change-password linked to a
/.well-known 404, and a 404 page at /foo/bar linked /foo and /foo/bar

• mark the current page with aria-current="page" and expose the trail as

a Breadcrumb navigation landmark (role on the existing inline span, so
the layout is unchanged)

Verified: /blog/<post> and /tags/<tag> link their section; .well-known
and unknown 404 segments are text; the header looks the same.

workbox-<hash>.js lost its immutable header when the catch-all /*.js
rule was removed (ced99350). It is content-hashed, so it is safe to
cache forever.

• fail the push when generate:ascii itself fails, instead of checking

an unchanged file and passing

• diff against HEAD, not the index: the pushed commit is what matters,

and a staged-but-uncommitted regeneration must not pass

Found by the Phase 2-4 audit review of 793dfebc.

Observe data-theme instead of listening for "set-theme". Since f43316f9,
URL theme overrides (?theme=) paint without dispatching that event, so
/404?theme=light over a saved dark theme drew the dark-theme fire.

Found by the Phase 2-4 audit review. Verified: /404?theme=light now
renders the same light palette as a saved light theme.

• load playlist details with Promise.allSettled: one failing playlist

is logged and left out instead of failing the whole catalog (every
music route returned 502 until a full load succeeded)

• serve /api/music/playlists from the catalog itself, so the list never

offers a playlist, track or cover the other routes would refuse

• isInPublicCatalog(): on a miss, reload the catalog once (at most every

30s) before answering 404, so a playlist just made public or a cover
id changed by an edit is not refused for the 5-minute TTL

• forward If-None-Match / If-Modified-Since for covers and pass 304

through; abort upstream at once if the request is already aborted

Found by the Phase 2-4 audit review of a659fdaf. Verified against the
real Navidrome: 10 playlists, 206 stream, cover 200.

• hide the inactive brand variant with visibility as well as opacity,

max-height and pointer-events; visibility switches instantly when a
side appears and waits for the fade when it disappears, so the
crossfade is unchanged

• drop aria-hidden="true" from the collapsed brand container: it wrapped

a focusable role="button" (axe aria-hidden-focus), and visibility now
hides it from assistive tech when it is not shown

Before: in the expanded sidebar the invisible collapsed-avatar trigger
was a tab stop; in the collapsed sidebar the invisible prompt button was.
Verified in both states: only the visible variant is focusable;
screenshots match the previous look.

• hamburger is a <button aria-controls="nav-menu" aria-expanded> that

toggles the existing #nav-toggle checkbox (still the CSS state);
it was a <label> for a display:none checkbox, so keyboard and switch
users could not open the drawer, and Escape "returned focus" to an
element that cannot take focus

• below 1024px the closed drawer is inert (its ~35 off-canvas links were

tab stops); opening moves focus into it and Tab is trapped between the
hamburger and the drawer until Escape, a link or the overlay closes it

• drop role="navigation" + aria-label from the <aside>: it nested a

second "Main navigation" landmark around the real <nav>

• sidebarCollapse: handle Escape only on desktop; at mobile widths the

same Escape that closed the drawer also cleared the saved collapse
preference

Verified at 390px with the keyboard: closed drawer has no tab stops,
Enter opens with focus inside, 60 Tabs stay inside, Escape closes and
returns focus, overlay click syncs aria-expanded; desktop not inert.

• themeManager: toggleTheme (no callers; also skipped disabling

match-device mode, unlike handleThemeToggle) and resolveActiveTheme

• keyboardShortcuts: registerShortcuts


• copyToClipboard: the CopyToClipboard class and its options type

knip still reports eight exports of the unwired transition-picker
system, kept until the finish-or-remove decision is made.

• tabTitle: clear any running rotation before starting a new one; a

second "hidden" without "visible" (bfcache) orphaned an interval that
rewrote document.title forever

• scrollProgress: 0% on pages shorter than the viewport (was NaN%), and

no width transition under prefers-reduced-motion; remove the unused
removeProgressBar

• Layout: fix a comment that labelled the console egg script as scroll

progress

• only assign iframe.src when the themed URL actually differs; every

assignment restarts navigation, so each page load and theme event
reloaded the GitHub contributions / resume iframe

• observe data-theme instead of the "set-theme" event, which URL theme

overrides no longer dispatch (f43316f9)

• drop initMultipleIframeThemes and cleanupIframeTheme (unused; the

cleanup built fresh closures and removed nothing)

• add clientRuntime.dom.test.ts (jsdom) for both, plus back-to-top

• cancel the auto-hide while the button has focus (focusin/focusout),

not only on hover; hiding a focused button dropped keyboard focus
to the body

• after scrolling up, move focus to #main-content (tabindex -1) so the

keyboard user continues from the top of the page

• scroll with behavior "auto" under prefers-reduced-motion


• no focus ring on #main-content: it is a programmatic focus target

(skip link, back-to-top), not a control

• add getPublicCatalog() in navidrome.ts: ids of public playlists, the

tracks they contain and the covers they use, cached per warm function
instance for 5 minutes (failed loads are not cached)

• /api/music/playlist/[id], /stream/[id] and /cover/[id] now 404 any id

outside that catalog

• delete /api/music/albums: unused by the player, and it listed the

whole album library unfiltered

• validate ids against /^[A-Za-z0-9_.-]{1,128}$/ before any upstream call


• stop returning upstream and config errors ("Wrong username or

password", missing env var names) to the browser; log them and answer
"Music service unavailable" (502/503) or "timed out" (504)

• time out JSON calls (8s) and media until headers arrive (8s), and

abort the upstream stream when the browser disconnects

• covers: public, max-age=86400 plus ETag/Last-Modified; pass 404/416

through; nosniff on media responses

• add musicApi.test.ts route tests against a fake Navidrome

Before: the playlists list hid private playlists, but any private
playlist was readable by id, and stream/cover proxied any id in the
library with the server's credentials.

Verified against the real Navidrome on an isolated dev server: 10
public playlists, playlist detail, 206 range stream, cacheable covers;
unknown ids 404, malformed id 400, /albums 404; in-browser playback OK.

• setTheme(theme, false) now paints data-theme and color-scheme directly

instead of dispatching "set-theme": astro-themes' handler stores
whatever that event carries, so persist:false still saved the URL value

• add paintTheme() and use it for the after-swap URL/match-device

restamp, which previously set data-theme but left color-scheme on the
stored theme (mismatched scrollbars and form controls)

• add a test that a URL theme fires no "set-theme" and leaves storage

Before: a visitor whose saved theme was dark who opened a ?theme=light
link (embed, screenshot, share) had their saved preference silently
switched to light on every later visit.

Verified in the browser: /?theme=light paints light with the saved
dark intact; plain / is dark again; the manual toggle still persists.

• add both to tsconfig include; stop ignoring *.config.ts in eslint


• replace the any-typed remarkReadingTime signature with precise types


• cast the three rehype plugins whose Node->Node transformer types do

not satisfy Astro's Root->Root signature to the unified() plugin
entry type, instead of any (and without the deprecated
markdown.rehypePlugins type)

markdown.config.ts holds real logic but was outside astro check and
eslint. Verified by build: reading time, heading ids/TOC (27 posts),
external-link icons and accessible emoji all still render.

• strip a trailing slash only when present; slice(0, -1) cut the last

character of slashless URLs (dev server)

• drop the no-op .replace(".mdx", "") in the OG route: glob loader

ids carry no extension

The schema accepts any non-empty permalink, but prev/next navigation and
share links use it while URLs and OG images use the file id, so a typo
diverges silently. Verified the test fails on a planted typo.

• stop listing every component, layout and client script as a knip

entry; they are now reached through pages, so orphans get reported

• load musicPlayerModal via <script> import like every other component;

knip cannot follow <script src>, and it was the only one using it

• keep MagicalText.astro as an explicit entry: built but not yet placed

on any page (decision pending)

knip now reports 15 unused exports in the client runtime; they are
removed with the Phase 4 dead-code fixes.
Verified: music player opens from its trigger, no console errors.

• regenerate src/data/ascii-art.json and fail with a message when it

differs from the committed file, instead of git-adding it: staging
in pre-push never makes it into the push and left the tree dirty

• run astro check before every push; vitest strips types, so a type

error in a test (bb465efe) passed the pre-commit hook

Verified: clean tree passes; a stale committed file fails with exit 1.

The page claimed the site has no authenticated section; /admin exists
(owner-only token login). State that there are no user accounts or
passwords to change instead.

• drop the catch-all immutable rules for /*.js and /*.css; they also

hit unhashed /sw.js and /registerSW.js. Serve both with no-cache.
Hashed build assets keep immutable via /astro/*

• NODE_VERSION 22 -> 24 to match local development; add package.json

engines (">=22.23.4", Astro's floor)

• remove NPM_FLAGS="--legacy-peer-deps"; the lockfile installs cleanly

with a plain npm ci, and the flag resolved peers differently from
local installs

• remove @netlify/plugin-sitemap: @astrojs/sitemap already emits

sitemap-index.xml, and the plugin's sitemap.xml would shadow the
/sitemap.xml redirect with a second, unfiltered sitemap

• delete public/_headers (duplicated netlify.toml content types) and

the unsigned root public/security.txt; redirect /security.txt to
/.well-known/security.txt, the copy the signature covers

• add src/tests/deployConfig.test.ts contracts for all of the above

plus the IcoMoon token

Verified: clean npm ci of this lockfile without the flag (exit 0).

• load /fonts/icomoon/style.css?<token> with the same token its font

URLs use, from one ICOMOON_TOKEN constant shared with the preload

/fonts/* is served immutable for a year, but the stylesheet URL never
changed. After the 2026-10-22 IcoMoon regeneration (7 new icons),
returning visitors kept the old stylesheet and the new icon classes
rendered as nothing. A contract test (next commit) keeps the Layout
token in sync with style.css.

• retry undici's TypeError("fetch failed") and read the TCP/DNS code

from err.cause; the old pattern only checked err.message, so real
network failures never retried and logged only "fetch failed"

• keep the abort timer running until the response body is read, so a

stalled error body cannot hang the guestbook POST

• add a total budget across attempts and backoff

(GUESTBOOK_EMAIL_DEADLINE_MS, default 6s, max 8s; per-attempt default
4s), since the POST awaits delivery inside a 10s serverless limit

• parse tuning env vars so "0" is honoured; GUESTBOOK_EMAIL_RETRIES=0

used to fall back to 2 via Number(x) || 2

• send the admin notification and entry copy in parallel, each with its

own error handling, so a failed send or delivery-record write never
skips the other; log the reason when a send does not go out

• drop getNotificationFlags: it read flags on a row inserted a moment

earlier, so they were always null; dedup comes from the Idempotency-Key

Before: worst case was ~31s per email, sequentially, after the entry was
already inserted. The function would time out, the visitor would see an
error and resubmit, creating a duplicate entry.

Verified on an isolated dev server: POST redirects in ~50ms with both
failures logged (no Resend key configured there). Suite run 3x clean.

• set maxlength on name, email, url and message from ENTRY_LIMITS so

the browser enforces the server limits

• when the server rejects a submission (not a bot), answer 400 and show

an error notice above the form instead of silently re-rendering it;
honeypot hits still get the plain page

• re-validate the stored avatar state at render (legacy rows) and pass

the canonical value to the canvas and entry actions

Found by the Phase 1 audit review: the 100-character name cap from
94f3724b was enforced with no feedback.

• accept whitespace or / after the tag name, so <svg/onload=...> and

<img/src=x ...> are hard-hidden again (the previous /<[^>]+>/ caught
them; the narrowed regex in 99487a49 did not)

• if an entry is deleted between the read and the moderation batch,

return false instead of surfacing the foreign-key failure as a 500

Found by the Phase 1 audit review.

• add singleLine(): line breaks (CR/LF, NEL, U+2028/U+2029), C0/C1

controls and bidi overrides/isolates collapse or drop; use it for
name and email in both plain-text bodies so a field cannot forge a
"Status:" or "Review:" line

• sanitizeHeaderValue and parseEmailAddress now cover the same

characters, not only CR/LF, and truncate by code point

• truncate() cuts on code points; a split surrogate pair serializes as

a lone "\ud83d" that strict JSON parsers can reject

• HTML templates use the same sanitizeUserText + truncate as the text

part; preheaders no longer slice mid-emoji

• build the avatar image URL with URLSearchParams


• render the "open a GitHub issue" link only when the URL is known

• escape the image src and alt interpolated into each RSS item's HTML

description; fall back to the build time for lastBuildDate when the
blog collection is empty instead of emitting "undefined"

• hash-admin-token: reject tokens with leading or trailing whitespace

(the login trims input, so such a token could never log in) and warn
on stderr that the argv form leaks the token into shell history and
ps; stdout still carries only the hash

• answer moderation POSTs with 303 to /admin/guestbook?filter=&result=&entry=

so reloading the page cannot repeat the action

• show "no longer exists" when the entry id is unknown


• validate the filter query against the known values (unknown -> all)

instead of casting it

Verified on an isolated dev server (local SQLite, throwaway admin
token): hide -> 303 -> "Entry #21 hidden.", unknown id -> "no longer
exists", ?filter=bogus -> 200 with all entries, two audit rows written.

• return false from updateEntryStatus when the entry does not exist,

instead of inserting an audit row that fails the foreign key (500)

• write the status update and its audit row in one db.batch so they

commit together

• add guestbook.db.test.ts: runs guestbook.ts against a real libsql

database from the baseline migration (duplicate + rate-limit through
createGuestEntry, moderation update and audit row, unknown id)

The existing guestbook tests mock the DB, which is why the timestamp
format bug never surfaced. The new suite covers the real query path.

• validate the HMAC session cookie first in checkAdminAuth and only

verify a bearer token when no valid cookie is present

• add a test that a valid cookie never triggers argon2

The middleware calls checkAdminAuth on every /admin* request. With the
bearer check first, any request carrying an Authorization header paid
a full argon2 verify even for a logged-in admin.

• require a tag-shaped match for html_tag (<, optional /, letter-led

name, then > or attributes); "I <3 this, 5 > 4" was auto-hidden

• run html_tag, bbcode, obfuscated_link and url_shortener over the name

as well as the message, and url_shortener over the url field

• bump CURRENT_MODERATION_VERSION to 2 for the changed ruleset

The name is rendered publicly beside the message but skipped every
hard check, so "<b>Buy now</b>" or "bit.ly/xyz" as a name published as
visible. The old /<[^>]+>/ matched any "<" followed later by ">", which
hid ordinary prose with no review.

• add src/lib/api/guestbook-input.ts: readGuestbookForm, sanitizeEntryUrl

(http/https only, normalized href), parseEntryStyle (customizer
allowlists only), normalizeAvatarState, and field length limits

• use it in the POST handler (missing fields no longer throw; a

non-form body returns 400), in createGuestEntry before insert, and
again at render time in GuestbookEntry and the admin page for rows
stored before the boundary existed

• show unsafe stored URLs on the admin page as inert text, not links


• replace the email helpers' looser parseEntryStyle with the shared one

(also closes the prototype-key palette lookup) and have sanitizeUrl
return the normalized href so plain-text emails cannot gain lines

Before: url only had a client-side pattern, so a POSTed
javascript: URL was stored and rendered as a clickable href on the
public page and on the admin page (script on the admin origin). The
style JSON was spread unvalidated into the inline style attribute, so
an entry could overlay the page or load third-party images. name,
email, url, style and avatarState had no length caps.

Verified on an isolated dev server (local SQLite, no email): hostile
POST stores url NULL, a defaulted borderWidth and avatarState NULL; a
hostile legacy row renders with no javascript: href and default style;
non-form POST returns 400.

• replace .default(sqlCURRENT_TIMESTAMP) with $defaultFn(() => new Date())

on Guestbook.timestamp and GuestbookModerationLog.at

• add a libsql integration test that inserts without a timestamp and

queries a same-day window

Drizzle emitted CURRENT_TIMESTAMP for omitted timestamps, which SQLite
stores as "YYYY-MM-DD HH:MM:SS". Window bounds are bound as ISO
("...T...Z") and compared as text; " " sorts before "T", so every row
inserted the same UTC day fell outside the 10-minute rate-limit and
1-hour duplicate windows. Spam bursts were never rate_limited or
flagged duplicate.

The migration SQL default is unchanged (inserts outside Drizzle). Rows
already stored in the old format are older than any window.

• replace workbox navigateFallback with a NetworkOnly navigation route

that uses PrecacheFallbackPlugin for /offline/index.html

• set navigateFallback to null explicitly; vite-plugin-pwa defaults a

missing value to "index.html", which would serve the home page instead

• drop the hand-maintained navigateFallbackDenylist (redirects, SSR

routes and feeds now reach the network by construction)

• update the Astro 7 contract test for the new fallback shape

navigateFallback is an app-shell setting: once the service worker was
installed it answered every navigation missing from the precache with
the offline page, even while online. Precache keys are dir/index.html,
so every slashless URL (/about, /blog, /now: all sidebar hrefs), the
/sps redirect and any future redirect missing from the denylist showed
"Offline" on reload, new tab, bookmark or shared link.

Verified on a built dist with an active worker: online /about, /blog,
/now redirect to their pages, unknown paths get the server 404; offline
precached pages load from cache and /guestbook shows the offline page.

• decide admin-ness from context.routePattern as well as the raw

pathname, so /%61dmin/guestbook and /%2561dmin/guestbook get the
CSRF check, auth redirect and no-store headers

• re-check admin auth inside admin/guestbook.astro as defence in depth


• add middleware regression tests for encoded and double-encoded paths

Astro decodes the pathname repeatedly before routing, but the
middleware tested the raw URL pathname. An unauthenticated GET to
/%61dmin/guestbook rendered the full moderation page (entries,
emails, moderation actions) with no Cache-Control, both locally and
on production (verified read-only: 200 "Guestbook Moderation").

Verified: dev server returns 303 -> /admin with no-store for all
encoded variants; /, /about/, /administer unaffected; middleware
tests 23/23; astro check 0 errors.

• mock getContext with mockImplementation typed as the full method

signature instead of mockReturnValue

• mockReturnValue resolved to the last getContext overload

(GPUCanvasContext), so astro check failed with ts(2345)

• vitest strips types, so the suite passed while astro check failed

Verified: astro check 0 errors; burn404.dom.test.ts 7/7 pass.

npm 11.19.1 (bundled with Node 24.22.1, now the local default) no longer
marks the optional pg-cloudflare package as dev-only. Metadata only; no
version or resolution changes.

• add jsdom as a dev dependency; tests opt in per file with

// @vitest-environment jsdom, so existing node-env suites keep their
speed and isolation

• cover the burn404 soft-navigation lifecycle: both fire canvases are sized

on first load and again after 404 -> away -> back, and the torch mutation
observer rebinds to the new 404 article

• cover resolveFlammableAnchor and containsFlammableAnchor anchor resolution

The lifecycle tests were run against the pre-fix burn404.ts and
burn404torch.ts from main: both soft-nav regressions fail there and pass on
this branch. jsdom has no canvas backend or layout engine, so the file stubs
a minimal 2D context, matchMedia, document.fonts, requestAnimationFrame, and
Range#getClientRects. The last one stays installed file-wide because the
torch's debounced detection can fire after a test ends.

Vite flags __dirname as unsupported by the native config loader planned as
the default in its next major. import.meta.dirname is the ESM equivalent.

Mechanical reformat of tracked files after the formatter major upgrades in
the previous commit. lint-staged would otherwise apply it piecemeal to every
file a future commit touches, mixing format churn into unrelated diffs.

• prettier-plugin-astro 1.x breaks inline elements onto separate lines and

writes explicit {" "} separators where whitespace is significant

• prettier-plugin-toml 4.x adds blank lines between netlify.toml tables

No rendered output changes: both builds were compared page by page (93 pages)
on visible text with whitespace preserved and on <pre> content verbatim,
with zero differences. The comparison was confirmed to flag a single dropped
space when one was planted.

• upgrade all dependencies to latest via ncu -u, with a clean reinstall

(node_modules and package-lock.json regenerated)

• notable majors: @astrojs/mdx 8, vite-plugin-pwa 2, vitest 5,

prettier-plugin-astro 1, prettier-plugin-toml 4, netlify-cli 27

• keep typescript at 6.0.3: 7.0.2 is outside the peer ranges of

@astrojs/check (^5 || ^6) and typescript-eslint (<6.1.0), so npm install
fails with ERESOLVE; forcing it would run astro check and lint on an
unsupported compiler

• override toml to ^5.0.1: netlify-cli 27 still pins toml 4.3.0 (three

high-severity parse DoS advisories). 5.0.1 is patched, and netlify-cli's own
zip-it-and-ship-it already uses it with the same default-import API. npm
audit's suggested fix downgraded netlify-cli to 5.3.1.

Verified: npm audit reports 0 vulnerabilities; astro check, eslint, knip,
and 567 tests pass; production build succeeds and the generated service
worker still precaches offline/index.html and binds the fallback to
/offline/index.html; dev server pages load with clean consoles.

Local Node 24.2.0 is below the ^24.16.0 engine range of the new
eslint-plugin-astro/astro-eslint-parser (EBADENGINE warning only).

The torch stored burns as viewport cells and cleared all of them on any DOM
mutation in the 404 article, on scroll, and on sidebar collapse. Every
text-effect tick (typewriter, glitch shimmer, ASCII dice) therefore wiped
burns across the whole page, not just the characters it changed.

• add burn404flammable.ts: flammable ink and burn memory are stored per

anchor (nearest h1-h6/p/pre/li/a/hr) relative to its origin cell, with
origins read each frame so burns travel with their text

• re-detect only the anchors a mutation touched; a full re-detect runs only

for structural changes, resize, and sidebar toggles

• mask burn memory by current ink: a removed glyph stops burning and

re-ignites when ink returns to that spot

• drop an anchor's burns only when a full re-detect finds its width changed

(glyphs reflowed); anchors with no ink right now keep their memory

• remove the scroll listener; guard queued detection with a generation

counter; grow burn sets in place and skip off-screen anchors per frame

• fix soft navigation back to the 404 (pre-existing): both burn404 canvases

kept stale _fireW, so the new canvas stayed at the 300x150 default, and the
mutation observer stayed bound to the detached article

Verified in the browser at 1280x900 and 390x844: a burnt heading holds
~760 lit cells for 12s of typewriter and glitch activity (previously 0
after ~8s), follows scroll, survives typewriter backspace/retype, and both
canvases size correctly after two 404 -> /blog -> back round trips.

Every text effect indexed strings by UTF-16 code unit (split(""), text[i],
slice(0, i)). The typewriter therefore painted half of a surrogate pair for
one tick, so "...set the page on fire 🔥" on the 404 page flashed U+FFFD
before the emoji settled. The same latent bug existed in every other effect
and in charset pickers given emoji items.

• add splitGraphemes() (Intl.Segmenter, Array.from fallback) and

pickRandomGrapheme() to textEffects/utils

• route all 14 renderers, renderTypingFrame, and charset/items pickers

through grapheme arrays; ASCII behavior is unchanged

• add a renderer sweep test that records every textContent write for text

with a surrogate pair and a ZWJ sequence and asserts no frame splits one

Verified in the browser: sampling the 404 typewriter every 40ms across a
full cycle shows no lone surrogates (previously "\ud83d█" was observed).

• docs/sps-operator-controls:

docs(sps): update SPS policies for operator-controls launch

Describe live status notices and operator-enabled feedback, control,
review, and export instead of a not-yet-operational interface. Add the
implemented retention schedule, storage protections (per-user ACLs,
DPAPI for the bot token and action payloads), export, correction, and
scoped erasure procedures, and a reviews-and-acceptance section in the
terms.

• docs/sps-policy-language:

docs(sps): use neutral policy voice in SPS terms and privacy

Replaces first-person wording with defined roles: "the operator"
(the person who runs SPS) and "authorized users" (people allowed to
use the Discord interface). Storage location now reads as the computer
where SPS runs. No change to what the pages commit to.

• feature/sps-policy-pages:

feat(sps): add Self Prompting System terms and privacy pages
chore(icons): add policy icons to icomoon set

Adds /sps/terms/ and /sps/privacy/ for the private SPS Discord
application, cross-linked and indexed. Both state that the Discord
interface is planned and not yet operational, and describe intended
data handling without claiming unestablished storage, retention or
provider guarantees.

The website privacy page gains a scoping line linking the separate
SPS policy; existing website and guestbook commitments are unchanged.
/sps redirects (302) to /sps/terms/ because the header breadcrumb
links that segment.

Adds exclamation-triangle, robot, person-check, clock-history, hdd,
database and file-earmark-text, and updates the font cache-bust token
in the Layout preload. Keeps woff ahead of ttf in the @font-face src
list so the preloaded woff is the file browsers use.

• feat/motif-attachments:

feat(motifs): add waving-hand creature and granular Haunted glow/creature toggles

• Register a multi-tone waving-hand SVG in the shared adornments registry

and wire it to the hello page's "Hello." header via data-magical-text

• Add disableGlow and disableCreatures to Haunted, independent of

disableFun, exposed through both the component props and the
data-haunted-* attributes

• Fix MagicalText re-inserting captured markup via textContent instead of

innerHTML, which rendered raw tag syntax for elements with child markup
(e.g. an icon) instead of parsing it

• Wrap GuestbookEntry bubbles in Haunted (heart creature, glow disabled)

and scope the guestbook content-stacking CSS rule to .haunted-content so
it doesn't fight Haunted's creature overlay

• Add typewriter, glitch, and signal-loss text effects to the 404 page

headings

• fix/pwa-offline-fallback:

fix(pwa): align offline fallback with precache

Point the production Workbox navigation fallback at the generated offline/index.html document while retaining the clean /offline route in development.

Add an Astro 7 contract test that prevents the production and development fallback paths from drifting back together.

• fix/header-cursor-spacing:

fix(header): refine cursor and greeting scale

• feat/sidebar-active-route:

feat(sidebar): add Workbench nav selection states

• fix/pwa-production-dependency:

fix(pwa): install build plugin in production

• update:

build(astro): complete v7 compliance migration
build: upgrade Astro stack and preserve PWA
fix: honor manual theme toggle for dark Shiki code blocks

Upgrade Astro, lint, formatting, and supporting packages while adapting changed parser, OpenGraph, Tailwind, and TypeScript contracts.

• replace the Astro-6-only PWA adapter with a tested Astro 7 lifecycle bridge


• preserve manifest, offline fallback, precache, runtime-cache, and Netlify service-worker output


• remove obsolete CollapsibleNav and MagicalText compatibility code


• regenerate the lockfile without legacy peer overrides

Dark code-block colors were gated behind @media (prefers-color-scheme:
dark), so they only applied when the OS preference also happened to be
dark. Since theme is driven entirely by the html[data-theme] attribute,
this left code blocks stuck on the light Shiki theme whenever the site
was toggled dark but the OS/browser preference was light.

• update/colors:

upate site greeting font
feat(theme): add observatory flavor, rework color system to dark-first

theme.css:

• Flip default @theme from light-first to dark-first; light now lives

under the [data-theme="light"] override

• Add "observatory" flavor (deep-space indigo, nebula violet, gold

starlight) for both dark and light

• Decouple --color-link from --color-warning to --color-primary


• Add --text-display/--font-display (uni0553) for hero/greeting moments


• Reduce heading font-weight 800 -> 700; retune flavor hue/chroma values

Consumers (design-tokens.ts is a manual snapshot for /palette - runtime
colors come from CSS vars, but the doc copy had drifted):

• Resync colorValues, hexColorValues, and all 7 existing themeFlavors

entries in design-tokens.ts to the new theme.css values

• Wire "observatory" into flavorManager, transitionRegistry (ripple

transition), musicPlayer flavor mapping, asciiVisualizer theme,
burn404palettes fire stops, and navBrand command-palette targets

• Extend transitionRegistry/burn404palettes/musicPlayer/navBrandCommands

tests for observatory coverage

Verification: npm run check (0 errors), npm run lint (clean), vitest
524/524 passing across 30 files.

• fix/8biticon:

fix: remove redundant DOMContentLoaded guards causing double init on page load

astro:page-load fires on initial load and every subsequent soft navigation,
making the readyState/DOMContentLoaded guard pattern redundant. Having both
caused init functions to run twice on first visit, stacking duplicate event
listeners on buttons, scroll handlers, and keyboard shortcuts.

Affected: AvatarGenerator, BackToTop, CollapsibleNav, FloatingSearch,
SearchField, TerminalModal, SocialShareButtons, Layout (scroll progress),
resume (PDF viewer), terminalModal.ts

• updates:

refactor(music-player): revert ASCII visualizer to linear frequency mapping
fix(music-player): close partially-created AudioContext on connect() failure
perf(music-player): harden and optimize ASCII visualizer

Replace log-spaced bin ranges with simple equal-width binsPerCol averaging.
Log mapping gave low frequencies extra visual space, making the display
bass-forward. Linear slicing keeps each column balanced across the spectrum.

• Fix isPlaying tracking: set flag before reduced-motion early return so

motion listener correctly resumes active bars vs idle diamonds

• Harden motion listener: explicitly stop the opposite loop when toggling

reduced-motion on/off to prevent double-running RAF and setInterval

• Guard RAF startup: skip active mode if AudioContext setup failed,

avoiding a wasted RAF loop that would just re-render idle

• Fix AudioContext resume: use void + .catch(() => {}) to silence

unhandled rejection noise if browser refuses resume

• Log-spaced bin ranges: precompute {start,end} per column once in

connect() instead of calling Math.exp() every frame

• Include bin 0 in column 0 for fuller sub-bass representation


• Peak decay: previousHeights buffer smooths bar falloff (VU-meter feel)


• DOM write cache: skip textContent/color/shadow writes when unchanged


• Immediate idle repaint on setFlavor() when not in active mode


• Reduced-motion live listener: react to OS setting without page reload


• Reset isPlaying and logBinRanges in teardown() for full state hygiene

• updates:

feat(music-player): add real-time ASCII audio visualizer

Replaces the static AsciiWidget placeholder in the music player's right
panel with a live FFT-driven ASCII visualizer. Shows a scrolling diamond
idle pattern when paused and 32×12 frequency bars during playback.

• New AsciiVisualizerController class (src/lib/asciiVisualizer.ts):

pre-allocated span grid, Web Audio API AnalyserNode (fftSize=256),
lazy AudioContext init on first play, setInterval idle loop,
requestAnimationFrame active loop, prefers-reduced-motion support

• 8 flavor themes all derived from --player-ink / --player-bg CSS vars

so colors automatically track the active site flavor; per-flavor
personality via ramp width and glow radius; REDLINE uses a power-curve
ramp for extra punch at peaks

• Wired into musicPlayerModal.ts: connect+setPlaying on audio events,

setFlavor on theme change, teardown on cleanup/close

• CSS: removed .ascii-widget-* rules, added .music-ascii-visualizer

with bottom-alignment so the grid sits flush with the album art

• updates:

fix(a11y): resolve aria-hidden violations on focus in haunted and music player

Use parseCSSColor to convert oklch computed values to rgb channels before
building rgba() box-shadow strings in haunted/controller.ts, preventing
invalid keyframe values when --color-primary resolves to a modern color space.

Return focus to the music launcher trigger before hiding the music terminal
dialog (close and minimize actions) so aria-hidden is never set while a
descendant button retains focus.

• update/music-player:

fix(music-player): retain active playback queue when browsing albums

Music controls (next/prev/auto-advance) were routing to the browsed
album instead of the playing album, because renderTracks() replaced
playbackState.playlistTracks on every album open.

Separate browsing state (browsingPlaylist/browsingTracks) from playback
state. The active queue is only replaced in playTrackFromBrowse() when
the user explicitly plays a track, leaving controls anchored to the
playing album while the user browses freely.

• update/effects:

feat(effects): add creatureColors prop to Haunted with round-robin distribution
feat(effects): extend components with arbitrary tag and attribute forwarding
refactor(effects): centralize effect registries in Layout.astro
fix(effects): re-resolve theme CSS vars on flavor-change

Accept an array of CSS colors on the Haunted component/data-attribute API.
Colors are distributed across the N creatures in round-robin order. Defaults
to --color-primary from the active theme and re-resolves on flavor-change.
Has no effect on creatures with hardcoded SVG fills (ghost, ghost-alt).

• MagicalText and Haunted now accept a tag prop (sup, i, b, em, strong, a, etc.)

and forward any unknown HTML attributes (role, tabindex, aria-*, data-*) to the
root element via ...rest spread, enabling use as interactive elements

• Fix multi-path SVG color tracking: wrap sibling paths in <g data-sparkle-path>

so the single querySelector hit cascades fill to all children (fixes music-note
showing only the note head colored)

• Add north-star, music-note, and cassette adornments to the shared registry and

Haunted creature map

• Import magical-text.css and haunted.css via global.css so data-attribute

standalone usage works without requiring a component import on the page

• Apply haunted (music-note creature) and magical-text (cassette adornment) effects

to the music player launcher on the home page

Move textEffectRegistry, magicalTextRegistry, and hauntedRegistry imports
from individual components (Header, Sidebar, MagicalText, Haunted) into
Layout.astro so all three effects work declaratively via data attributes
on any page without requiring per-page or per-component script imports.

MagicalText and Haunted were resolving --color-primary / --color-accent
once at mount time, so colors stayed stale when the user cycled flavors.
Both controllers now listen for the flavor-change document event and
re-resolve their defaults live; listeners are torn down with the rest of
cleanup. User-supplied colors and glow overrides are left untouched.

• update/text-effects:

feat(textEffects): add standalone typewriter effect
feat(textEffects): add standalone glitch effect
refactor(textEffects): rename GlitchEffectOptions and glitchOptions to GlitchLockOnEffectOptions and glitchLockOnOptions
feat(textEffects): overhaul standalone effects with restore, delay, items options

Implements a full typewriter renderer with:

• Character-by-character typing with configurable delay and stutter


• Cursor blinking via visibility toggling (no layout shift in grid/flex/centered contexts)


• Cycle mode: loops through pipe-separated strings, backspacing between items


• Lead-in delay: blinks cursor before typing starts (matches reference behavior)


• Existing text + cycle: types element content first, then cycles through items


• Empty element support: cycle plays even when element has no prior text


• DOM span wrapper with all: inherit; display: inline to preserve element styles


• WeakMap-based orphaned blink cleanup on retrigger

Two-phase renderer: Phase 1 progressively locks in characters from fully
randomised noise (left→right or right→left with reverse); Phase 2 runs a
persistent post-settle shimmer that randomly corrupts and restores a single
character on a random timer until cancel() is called.

Options: charset, items (overrides charset), reverse, delayMs, count (extra
noise frames before reveal), shimmerIntervalMs, shimmer (disable post-settle
loop). All options are wired through the full declarative pipeline —
dataset attributes, config parser, triggers, transition — and exposed via
the registry under data-text-effect="glitch".

Disambiguates the glitch-lock-on effect's types and option keys from the
upcoming standalone glitch effect, which would otherwise collide on the
same names across types, config, transition, triggers, and registry.

• update/text-effects:

feat(effects): wire MagicalText and Haunted defaults to active theme tokens

Add resolveThemeCSSVar() to shared/colorUtils that resolves a CSS custom
property to a concrete rgb() string via a short-lived probe element, making
it compatible with the existing parseCSSColor pipeline.

MagicalText now defaults gradient colors to --color-primary and --color-accent
instead of the static 'darkorange'/'purple' pair. Haunted glow now defaults to
--color-primary instead of hardcoded red. Both remain fully overridable via
their existing options interfaces.

• update/text-effects:

feat(haunted): add Haunted container with creature fly-out and glow effects
feat(magicalText): add hsl/oklch color support; tighten barrel exports
feat(magicalText): add MagicalText gradient-sweep text with sparkle adornments
feat(textEffects): add 6 standalone rare effects (glitch, censor, uncensor, scramble, slow-reveal, shuffle)
feat(textEffects): improve and rename text effect system
refactor(textEffects): split terminalTextEffect.ts into focused modules

Implements the Haunted component — a container that emits flying SVG
creatures and pulses with a box-shadow glow on hover.

Refactor: extract shared/colorUtils and shared/adornments from
magicalText/ so both MagicalText and Haunted draw from a single source
of truth. colorUtils.ts re-export shim removed (no consumers).

New files:
src/lib/shared/colorUtils.ts — RGBColor, color parsers, multiColorFade
src/lib/shared/adornments.ts — AdornmentKind, AnimationType, ADORNMENTS, SVG strings
src/lib/haunted/types.ts — CreatureKind, HauntedOptions
src/lib/haunted/creatures.ts — CREATURES registry (SVGs from shared/adornments)
src/lib/haunted/controller.ts — bindHaunted() via Web Animations API
src/lib/haunted/index.ts — barrel export
src/styles/components/haunted.css — base positioning styles
src/scripts/hauntedRegistry.ts — declarative data-attribute registry
src/components/Haunted.astro — typed Astro component

colorUtils.ts:

• Add hslStringToRgb — handles hsl()/hsla(), comma and space syntax, deg suffix


• Add oklchStringToRgb — full OKLCH→OKLab→linear sRGB→gamma pipeline (Ottosson 2020)


• Add JSDoc to hexToRgb, rgbStringToRgb, hue2rgb


• Both parsers sit before the canvas fallback, so they work without a DOM

index.ts: remove ADORNMENTS, parseCSSColor, multiColorFade from barrel
(internal utilities consumed directly by controller.ts; not part of public API)

magicalTextRegistry.ts, MagicalText.astro: import through barrel instead of sub-modules
(fixes knip "Unused files" report on index.ts)

Provides two integration paths that share the same core engine:

Astro component:
<MagicalText text="Hello" colors={['hotpink','purple']} adornment="heart" />

Declarative data-attribute path (works on any element):
<span data-magical-text data-magical-text-colors="hotpink,purple">Hello</span>

Core (src/lib/magicalText/):

• colorUtils.ts — parseCSSColor (hex/rgb/named) + multiColorFade (200-step table)


• adornments.ts — four inline SVG adornments with authoring docs for adding more


• controller.ts — bindMagicalText() mounts gradient + rAF sparkle lifecycle


• types.ts — AdornmentKind, AnimationType, MagicalTextOptions

CSS (src/styles/components/magical-text.css):

• Gradient sweep via @keyframes (background-position 0% → -200%)


• Sparkle scale+rotate (@keyframes magical-text-sparkle)


• Scale-only variant (@keyframes magical-text-scale)


• prefers-reduced-motion: gradient freezes, adornments hidden

Adornments: star, heart (gradient color-tracked via rAF); ghost, ghost-alt (static fills)
Color tracking SparkleAnimator approach:
multiColorFade(colors, 200) builds a 200-step table; each frame maps sparkle X
position + current gradient offset to the matching table entry.

Astro navigation: astro:before-swap cancels all rAF loops; astro:page-load re-inits.

Adds 6 new role: "standalone" effects to the rare family, each with
typed option bags, HTML data attributes, and a dedicated renderer:

• glitch — per-frame intensity-based burst corruption, restores


• censor — fills chars L-to-R with block char, restores by default


• uncensor — starts fully censored, reveals chars L-to-R


• scramble — accumulates one random noise char per tick, restores


• slow-reveal — per-char slot-machine cycles before locking in L-to-R


• shuffle — Fisher-Yates anagram frame, restores

Architecture changes:

• resolveGlitchCharsetStr moved to utils.ts as a shared export;

glitchLockOn.ts now imports it rather than duplicating

• playTextEffect mode resolution extended: role: "standalone"

effects now correctly enter "standalone" mode (play + restore)

• glitch-lock-on data attributes renamed from glitch-* to

glitch-lock-* to free the glitch-* namespace for the new
standalone glitch burst effect

• All 6 new effects wired through config, transition, triggers,

and textEffectRegistry option bag passthrough

Drops the Terminal prefix throughout (TerminalTextEffect* → TextEffect*,
TERMINAL_TEXT_EFFECT* → TEXT_EFFECT*, terminalTextEffect.ts → textEffect.ts)
to reflect that these are generic text effects, not terminal-specific.

Also adds per-effect customisation options to typing, backspace, glitch-lock-on,
and signal-loss renderers — exposed via both the JS API and zero-JS data attributes:

Typing / backspace:
data-text-effect-typing-cursor-char, -cursor-blink-ms, -end-blink-count,
-lead-in-ms, -stutter-chance, -stutter-max-ms

Glitch-lock-on:
data-text-effect-glitch-charset ("blocks" | "letters" | "binary" | custom),
-reverse (right-to-left lock-in), -frames, -intensity

Signal-loss:
data-text-effect-signal-dropout-char, -blackout-ms, -false-recovery

All defaults preserved; zero breaking changes. 0 type errors, 506/506 tests passing.

1368-line monolith split into types, constants, utils, config,
activeEffects, transition, triggers, and effects/* per the module
dependency DAG. Barrel re-exports preserve the full public API.
No logic changes.

• update/404-burn-page:

fix(burn404): skip resize on height-only changes (mobile chrome toggle)

Root cause: _canvas.width = X always clears the canvas bitmap, even when
the value changes only slightly. Mobile browser chrome show/hide triggers a
resize event that changes only window.innerHeight (width stays constant),
which caused both canvases to clear and restart the fire animation on every
scroll-then-stop cycle.

Fix: return early in resizeCanvas / resizeTorchCanvas when newFireW ===
_fireW (width unchanged). Height-only events are chrome toggles — the
canvas keeps its current size, anchored at bottom: 0 / top: 0, with no
bitmap disruption. Width changes (device rotation, desktop resize) still
trigger a full update with buffer state copied across dimensions.

• update/404-burn-page:

fix(burn404): preserve fire buffer on resize and extend detection overflow

Both canvases were reinitializing their fire buffers completely on every
resize event. Mobile browser chrome show/hide changes window.innerHeight
by ~60px during scroll, which always produced a different cell count and
bypassed the existing dimension guard, causing the fire to visually restart.

Buffer preservation: copy existing cells into the new buffer on resize,
clamping to the overlapping region. The source row is always restored at
full intensity for the bottom strip. Burning torch pixels outside the new
bounds are dropped; the rest are retained.

Detection overflow: increase DETECT_OVERFLOW from 8px to 64px and extend
all three visibility checks to canvasH + DETECT_OVERFLOW. On screens where
the 404 page is marginally taller than the viewport (e.g. 2560x1440), the
final content section was past canvasH and got silently skipped. The extra
64px means content up to one screen-cell below the fold is still detected
and mapped to the last fire row.

• update/404-burn-page:

fix(burn404): debounce resize and skip reinit when dimensions unchanged
fix(burn404): fill all text glyphs and re-detect on sidebar toggle

On mobile, the browser chrome slides in/out during scroll, firing resize
events that called resizeCanvas() and reset _buf via initFire() — making
the bottom fire strip visually restart after every scroll stop.

Two-layer fix:
1. resizeCanvas() now checks whether the cell grid (fireW × fireH) actually
changed before reinitialising _buf. If only the CSS display size changed
(browser chrome height delta within a cell boundary), the running fire
state is preserved.
2. onResize() debounces the resize handler by 250 ms so the buffer only
reinitialises once the user has fully stopped resizing, not mid-scroll.

Two fixes:

1. Text visible through flames on large screens — caused by strokeText-only
detection for large text (≥24 px): only outline pixels were flammable so
character interiors never entered _burningPixels and showed through the
fire overlay. Removed the useStroke distinction; all text now uses fillText
so every glyph pixel is marked flammable and fully covered when burnt.

2. Sidebar collapse/expand shifts page content — main content re-centres
when the sidebar collapses, making previously detected flammable coords
stale. Added _sidebarObserver (MutationObserver on document.documentElement
attributeFilter: data-sidebar-collapsed) that triggers redetectAfterChange()
after a 300 ms delay to let the CSS transition complete before re-sampling
element positions. Started in enableTorch(), stopped in disableTorch().

• update/404-burn-page:

fix(burn404): accurate glyph detection, mutation re-scan, and deferred init

Three flammable-detection bugs fixed:

1. Descenders ('y', 'g') not igniting — baseline was r.top + r.height * 0.8
which ignores line-gap; corrected to r.top + (r.height - fontSize)/2 +
fontSize * 0.8. Extended detection canvas by DETECT_OVERFLOW (8 px) and
clamped fy so viewport-bottom descenders map to the last fire row instead
of being silently discarded.

2. Neofetch widget ASCII art randomization — added MutationObserver on
[data-page-404] (childList + subtree, 150 ms debounce). On DOM change:
clears _burningPixels and re-runs detection after document.fonts.ready so
new art positions replace stale flammable coords.

3. Post-navigation / reload timing — initTorch() now defers
detectFlammablePixels() behind document.fonts.ready + 50 ms timeout.
This prevents Range.getClientRects() from sampling intermediate positions
during Astro view transitions and back-navigation.

• feature/404-burn-page:

feat(burn404): icon-fire, default-on, granular ignition, and privacy updates
feat(burn404): theme-aware palettes and graceful extinguish animation
fix(burn404torch): canvas pixel-scan detection + scroll extinguishing
feat(burn404): add full-viewport torch with flammable text detection
chore(burn404): cap source intensity at 33 to reduce white at flame base
fix(burn404): remove stacking context override that broke sidebar layout
fix(burn404): cancel RAF and clear active attr on non-404 navigation
feat(burn404): add data-page-404 sentinel and reduced-motion gradient to 404 page
docs(privacy): disclose flourish-burn404 localStorage key (12 total)
feat(burn404): wire burn404 script into Sidebar flourish block
feat(burn404): add canvas positioning CSS and reduced-motion fallback
feat(burn404): implement Doom-fire engine and lifecycle manager
feat(prefs): add burn404 localStorage key

• Use icon-fire for the Burn 404 sidebar toggle (was icon-stars)


• Flip default: burn404 is ON by default; storage key "0" = disabled,

absent = enabled. Updated isActive() in both burn404.ts and
burn404torch.ts, toggle handler, prefs.ts comment, privacy.astro,
and dnt-policy.txt to reflect the new semantics.

• Replace bounding-rect flammable detection with glyph-pixel accuracy:

large text (≥24px) uses strokeText so fire traces letter outlines;
small text uses fillText; short nodes (≤200 chars) render
character-by-character via Range for ASCII art glyph granularity;
long nodes fall back to line-level for performance.

• Split ignition radius from visual fire radius: TORCH_IGNITION_RADIUS=2

(tight contact zone) vs TORCH_FIRE_RADIUS=8 (visual flame spread),
so fire only permanently lights pixels directly under the torch tip.

• icomoon font updated with icon-fire glyph.

• Add burn404palettes.ts with 16 color-stop presets (8 dark + 8 light)

covering all flavors: dark, crt-green, amber, synthwave, dos, void, ice,
redline. First two stops are always transparent to prevent cold-cell
overlay on light backgrounds.

• buildPalette() interpolates stops via canvas linear gradient into the

37-step RGBA palette used by the Doom-fire renderer.

• getActiveColorStops() reads data-theme / data-flavor from the DOM so

the fire instantly reflects the active theme and flavor in both modes.

• rebuildPalette() wired to set-theme and flavor-change events so color

updates are live without a page reload.

• disable() now sets _extinguishing=true when the RAF loop is running;

updateFire() decays the source row naturally until the buffer hits zero,
then cleans up — producing a gradual burn-out instead of a hard cut.

• Torch mirrors the same extinguish pattern via _torchExtinguishing and

listens to BURN404_PREF_CHANGE so both canvases fade out together.

• Tests cover FIRE_COLOR_STOPS structure invariants and SSR fallback paths.

Detection now mirrors the 404-fire-page reference approach:

• Creates an offscreen canvas at viewport resolution (fireW*pixelSize × fireH*pixelSize)


• Paints all visible leaf elements (no child elements) by bounding rect, covering

icons <i>, <hr>, <pre> ASCII art, inline spans, links, and any other non-container
visible content — not just text nodes

• Also overlays text node Range.getClientRects() rects for per-line accuracy inside

compound elements

• Pixel-scans the result: any white pixel → flammable fire-buffer cell

Scroll extinguishing:

• On scroll: _burningPixels cleared immediately (fire decays naturally)


• 200ms after scroll stops: detectFlammablePixels() re-runs so coordinates stay

aligned with the new viewport position

• _scrollTimer cleared in disableTorch() to prevent ghost re-detection

Adds a second fire layer (#burn404-torch) that covers the full viewport.
Mouse/touch position injects Doom-fire at the cursor with a circular radius
and quadratic falloff. Text content on the 404 page is detected as
"flammable" via Range.getClientRects() — cells touched by the cursor are
permanently ignited and held at max intensity each frame.

• burn404torch.ts: initTorchFire, updateTorchFire (9 tests), detectFlammablePixels

(DOM TreeWalker + Range rects → fire-buffer coordinates), full canvas
lifecycle with AbortController cleanup

• burn404.css: #burn404-torch full-viewport styles; cursor:none on main

when burn is active

• Sidebar.astro: import burn404torch alongside burn404


• Both layers share the flourish-burn404 preference key and astro lifecycle

MAX_INTENSITY (36) is pure white — setting the source row to SOURCE_INTENSITY
(33, palette index [255, 247, 127]) keeps the base amber-yellow without the
stark white strip.

The body > :not(#burn404-canvas) { position: relative; z-index: 2 } rule
had specificity 1,1,1, overriding Tailwind's .fixed class (0,1,0) and
un-fixing the sidebar from the viewport. The sidebar fell into normal flow,
pushing all content down and breaking the layout.

Removed the rule. The sidebar's own z-40 (z-index: 40) keeps it above the
canvas (z-index: 1) naturally. Content in normal flow sits below the fixed
canvas — fire overlays the content at the bottom, sidebar stays above it.

When pref is enabled and the user navigates away from the 404 page,
enable() was leaving the RAF loop running on a detached canvas and
setting data-burn404-active on non-404 pages, which triggered the
z-index stacking context CSS site-wide with no canvas present.

Fix: call stopAnimation() first in enable(), then guard the attribute
set and canvas creation behind isOn404Page() — attribute is now only
set when fire is actually rendered, and the RAF is always cancelled
before re-evaluating whether to start it.

• fix/music-active-row-text-color:

fix(music): preserve active row inverse text color

Ensure active and playing music rows keep their inverse text color even
when nested text elements match the global typography color rule.

- apply player inverse color to text descendants inside active and playing rows

• fix/music-scrollbar-resize-overlap:

fix(music): reduce right resize handle overlap

Narrow the music dialog right-edge resize handle so it remains available
without blocking normal scrollbar interaction in the scrollable body.

- keep the left resize edge at the larger hit target
- reduce the right resize hit area to avoid competing with the scrollbar

• feat/theme-scrollbars:

feat(theme): add site-wide terminal scrollbars

Add a global themed scrollbar skin that matches the terminal visual
system and inherits from the active theme flavor.

- add reusable scrollbar color tokens in theme.css
- style WebKit scrollbars with square thumbs, transparent tracks, and primary-colored borders
- keep Firefox scrollbar colors scoped to its supported properties
- remove component-level scrollbar overrides so global styling applies consistently
- scope music player scrollbar tokens to the player theme so local flavor changes do not affect the rest of the site

• fix/misc:

build(astro): update Astro 6.4 and fix music player layout

Update Astro and related packages to the 6.4 line, including the MDX,
Netlify, sitemap, Shiki, lint, and test toolchain bumps captured in the
lockfile.

- move Markdown remark/rehype configuration into unified() for Astro 6.4
- add @astrojs/markdown-remark as a direct dependency for the config import
- remove stale vite-plugin-pwa from Knip ignored dependencies
- let the expanded music dialog scale on large desktop viewports
- fix playlist expansion so the panel grows with long track lists
- keep music controls and active playlist headers sticky while scrolling
- place terminal/music dock chips correctly below the desktop sidebar breakpoint

• fix/misc:

fix(site): align redirects and footnote navigation

Update PWA navigation fallback handling so Netlify vanity redirects for /why and /licensing are
allowed through to the network, and remove the obsolete /resume redirect now that /resume is a
real page.

Improve blog footnote back-navigation by keeping the TOC hidden during return jumps and adding
extra scroll margin for inline footnote reference targets so the source line stays visible.

Stabilize admin auth missing-env tests by explicitly stubbing ADMIN_TOKEN_HASH as undefined
instead of restoring the real shell environment.

Verification:

- npx vitest run src/lib/api/tests/admin-auth.test.ts
- npm test
- npm run check
- npm run lint

• docs-admin-argon2-auth-post:

blog(auth): add Argon2id security blog post pair

Add two linked security posts around the guestbook admin auth migration:

- add a standalone Argon2id/password-security explainer covering fast hashes,
memory hardness, storage format, tuning, and practical defaults
- add the guestbook migration write-up covering raw token removal,
Argon2-backed verification, signed sessions, query-token removal,
deployment notes, and test coverage
- add blog artwork for both posts
- normalize the admin token hash helper script file mode

• feature/sidebar-keyboard-shortcut:

feat(sidebar): add global collapse shortcut

Add a global Cmd+. / Ctrl+. shortcut for toggling the desktop sidebar
through the existing sidebar collapse state path.

- expose tested shortcut matching and platform-aware shortcut labels
- wire the shortcut into the sidebar collapse controller
- update the collapse tab accessible label, title, and aria-keyshortcuts
- keep shortcut handling inactive inside editable controls

• feature/admin-token-generator:

feat(admin): add interactive token generation

Extend the admin token hash helper so operators can generate a raw token and Argon2id hash in one command.

- add --generate mode for explicit raw token creation
- let blank interactive input generate a token and print storage guidance
- document npm-based generation and local dotenv escaping
- cover generated-token paths in the script tests

Verification:

• npm test -- src/lib/api/tests/hash-admin-token-script.test.ts

• feature/admin-token-hash-auth:

[feature] migrate: admin guestbook auth to argon2 hash

Replace raw ADMIN_TOKEN authentication with ADMIN_TOKEN_HASH-backed
Argon2 verification for the admin guestbook flow.

- verify raw bearer/login tokens with @node-rs/argon2
- remove query-string token upgrade support
- replace raw-token cookies with signed admin session cookies
- add a production-safe admin token hash helper script
- document .env variable escaping and deployment migration steps
- update auth and middleware tests for valid, invalid, missing, and query-token cases

• feature/music-page:

feat(music): add floating Navidrome player

Add a shared floating music player backed by same-origin Astro API routes that proxy Navidrome/Subsonic requests without exposing
credentials to the browser.

- add server-only Navidrome helpers, media proxy routes, and typed environment keys
- add pure playback queue helpers with coverage for shuffle, repeat, and navigation behavior
- add the persisted player shell, client interaction module, responsive dialog styling, default art, and dock stacking support
- add music navigation triggers and regenerate IcoMoon assets for the new player controls

• chore/updates:

refactor(ui): align interface utility usage

Apply the shared button utility stack to the guestbook entry actions trigger
and remove duplicated local trigger chrome from the guestbook stylesheet.

- add ordered-list coverage to the style guide prose specimen
- update style guide button personality specimens to the primary variant
- adjust the home Hello action color and add a bug icon on the Hello page

• fix/miscellaneous-issues:

fix(layout): align offline assets and content footnotes

Fix two miscellaneous production issues affecting content pages and
offline-capable asset handling.

- allow Workbox asset rules to match image/font/script URLs with query strings
- ignore Netlify dpl deploy query params during precache lookup
- prevent queried static assets from falling through to the offline page
- align MDX footnotes with the active sidebar width when the rail collapses
- animate footnote width and padding with the same sidebar timing

• fix/theme-url-flavor-param:

fix(theme): support URL theme and flavor overrides

Add URL-driven appearance handling for theme and flavor while preserving
manual theme switching after a URL theme has been applied.

- apply ?theme=light|dark before paint without persisting it
- apply ?flavor=<id> before paint and persist explicit flavor selections
- retain stored/current flavor when a later URL only provides ?theme=
- keep shareable URLs intact when users toggle theme manually
- preserve match-device behavior when no URL theme override exists
- add regression tests for URL theme toggles and flavor retention

Verification:
- npx vitest run src/scripts/tests/themeManager.test.ts

• feature/style-guide-page:

feat(style): add personal style guide page

Add /style as a writing-first field manual for alexmbugua.me, with
editorial voice rules, title conventions, formatting guidance, technical
writing standards, rule-breaking notes, and before/after examples.

- document supporting interface specimens for tokens, type, prose, links,
badges, buttons, forms, controls, cards, and terminal accents
- add the Style route to Explore navigation
- update the IcoMoon font build with the style-page icon set
- update the IcoMoon preload cache key in the shared layout

• chore/palette-theme-flavors:

feat(palette): document theme flavor tokens

Expand the design token registry so the palette page reflects the current
light, dark, and flavor-aware color system.

- add semantic color roles, base theme OKLCH values, and all theme flavor token sets
- add a palette Flavors tab with dark/light token grids and copyable OKLCH values
- update email and console consumers to use current semantic token mappings
- resolve console colors from live CSS variables so active flavors affect the console egg
- add the flask-florence icon to IcoMoon and update the font preload cache key

• update/blog-content:

update(content[blog]): add one about being brave enough to begin

• fix/avatar-exploratory-state:

fix(avatar): discard unsaved exploratory state

Keep avatar edits exploratory until the user explicitly saves or opts in
through guestbook avatar submission.

- initialize the full avatar generator from saved localStorage state or defaults
- prevent randomize, layer edits, and gender changes from rewriting the page URL
- build share URLs on demand from the current exploratory avatar
- reset mini avatar widgets to saved/default state when they initialize
- preserve guestbook opt-in as an explicit save path
- add focused coverage for saved/default initialization and exploratory edits

• fix/avatar-generator-responsive-layout:

fix(avatar): make generator layout fully responsive

Center the 8-bit avatar generator once the preview and selection areas
collapse into a single column, so the picker no longer sits left-aligned
during intermediate viewport widths.

- constrain preview and selection sections to the same stacked width
- center the selection section and layer picker in single-column layout
- keep desktop side-by-side layout and mobile picker height behavior intact
- preserve the updated avatar save/share action treatments

• fix/avatar-generator-responsive-selection:

fix(avatar): improve generator controls responsiveness

Refine the 8-bit avatar generator layout so the layer picker and preview
controls stay balanced across desktop and mobile views.

- make the layer tabs compact and shrink-wrapped when all tabs fit
- keep horizontal tab scrolling available only for narrow views
- preserve mobile picker height while increasing desktop selection height
- move save and share into icon actions below the avatar preview
- use primary-to-accent icon states for save/share hover and focus
- keep Randomize and Download as the main lower action buttons

• fix/mobile-terminal-neofetch-size:

fix(terminal): tune mobile neofetch text scale

Reduce the floating terminal's mobile neofetch/system output text so it no
longer appears larger than the init messages.

- size mobile system art and metadata rows to match the smaller status text
- reduce the system font label one step further for visual hierarchy
- keep regular terminal log, command, and init message sizing unchanged

Replace the flat share notification with a launch-stamp treatment that better
matches the site's retro-cosmic visual language.

- add a rocket sigil rail and compact stamped notification layout
- move notification-specific CSS out of global.css
- keep the existing framed error close button treatment
- show the dynamic copy message as muted supporting text
- rotate through common and rare static notification titles on display
- replace the plain slide animation with a clipped launch/depart motion

Verification:
- npm run test -- src/scripts/tests/feedbackManager.test.ts

Replace the custom share notification close-button styles with the existing
button classes so the control matches the site's framed error button treatment.

- apply shared btn, btn-frame, btn-error, and btn-xs classes to the close button
- switch the close icon to the larger x-lg glyph
- remove the old notification-only close-btn CSS

Keep nav-brand copy ownership inside the coordinator so hover, resume,
return, and terminal-context messages do not race through DOM mutations.

- drive greeting, teaser, and visit-count updates through the shared text
effect API
- respect each element's declared random-effect configuration when the
coordinator starts an effect
- keep hover/focus terminal affordances scoped to the teaser line
- delay return-to-active settling until the return greeting finishes
- gate terminal-specific sidebar greetings until the terminal is open or docked
- remove obsolete cursor and hint-state exports after the prompt cursor moved
into the typing effect

Verification:
- npm run test -- src/lib/tests/navBrandMessages.test.ts

Add lightweight utility interactions to the expanded sidebar nav-brand.

- copy the site email from the nav-brand identity line using the shared
clipboard/notification flow
- render the visit count after the shell prompt path with the shared typing
effect
- remove the redundant trailing underscore cursor and its cursor-mode styling

Add shared native-share-first behavior for site share surfaces while keeping
clipboard copy as the fallback.

- add shareOrCopyToClipboard to centralize Web Share API handling
- use native share for blog post, avatar, and guestbook entry share actions
- keep copy-only guestbook actions on the existing clipboard path
- center the blog share label and icon row without breaking mobile wrapping
- treat native share cancellation as a no-op instead of copying unexpectedly
- cover native share success, cancellation, unavailable API, and fallback copy

Verification:
- npx vitest run src/scripts/tests/feedbackManager.test.ts

Keep headings visible when selecting entries from the sticky table of
contents.

- define the default anchor scroll offset as a layout token
- measure the rendered TOC height at runtime and publish it to the token
- use the token for heading scroll margins instead of a fixed value
- update the offset after details toggle and viewport resize events

Add Bluesky, Reddit, Mastodon, and LinkedIn targets to the content share
controls.

- use updated IcoMoon classes for the new platform icons
- refresh generated IcoMoon font assets and demo metadata
- update the Layout font preload hash to match the regenerated woff asset

Separate decorative atmosphere colors from structural surface tokens so
background texture, matrix rain, and guestbook card patterns remain legible
without brightening borders, cards, or base surfaces.

- adds per-theme and per-flavor ink roles for:
- atmosphere texture
- guestbook card patterns
- matrix rain glyphs
- updates topography masks in global and sidebar styles to use atmosphere ink
- updates matrix rendering to read the matrix rain token
- gives sidebar flavor swatches fixed representative colors
- moves guestbook browser card, preview, and swatch masks to guestbook pattern ink
- updates guestbook notification and entry-copy emails to recolor notecard SVGs with email-safe pattern ink
- isolates missing-pepper hash tests from local GUESTBOOK_HASH_PEPPER values

Updated terminal-window__body scanlines to be more visible and theme-aware

- Moved scanlines into terminal-window__body::before so they overlay the terminal body without affecting layout.
- Increased line visibility from the old very subtle 2% content mix to 9%.
- Used a 2px transparent / 2px line rhythm similar to your reference.
- Added a subtle secondary-color sweep so it feels integrated with the terminal theme.
- Raised log and prompt content above the overlay with z-index: 1.

Updated footnotes styling for better readability and aesthetics
- Add numbering styles to the <ol> inside .footnotes:

Redesign the terminal text effect engine from reveal-only playback into lifecycle-aware motion with effect metadata, paired enter/exit
families, standalone flourishes, cancellation, reduced-motion fallbacks, and declarative trigger coordination.

Add type, cipher, and rare signal families: typing/backspace, decrypt/entropy, and glitch-lock-on/signal-loss. Tune short/long text
pacing, terminal block cursor behavior, backspace realism, signal dropout holds, and rare signal visuals so they read differently from cipher
effects.

Add content-change, delayed route-enter settling, bind-time load delay support, hover replay guards, random-effect eligibility, and
registry-backed sidebar/header/terminal flourish wiring through data-text-effect attributes.

Move sidebar navbrand flourishes out of navBrand state policy and into declarative Sidebar.astro markup. Remove the navbrand-specific
effects adapter and transition-effect chooser so navBrand remains responsible for state, copy, cursor, and terminal nudges only.

Update tests for metadata, parser support, reduced motion, paired transitions, interruption restoration, rare signal behavior, content-
change, route-enter settling, sidebar declarative behavior, and navbrand state cleanup.

Promote changed stable text from enter-only reveal into full paired transitions so typing uses backspace first, decrypt uses entropy first, and rare lock-on effects can use signal-loss.

Wire navbrand through runTerminalTextTransition instead of reset-then-reveal so the previous greeting remains available for the exit phase.

Add rare-family motion metadata and renderers for glitch-lock-on and signal-loss while keeping rare effects opt-in through explicit data-text-effect declarations.

Expand header greeting and terminal atmosphere declarations with reversible type/cipher exit effects and preserve terminal atmosphere stable text with data-text-effect-stable-text.

Document the motion model: public effect names, internal families, lifecycle roles, standalone safety, stable text caching, and paired-transition inference.

Expand focused tests for rare metadata/parser support, paired full-transition promotion, rare transition playback, and navbrand paired-transition behavior.

Introduce effect metadata for terminal text effects, including family, lifecycle role, standalone eligibility, and reduced-motion strategy.

Add runTerminalTextTransition as the lifecycle-aware coordinator for enter-only, exit-only, standalone, and full text transitions.

Split playback into renderer functions for typing, backspace, decrypt, and entropy instead of continuing to expand the old branch-heavy playback path.

Centralize reduced-motion fallback behavior in the generic engine and add a neutral data-text-effect-stable-text cache while preserving data-greeting-target compatibility.

Decouple navbrand effect typing from hardcoded typing/decrypt values so the shared engine owns the generic effect vocabulary.

Expand terminal text effect tests for metadata, parser support, reduced motion, standalone backspace, backspace-to-typing transitions, cancellation restoration, entropy, and standalone-safe randomization.

Reordered the IcoMoon @font-face sources to prefer woff before ttf.

Diagnosis:
- Layout.astro preloads /fonts/icomoon/fonts/icomoon.woff?4weq0r.
- But icomoon/style.css declares ttf before woff in @font-face.
- So the browser could preload woff and then still choose ttf,
which triggers the "preloaded but not used" warning.

• feat/navbrand-redesign:

fix(navbrand): guard NaN corruption, negative elapsed, and sessionStorage exceptions
chore(privacy): document nav-brand-visits and nav-brand-last-visit keys
fix(navbrand): collapse hidden sub-row and increase max-height for expanded content
feat(navbrand): replace nav-brand-prompt CSS with shell prompt styles
feat(navbrand): update Sidebar.astro HTML structure
feat(navbrand): add DOM rendering and event listeners
feat(navbrand): add pure functions with unit tests
chore(prefs): add navBrandVisits and navBrandLastVisit keys

Replace badge-stack nav-brand with multi-line visitor-aware shell prompt
layout and wire up the navBrand script import.

Three tiers keyed to idle duration
— playful (0-10s), system (10-30s), cosmic (30s+)
— cycling every 8s via setInterval. Index resets on tier
transition. Timer clears on tab focus restore.

Added theme-flavor, theme-transition, and sidebar-collapsed to all
privacy disclosures. All three disclosure files now
consistently declare nine localStorage keys.

- src/pages/privacy.astro
- six to nine
- added three <li> entries
- src/components/PrivacyPolicy.astro
- five to nine
- updated prose
- public/.well-known/dnt-policy.txt
- six to nine
- three new bullets
- "contact us" to "contact me"
- reassertion date 2026-04-15

Update @vite-pwa/astro to pkg.pr.new/astro@73 (Astro 6 / Vite 6
compatibility pre-release) and add a custom pwa-sw-copy-to-dist
integration to bridge the build output mismatch.

Root cause: @astrojs/netlify v7 sets config.build.client to
.netlify/build/ (the SSR function directory). @vite-pwa/astro reads
this at config-setup time and writes sw.js + workbox-*.js there
instead of dist/ where Netlify serves static files.

The custom integration hooks into astro:build:done (runs after the
PWA integration) and copies sw.js and workbox-*.js from .netlify/build/
to dist/, falling back silently on local static builds where
.netlify/build/ is absent.

fix(pwa): set explicit globDirectory to suppress Workbox precache warnings

@astrojs/netlify v7 sets config.build.client to .netlify/build/ (the
SSR function bundle directory). @vite-pwa/astro picks this up as
globDirectory, finds no CSS/HTML/font assets there, and emits
"glob pattern doesn't match any files" warnings (leaving the precache
manifest empty).

Explicitly setting globDirectory to dist/ in the workbox config takes
precedence over the integration's auto-detected value, pointing Workbox
at the correct static output directory where all built assets live.

Implements a two-state collapsible sidebar for desktop (lg+).

Key design decisions:
- Sidebar width animation is the primary motion driver.
- All other elements follow its lead via CSS transitions and timing.
- Overflow switches to visible after the width animation completes
(transition: overflow 0s delay trick) so tooltip ::after pseudo-elements
can escape the panel once settled
- Nav-text uses opacity-only fade with a delayed max-width snap (no squish)
- Section labels, hidden sections, and footer are hidden via visibility:hidden
with no transition (the sidebar clip handles their visual disappearance)
- Header brand (prompt <> avatar) crossfades via opacity only
- Active item box-shadow removed in collapsed rail (too wide for 3.5rem)
- State persisted to localStorage and re-stamped on astro:after-swap to
survive Astro ClientRouter soft navigations
- Easter egg hidden instantly (display:none) to prevent flicker animation
playing during collapse
- Bookmark tab sits at z-39 (behind sidebar z-40) and slides out 14px on
hover via transform — no clip-path needed
- CSS-only tooltips (::after/::before) on nav-link[data-tooltip] in
collapsed mode, keyboard accessible
- Preference key: PREF_KEYS.sidebarCollapsed in lib/prefs.ts
- --sidebar-current-width CSS var drives both sidebar width and content
margin-left offset
- Desktop only, behavior unchanged on mobile

Files: Sidebar.astro, Layout.astro, sidebarCollapse.ts, sidebar.css,
prefs.ts, global.css, theme.css, icomoon (collapse/expand icons)

commit 361941368c9fa99c553cefde47c5284550c0ef6c
Author: asce1062 <tnkratos@gmail.com>
Date: Thu Apr 9 14:46:55 2026 +0300

chore(ctv2): misc adjustments

commit 320a1092796cb7283215f2c4bfad14ed6fa7a986
Author: asce1062 <tnkratos@gmail.com>
Date: Wed Apr 8 19:51:44 2026 +0300

feat(transitions): add switchFlavor - resolves effective style and calls atomicSwitch

commit 6ad6f423efa7ffc435fae9e565adb9d10de20b09
Author: asce1062 <tnkratos@gmail.com>
Date: Thu Apr 9 00:22:10 2026 +0300

feat(transitions): add transition pill styles to sidebar CSS

commit b4b20f466fe726378d2a9895b0c33bc9cf90ead2
Author: asce1062 <tnkratos@gmail.com>
Date: Thu Apr 9 00:05:12 2026 +0300

feat(transitions): implement scanline handler with CRT raster bands and halo beam

commit 31cf6cf9c0d6fd806d62f3acbe57e405167e0993
Author: asce1062 <tnkratos@gmail.com>
Date: Wed Apr 8 19:33:42 2026 +0300

feat(transitions): add transition manager - pref read/write and pill sync

commit c968445f7082624e68a60d032d1eba6575e70b79
Author: asce1062 <tnkratos@gmail.com>
Date: Wed Apr 8 19:58:55 2026 +0300

feat(transitions): pass context to atomicSwitch in handleThemeToggle

commit 3ad7b1a646113161eb0fbded9deeeb4e17b05235
Author: asce1062 <tnkratos@gmail.com>
Date: Wed Apr 8 19:45:54 2026 +0300

refactor(transitions): atomicSwitch dispatches to registry with cancel-and-replace guard

- Replace themeTransition.ts: atomicSwitch now accepts TransitionContext,
resolves style from stored pref, guards against terminal on init/soft-nav,
cancel-and-replaces any in-flight transition, dispatches to registry handler
- Add transitionState.ts: isolated cleanup-closure state to break circular dep
- Re-export registerTransitionCleanup from themeTransition for backward compat
- Deprecate initTransitionOverlay as a no-op stub (handlers own the overlay)
- Add "programmatic" to TransitionContext.source union in transitionRegistry

commit 5465dbf6f863817ebe280b6cc5e9c2d2cc3f179c
Author: asce1062 <tnkratos@gmail.com>
Date: Wed Apr 8 14:04:59 2026 +0300

feat(transitions): add transition registry - types, mapping, pure helpers, none handler

Introduces transitionRegistry.ts with:
- TransitionStyle union type and TRANSITION_STYLES constant
- FLAVOR_TRANSITION_MAP covering all 8 flavors
- getMappedTransitionForFlavor() and resolveEffectiveTransitionStyle() pure helpers
- TransitionContext interface and TransitionFn type
- Exported getOverlay/wait/clamp helpers for use by overlay-based transition handlers (scanline, phosphor, retune, etc.)
- Full transitionRegistry record with none handler + stubs for all 8 styles
- 13 tests covering map coverage, per-flavor lookups, and resolve priority

commit 8ace8afc5b3d523fc39825bb708e2c5d8381cbcd
Author: asce1062 <tnkratos@gmail.com>
Date: Wed Apr 8 13:57:03 2026 +0300

feat(transitions): add PREF_KEYS.transition preference key

commit b0fe9f572076beb80bafdf88bcd6b42ac80da525
Author: asce1062 <tnkratos@gmail.com>
Date: Mon Apr 6 23:15:43 2026 +0300

feat: 7-flavor optional theme system and dark/light overhaul

Add a flavor picker to the sidebar with 8 opt-in color overlays (default +
crt-green, amber, synthwave, dos, void, ice, redline). Each flavor overrides
OKLCH color tokens on html[data-theme="dark"][data-flavor="X"] for dark-mode-
native theming without touching light mode.

- theme.css: 7 flavor blocks (full OKLCH palette per flavor), boosted dark
base surface chroma (base-200/300 from 0.004→0.010/0.012 at hue 270),
semantic tokens (--color-heading, --color-link, --color-muted, --color-code-bg)
- global.css: split coupled h2+a rule into separate heading/link semantic tokens
- flavorManager.ts: flavor type, FLAVORS/LABELS/SWATCHES exports, setFlavor,
applyStoredFlavor, syncSwatches, initFlavorPicker with AbortController
- flavorPicker.ts: entry script wired to astro:after-swap + astro:page-load
- prefs.ts: add flavor key ("theme-flavor")
- Layout.astro: early-init is:inline script stamps data-flavor before paint
- Sidebar.astro: flavor section with 8 swatch buttons (data-flavor-btn)
- sidebar.css: .nav-flavor-picker/.nav-flavor-swatch styles with active glow

commit 5b9491ba74c5ce0a123d092593133ab5455b7945
Author: asce1062 <tnkratos@gmail.com>
Date: Mon Apr 6 22:50:10 2026 +0300

feat: semantic color tokens and warm void depth

- Add --color-heading/--color-link/--color-muted/--color-code-bg semantic tokens
to decouple h2 and link colors (previously both --color-warning = no hierarchy)
- Split h2, a { color: warning } into separate rules using semantic tokens:
h2 → --color-heading (amber, phosphor warmth)
a → --color-link (orange in light, coral in dark)
- Boost dark base surface chroma: base-200/300 from 0.004 to 0.010–0.012
at hue 270 to match base-100's purple ghost - surfaces now feel chromatic
- Strengthen dark mode glow tokens: active +4px, accent +4px, identity +8px
- Deploy --glow-accent to three surfaces: link-action hover, input focus,
layer tab active state

commit e3832a7de8215ce09b4e1ba5c5e54b04cf887ade
Author: asce1062 <tnkratos@gmail.com>
Date: Mon Apr 6 22:00:18 2026 +0300

fix: a11y, hardening, and greeting polish

- fix(404): add sr-only h1 to restore heading hierarchy (WCAG)
- fix(preview): replace shadow-xl with elevation token
- fix(avatar): layer tab icons visible (color: transparent → token)
- fix(avatar): add role=tablist/tab + aria-selected to LayerTabs
- fix(avatar): sync aria-selected on switchLayer + gender/ext changes
- fix(guestbook): AbortController cleanup for document-level listeners
- fix(guestbook): ArrowUp/Down keyboard nav for role=menu entry actions
- fix(guestbook): auto-focus first menuitem on open; borderRadius → 0rem
- fix(guestbook): expand entry-actions-trigger tap area to 44px (WCAG 2.5.5)
- fix(sidebar): expand nav-avatar-btn to 44px tap target
- fix(sidebar): most-specific active link match (no false /blog highlight)
- fix(search): center floating modal within content area on lg+ (sidebar offset)
- fix(greeting): inline-block constrains hover zone to text width only
- fix(greeting): period now scrambles in decrypt animation

commit 083be1a0b36aaa401d2d02eeb8d12bc96537af45
Author: asce1062 <tnkratos@gmail.com>
Date: Mon Apr 6 21:22:14 2026 +0300

chore: polish scope transitions and fix listener leaks

Scope transition-all → specific GPU-safe properties across components:
- Header, ThemeSwitcher, guestbook random btn: transition-[color,transform]
- ProjectCard link: transition-colors (color changes only)
- PreviewImage: transition-transform (scale only)
- BackToTop: transition-[opacity,transform,visibility] (fade + scale)
- scrollProgress: transition-[width] (only width changes)

Zero-radius: BackToTop rounded-full → rounded-none (UI control, not avatar)

scrollProgress: add AbortController so scroll listeners don't accumulate
across Astro soft navigations (same pattern as sidebarNav, FloatingSearch)

commit f8d1ab857d017927575e7a1a2743acc759645b77
Author: asce1062 <tnkratos@gmail.com>
Date: Mon Apr 6 21:14:16 2026 +0300

fix: harden FloatingSearch against listener accumulation

Memory leak: window/document event listeners (resize, scroll, orientationchange,
keydown x2) and ResizeObserver were never cleaned up between Astro soft
navigations, causing them to pile up on each astro:page-load reinit.

Fix: Add AbortController (_ac) and ResizeObserver ref (_ro) at module scope.
Each init tears down the previous set before registering new listeners -
identical pattern to sidebarNav.ts.

Also:
- Restore focus to the triggering element on modal close (accessibility)
- Replace setTimeout(fn, 100) focus call with requestAnimationFrame
- Scope transition-all → transition-opacity on modal div (GPU path only)

commit 88b7ce7be00be724f47f77b6e47081744e162cc3
Author: asce1062 <tnkratos@gmail.com>
Date: Mon Apr 6 21:08:59 2026 +0300

perf: optimize font loading and containment

Font loading:
- Add <link rel="preload"> for 0xProto-Regular, 0xProto-Bold, 0xProto-Italic,
and icomoon.woff before CSS is parsed - reduces FOUT window for body text
and nav icons

CSS containment:
- Add contain: layout style to .nav-menu (sidebar is a self-contained panel;
internal changes no longer trigger external layout recalculations)

Transition scope:
- AvatarGenerator layer items: transition:all 0.2s → specific border-color/box-shadow
- ContentCard link: transition-all duration-300 → transition-colors duration-200

commit abec107b6cfd0f374a2ff04bbea96ac87427f528
Author: asce1062 <tnkratos@gmail.com>
Date: Mon Apr 6 20:52:11 2026 +0300

chore: centralize and tokenize all transition/animation literals

Replace every hardcoded timing literal (0.1s–0.3s) and bare ease keyword
across the CSS system with motion design tokens. Scope broad transition: all
to specific properties for GPU-accelerated paths only.

Files updated:
- global.css, sidebar.css, collapsible-nav.css - dark-mode, nav, and chevron transitions
- btn.css, toggle.css - interaction feedback timings
- link-action.css - already committed in previous session
- input.css, checkbox.css - utility component transitions
- guestbook.css - entry bubble, swatch, actions trigger, action item
- search.css - pagefind clear button, result row, result link
- avatar.css - gender-option, layer-tabs, layer-tab (narrowed from transition:all)

Intentional exceptions kept as literals:
- asciiWidget.css: diceSpin 0.5s (one-shot effect)
- guestbook.css: entry-highlight 1.5s (narrative anchor animation)
- asciiReveal.css: art-scan, flicker sequences (effect timings)

commit 66b054482e3a1e8a4ba6d59813fb73a01bfc1c22
Author: asce1062 <tnkratos@gmail.com>
Date: Mon Apr 6 20:29:11 2026 +0300

chore: align with standards

- guestbook.css entry-bubble + textarea-wrapper border-radius
0.25rem → 0rem; defends zero-radius identity in guestbook UI
- global.css share-notification box-shadow → var(--elevation-3);
sidebar.css 800ms literal → var(--duration-crawl) var(--ease-out);
link-action.css 0.2s literals → var(--duration-base)
- meta.astro + guestbook.astro rounded-md/rounded-none;
all public pages now comply with zero-radius identity
- heading transition-all → transition: font-size var(--duration-instant)
on h1/h2/h3/.site-greeting; scoped to font-size only, not all properties

commit 4480359046d5e9bf1cfcab604255f4e633958ebe
Author: asce1062 <tnkratos@gmail.com>
Date: Sat Apr 4 22:32:40 2026 +0300

chore: update layout and language

- remove b{color:warning} from components layer.
- bold text in prose no longer inherits warning color
- remove h4 from warning color selector (h2,h4,a → h2,a);
- h4 is rarely used and warning color should be intentional, not default
- humanize sidebar option descriptions
- Avoid mechanical phrasing and jargon; now conversational
- aria labels updated from generic "Visit the X page"
- pattern to action-oriented descriptions (read, browse, sign, search)
- about.astro resume copy - "digital version of my resume
available here" → "My resume is available here"

commit f45d1d7688d0686b1738f3f9a7b47115f5cf758e
Author: asce1062 <tnkratos@gmail.com>
Date: Sat Apr 4 17:01:26 2026 +0300

feat: visual identity push

- faded-text gradient reduced from 5-stop rainbow to 2-stop
primary→accent (warm void palette only); references motion tokens
- add glow token vocabulary to theme.css - glow-active,
glow-accent, glow-identity
- apply glow-active to active nav link (inset coral wash);
apply glow-identity text-shadow to site greeting
- homepage exit section - Hello link-action upgraded to
link-action--primary; one clear primary CTA vs three equal-weight items
- greetingReveal.ts - site greeting decrypts through CRT block
drawing characters on page load, mouseenter, and
touchstart; cancel-and-restart on rapid re-trigger; reduced motion
respected; content always visible before JS runs
- sidebar brand prompt - blinking cursor added after :~$ badge
- greeting scramble chars using terminal block/box-drawing glyphs
- nav section labels - remove success badge from section names;
replace with .nav-section-name plain text at neutral-content color;
6 fewer competing badges across main/explore/meta/options sections
- contact prominence on homepage - Hello and Verify link-actions
in exit section; bio copy revised

commit c04b69965f45a972ed0dcd8f236fd5a4a6eeaecd
Author: asce1062 <tnkratos@gmail.com>
Date: Sat Apr 4 16:45:54 2026 +0300

chore: layout composition and spacing rhythm

- homepage section spacing mb-3/mb-6 → mb-8/mb-12; terminal
commands now breathe like a real shell session
- main page wrapper pb-4/pb-8 → pb-8/pb-12; grounded bottom
- about.astro exit section mb-6 → mb-10; consistent section rhythm
- header #navigation mb-3 → mb-4; tighter breadcrumb clearance
- ContentLayout metadata - display:block with mt/mb, replace
<br><br> hack with proper spacer; date/tags visually grouped
- heading margins in markdown.css - article h2/h3/h4 get
margin-top/bottom for reading rhythm; first-child exceptions suppress
double-spacing at section tops
- skip-link border-radius 0 0 4px 0 → 0; defends zero-radius
identity
- share-notification box-shadow rgba → oklch for color consistency

commit 5cbbda715fb3145a4f854b1eac8720c7d867d93c
Author: asce1062 <tnkratos@gmail.com>
Date: Sat Apr 4 16:36:42 2026 +0300

chore: foundation, correctness and token alignment

- remove rounded-md from ThemeSwitcher (breaks zero-radius identity)
- remove rounded-md from Header search button (same pattern)
- aria-hidden decorative blink cursors across 13 pages
- remove color override from b{} in global.css
- shadow tokens → oklch; add motion token vocabulary to theme.css
- sidebar overlay → oklch color space
- code highlight color → color-mix warm void tokens
- char-id syntax highlight → primary/accent/secondary tokens
- collapsible-nav references motion tokens; grid refactor deferred to phase 5
- fluid heading scale with clamp() scoped to article (content pages only)