Aris watched over her shoulder, his arms crossed. "No way. Show me the live queries."
She selected "Update All" for that one note. It worked. The query ran instantly, showing three tasks instead of raw brackets. Then she tried a template—the old [% template "status" %] was now {{template status}} . The assistant flagged it with a gentle note: Template syntax changed in 1.1.0. Click here to auto-migrate. She clicked. It migrated. She ran the index rebuild. It completed in 12 seconds. silver bullet 1.1.4
A small, friendly banner appeared at the top of the screen: I found 1 legacy query. Would you like me to update it? [Preview Changes] [Update All] [Skip & Flag] Zara clicked "Preview Changes." It highlighted the exact lines that would change, showing a side-by-side diff. Nothing was hidden. No magic. Just clarity. Aris watched over her shoulder, his arms crossed
They rolled out the full upgrade that night. The migration assistant processed 2,304 notes. It flagged 14 ambiguous queries that needed human review—and provided clear explanations for each. No data loss. No emergency rollback. No antacid. It worked
Zara navigated to the solar array emergency protocol. The @page references were still there, but now they were smart . Instead of brittle text links, 1.1.4 used . The note said: See [[ops:emergency:solar_array]] . The old version would have broken because the path changed. But 1.1.4's new "fuzzy space resolver" looked at the note's frontmatter, saw space: lunar_vault , and automatically resolved the correct internal path.
On the right: the new, recommended syntax: {{#each page.tasks}} - [ ] {{this}} {{/each}} .
Zara pulled up the Silver Bullet 1.1.4 release notes on her tablet. "Look here," she said, pointing. "Section 1.1.4: 'Enhanced Query Resilience and Template Migration Assistant.'"