Hot Cache
Estimated reading time: 2 minutes
Page Improvements
- Improve Page Polish content, structure, and presentation of this page
- Expand Page Add depth, examples, and missing sections to this page
- Update Page Refresh outdated content, versions, links, and screenshots
- Fix Page Issue Report a typo, broken link, layout glitch, or content bug
- SEO Optimize Improve discoverability, metadata, and structured data
- Accessibility Audit Audit this page for WCAG 2.1 AA compliance
Site Improvements
- UI/UX Improvement Propose a design or UX refinement for the theme
- New Feature Propose a new site-wide feature or capability
- Component Enhancement Improve a Jekyll layout, include, or shared component
- Performance Optimization Improve load time, Core Web Vitals, and asset delivery
Table of Contents
Recent Context
Last Updated
2026-07-06. Ran a full pre-PR cleanup pass: fixed real contract-compliance gaps, and — per the repo owner’s explicit instruction this session — established that zer0-pages’ declared purpose is to be a second brain for zer0-mistakes, the upstream theme repo, which previously had no wiki presence at all.
Key Recent Facts
- This branch (
claude/beautiful-driscoll-82fb01) carries the entire architecture — PRD, vault conversion, claude-obsidian submodule, and the Jekyll/Obsidian bridge pipeline — as commits not yet merged tomain. This cleanup pass was preparation for that first PR. - Contract-compliance fixes:
pages/index.mdwas missingdescription/permalink/aliases;pages/posts.mdwas missingpermalink/aliasesand, worse, its default Jekyll URL wouldn’t have matched/posts/, which_data/navigation/home.ymlandmain.ymlalready hardcode — a real latent bug, now fixed. _posts/permalink “gap” is by design, not a defect: 31 of 38 post files lack explicit permalink/aliases, but_config.ymlconfirms_postsis Jekyll’s native collection (sitewidepermalink: pretty, no customcollections:entry) — rootCLAUDE.mdnow says so explicitly so this doesn’t get re-flagged as a bug next audit.- New entity: zer0-mistakes — first wiki page for the theme repo itself. Documents the real gem-consumption relationship (layouts/includes/Bootstrap from the gem,
_data/supplied locally,obsidian_links.rbdeliberately not reused) and is explicit that the “second brain” relationship is declared, not yet built out — no zer0-mistakes-internals content has been ingested here yet, only the existing consumer-facing_docs/development/docs. - README.md, PRD.md, wiki/overview.md all now state the second-brain purpose and/or caveat the PRD’s aspirational Django+React framing (previously that awareness existed only inside the wiki, not in the documents a first-time visitor would actually read).
- Verification: unit tests 93/93 passing. Full local
jekyll buildisn’t possible in this sandbox (Ruby 2.6.10 vs. theme’s >=3.2 requirement) — matches documented CI-only build capability. - Wiki orphans fixed:
wiki/sources/_index.md,wiki/concepts/_index.md,wiki/entities/_index.mdare now actually linked fromwiki/index.md(were zero-inbound before). - Content scope unchanged — docs / posts / notes only, 89 / 38 / 6 (Home).
Recent Changes
- Edited
pages/index.md,pages/posts.md(frontmatter fixes), rootCLAUDE.md(_postspermalink clarification),README.md(second-brain paragraph + PRD caveat),PRD.md(status-note callout). - Created
wiki/entities/zer0-mistakes.md. - Updated
wiki/index.md(orphan-fix + new entity link),wiki/entities/_index.md,wiki/entities/zer0-pages.md(cross-link),wiki/overview.md(second-brain framing), this hot cache, and appendedwiki/log.md.
Active Threads
- Biggest open gap: zer0-mistakes’ own internals (architecture, release-automation, plugin design) are not yet ingested into this wiki — only surface-level consumer docs exist. Next real second-brain step:
/autoresearchor/wiki-ingestagainst the zer0-mistakes repo’s owndocs/directory. .raw/still holdsREADME.mdun-ingested; drop further sources and say “ingest [filename]”.scripts/wiki-lock.shremains inoperable here (flockmissing) — solo passes only; no addresses (DragonScale off in this vault).- This branch has not yet been pushed or opened as a PR — that’s the next step once this cleanup is reviewed.