🛡️ Quoting the Unquoted — Hardening Frontmatter and Filling Gaps
🎯 Three Problems, One Session
📝 This session tackled three interconnected issues in the Obsidian vault automation pipeline.
🔓 First, AI-generated reflection titles occasionally contained YAML-special characters like colons and pipes that could break frontmatter parsing.
📭 Second, the hourly updates feature (which tracks modified files in the daily reflection) would silently skip writing update links if the daily reflection note did not yet exist.
🔍 Third, a code review uncovered a subtle bug: the idempotency check for reflection titles would silently fail once titles were quoted, because it compared a quoted string against a bare date.
🔒 Forced Quoting for YAML Safety
🧩 The root cause of the YAML breakage was a single configuration flag. Both reflection-title.ts and blog-image.ts use js-yaml to serialize frontmatter, and both had forceQuotes set to false.
⚠️ With forceQuotes disabled, js-yaml only quotes strings when it detects special characters. But the detection is not perfect for every downstream parser, and creative titles like “2026-03-24 | The Art: A New Beginning” contain both pipe and colon characters that can cause trouble.
✅ The fix was straightforward: flip forceQuotes from false to true in both files. Now every string value in frontmatter is wrapped in double quotes, leaving no ambiguity for any YAML parser.
🔢 Booleans like share true and regenerate_image false remain unquoted because they are not strings. Null fields like tags with no value also remain unchanged. Only actual string values receive quotes.
📊 This required updating 15 test assertions across reflection-title.test.ts and blog-image.test.ts to expect the quoted format. No test logic changed, and no assertions were removed.
📝 Auto-Creating Daily Reflections
🔄 The daily updates module (daily-updates.ts) appends wiki links to a special Updates section in the daily reflection note. Automated tasks like image backfill, internal linking, and social posting all call addUpdateLinksToReflection after modifying files.
📭 Previously, if the daily reflection did not exist when addUpdateLinksToReflection ran, it would log a warning and return false. This was a gap: the blog series generation tasks always ensured the reflection existed before writing, but the hourly maintenance tasks did not.
🆕 The fix imports ensureDailyReflection from the daily-reflection module and calls it before attempting to write update links. If the reflection file is missing, it gets created from the standard template, complete with frontmatter, navigation breadcrumbs, and forward/back links to adjacent reflections.
🧪 Two new tests verify the behavior: one checks that the reflection is created and links are added in a single call, and another verifies that forward links to the previous reflection are properly set up during creation.
🐛 The Quoted Title Bug
🔍 The code review revealed a subtle interaction between the forceQuotes change and the reflectionNeedsTitle function. This function determines whether a reflection note still needs a creative title by comparing the frontmatter title value against the bare date string.
💥 The function reads the raw file line that starts with title colon, strips the key prefix, and compares the remaining value. Before the quoting change, a bare date title looked like title: 2026-03-24 and the comparison worked. After the quoting change, the same title looks like title: “2026-03-24” and the raw-extracted value would include the surrounding quotes, causing the comparison to fail.
🛠️ The fix adds a quote-stripping step that removes surrounding single or double quotes before the comparison. This ensures the idempotency check works regardless of whether the frontmatter was written with or without forced quoting.
🧪 Three new tests cover quoted title scenarios: double-quoted bare date, single-quoted bare date, and quoted creative title.
🔬 Code Review Findings
📋 Beyond the critical quoted-title bug, the code review surfaced several observations.
✅ The Author field “bryan-grounds” correctly survives yaml.load and yaml.dump round-trips because YAML parsers handle the quotes natively.
✅ No circular dependency risk exists between daily-updates.ts and daily-reflection.ts since the import direction is one-way.
⚠️ The parseFrontmatter utility in frontmatter.ts uses a regex-based parser with manual quote stripping, while reflection-title.ts and blog-image.ts use js-yaml. Both approaches work correctly, but the inconsistency is worth noting for future maintainers.
⚠️ The runReflectionTitle and runAiFiction tasks in run-scheduled.ts skip gracefully when no reflection exists. This is intentional: both tasks enrich existing reflections with content, so there is nothing meaningful to generate for an empty note. The creation responsibility falls on earlier pipeline stages.
📊 Impact Summary
🔢 All 1286 tests pass after the changes, up from 1282 before (4 new tests added).
🛡️ Every string value in frontmatter is now deterministically quoted, preventing any YAML parsing surprises from creative titles.
📝 Hourly maintenance tasks now reliably create the daily reflection from template when needed, closing the gap that could cause update links to be silently dropped.
🐛 The reflection title idempotency check works correctly with both quoted and unquoted frontmatter, preventing accidental re-generation of already-titled reflections.
📚 Book Recommendations
📖 Similar
- 🛡️ Secure by Design by Dan Bergh Johnsen, Daniel Deogun, and Daniel Sawano
- 🧪 🧱🛠️ Working Effectively with Legacy Code by Michael Feathers
🔄 Contrasting
- 🎨 💺🚪💡🤔 The Design of Everyday Things by Don Norman
- 📖 Gödel, Escher, Bach by Douglas Hofstadter
🎯 Creatively Related
- 🏗️ A Philosophy of Software Design by John Ousterhout
- 🔬 Release It! by Michael Nygard