All readable docs ship as HTML on docs.jonahtebaa.com

name: All readable docs ship as HTML on docs.jonahtebaa.com
description: Hard rule — any .md/.txt/.doc Jonah is meant to read must auto-generate a simple HTML page on docs.jonahtebaa.com, get added to a date-grouped index, and open in his Mac Chrome (Default profile) the moment it's created. Locked 2026-05-10.
type: feedback
originSessionId: 793fec8a-3410-4470-ac41-247b031c3b60

🚨 HARD RULE — locked 2026-05-10 by Jonah

Whenever I create a .md, .txt, .doc, or any other readable text/document file that I want Jonah to read — plan, process, documentation, post-mortem, summary, brief, operator guide, anything — I MUST:

1. Render an HTML version of it (simple, fast, small — basic formatting only: bold titles, indentation, bullets, tables).
2. Publish it to docs.jonahtebaa.com so it opens in a Chrome tab via clean URL.
3. Add it to the index page at https://docs.jonahtebaa.com/ — sorted by date, grouped by date.
4. Each index entry is a clickable link with: file name — description — file location — date created. The name links to the formatted HTML.
5. Open the new page in Jonah's Mac Chrome (Default profile, NEW tab) as soon as it's created — same mechanism as /ask (osascript open location).

HTML style — minimum-viable, NOT fancy:
- One small <style> block, no external deps, no JS.
- Bold headings (h1/h2/h3 with weight + size).
- Proper indentation for nested lists.
- Real bullets and tables (don't lose them in the convert).
- Monospace for code blocks.
- Max-width ~ 820px, comfortable line-height, padding.
- Footer line with: source path + date generated + back-to-index link.

Why: Reading raw markdown in a chat or terminal is friction. Jonah wants to skim/read/copy from a real Chrome tab in the same flow he uses for everything else. The index is so nothing gets lost — every doc I've ever written for him is one click away, sorted by when I made it.

How to apply:
- Trigger every time I Write or save a doc/plan/process/summary intended for Jonah's reading.
- Skip for code files, configs, JSON, internal scratch, hook output, or files I'm only writing for myself / for another agent to consume programmatically.
- If unsure → render it. The cost is ~50ms.
- Tooling: brian-doc add <path> --desc "..." (CLI at /usr/local/bin/brian-doc) handles render + index update + Mac Chrome tab.
- Backend: Caddy block docs.jonahtebaa.com → file_server /var/www/docs/.
- Source-of-truth metadata: /var/www/docs/.index.json (regenerates index.html on every add).
- Mac Chrome tab opens via existing chrome-mac SSH path — Default profile, NEW tab (existing hard rule).

Failure modes to avoid:
- Don't fall back to Drive file:// — the URL must be https://docs.jonahtebaa.com/....
- Don't reuse the active Chrome tab — always NEW tab (open location in AppleScript does this).
- Don't hijack profiles other than Default unless Jonah names one.
- Don't skip the index update — that's what makes the rule useful.