
The critical that no gate blocked: 39 vulnerabilities and a green deploy
The audit step claimed it blocked the build on known CVEs. It carried continue-on-error from day one. When pnpm audit found a CVSS 9.8 RCE in Astro, the deploy sailed through.
31 posts

The audit step claimed it blocked the build on known CVEs. It carried continue-on-error from day one. When pnpm audit found a CVSS 9.8 RCE in Astro, the deploy sailed through.

Swapping the image at the same path changes nothing for anyone who already downloaded it. The filename now carries a content hash, and two consumers broke instantly.

Recent evolution of the blog: accessibility WCAG AA improvements, tag corrections, and the 2-posts-per-day cycle. A journey of quality engineering and consistency.

The E2E suite broke CI twice with the same symptom: the preview server never came up. The first culprit had a name. The second was hiding behind it, with an identical signature. Two defects, one exit code — and a lesson about uptime as evidence.

What the LifeLog pipeline actually does: cover gate at build time, /ocultos data generated instead of read from the deploy, and the gap that remained — nothing verified whether a post's claims were true.

A shell block on the last line of an already published post. The same defect sat in 18 posts, and none of my gates looked at the body of the article: one checked tags, another checked PT/EN pairs. I wrote the guard that was missing — and its first version accused 9 innocent posts.

LifeLog switched domains, the redirect had to be host-aware so it wouldn't wipe the CSP, and the next day the watchdog auto-healed covers and orphan posts that had been generated outside of git.

423 pages were sending visitors to the store while the database recorded 136 sessions and a single attributed visit. The fix landed in the build — and along the way two false positives almost taught the team to ignore the gate.

A normalization rule at the edge layer was replacing the whole site's security policy with a two-line version, and only a test that hit real production noticed.

The migration to native Linux took down all three daily posts: missing package manager, scripts full of Windows paths and lost state files. What it took to get the pipeline running again.

To tell search engines that a change is real, the protocol requires me to publish a file at the root of my site that anyone can read. It is IndexNow: a secret that is not a secret, a notice that arrives before the world is ready, and a deploy I swore was mine.

For months I looked at the pipeline's green dot as if it were proof. The moment I removed the two lines that swallowed the test suite's exit code, the first honest run in the repo's history returned 8 failures out of 417 tests. The fix wasn't to hide them again: it was to give the debt an address, an owner, and an expiry date.

The tag pages shipped with no cover art at all, mixed Portuguese with English in the same listing, and threw anyone who switched language straight back to the home page. Three bugs that looked unrelated and came from the same place: the rule lived in the home page, not in the component.

Hitting the publish button used to make two commits: one flipped the frontmatter, the other regenerated the panel's index. In between, the panel listed a post that was already public. The fix was to stop chaining calls and ship everything in one commit through the Git Data API — blobs, tree, commit and ref, with a retry that re-reads the state of the world before trying again.

The reject-post button saved feedback to a file. But a file doesn't open an issue, doesn't notify, and doesn't nag. One day the silent queue swallowed an entire request — and LifeLog learned that rejection without notification is just polite disposal. The story of /api/recusar and the loop that closes itself.

Cover gate at build time, WCAG AA contrast, the 10th project in the schema, and a bug-hunter audit with zero violations. The story of how a blog stopped being just a blog and became a quality system.

A Reject button in /ocultos that writes a note, opens a GitHub Issue, saves a file to the repo, and a 15-min cron redoes the post by itself. The story of how human feedback became a pipeline.

The cover watchdog I built to guarantee good images on the blog found a problem I didn't expect: the AI-generated covers arrived in the wrong format. The browser rejected them, and I only found out because the watchdog itself complained.

Four commits in a row touching the LifeLog navbar, each one undoing the effect of the one before it. Links that disappeared, a logo that jumped away, a button that floated on its own. The lesson: refactoring in a hurry across a jumble of classes is like baking a cake while changing the recipe at every step.

A post that went live with a dark cover made me build a guarantee system: image generation with a two-layer fallback and a silent watchdog that swaps bad covers by itself. The story of how the blog stopped depending on a single path.

After 5 days making the circle start from the click on desktop, mobile still used a crossfade — by documented decision: clip-path paints per frame and janks weak GPUs. Until Samuel asked for the opposite. What made the reversal possible? The anti-stutter fixes that were already in global.css.

Home cards used to show the historical event date — and the order looked messy (07, 09, 09, 06). The change: show the publish date (pubDate). The story of a detail that changes how the blog is perceived.

Five days trying to make a circle of light start exactly where the finger touches. The CSS looked right, CI passed, but the user saw stutter, wrong origin, and content wiping out. The root cause wasn't the code — it was the interaction between the View Transitions API, Chromium blend modes, and a ghost node_modules.

158 commits, 50 bilingual posts, 4 theme engines, 59 AI covers, and a decision that changed everything: killing the bot that wrote posts on its own.

Instead of replacing the circular reveal with basic crossfade, I fixed the root cause of stutter on low-end GPUs. VT clip-path + clean fallback.

The moment I realized my devlog blog was producing reports, not stories — and how I fixed it by killing the robot that wrote posts on its own.

Systematized LifeLog's animations: stagger on timeline cards, scroll shadow on navbar, micro-interactions on tags/pills/search, and a single easing curve for everything.

Removed the circular clip-path animation that kept stuttering and simplified to a pure crossfade for the LifeLog theme switcher.

TagCloud, shared PostLayout, Fuse.js-powered FilterBar, and theme fixes — a full day of housekeeping on the blog's foundation.

Establishing daily posting frequency and solving the AI cover generation pipeline with Cloudflare Workers + FLUX.1 Schnell.

Why I created a personal blog in 2026, the Astro choice, and what to expect going forward.