Write Internal Docs

Write a doc for .internal-docs/ (private repo browseros-ai/internal-docs), as Markdown plus a self-contained HTML sibling, and open a PR. The subject is whatever the user names ("/write-internal-docs nightly signing") or, on a feature branch with no topic, the branch's diff. Companion to ask-internal: that skill reads internal-docs, this one writes it. Supersedes the older personal document-internal flow.

Announce at start: "I'm using the write-internal-docs skill to draft and land an internal doc."

Hard rules — never do these

• NEVER write inside the user's .internal-docs/ checkout. All writes happen in the work clone.
• NEVER push to internal-docs main. Feature branch + PR only.
• NEVER touch the OSS repo's .gitmodules or submodule pointer. The sync workflow moves it after merge.
• NEVER git add -A or git add . in the work clone. Specific paths only.
• NEVER run a clone-touching command without the guard [ -d "$CLONE/.git" ] — a missing clone must fail loudly, not fall through to the OSS repo.
• NEVER fabricate content for empty template sections. Empty stays empty.
• NEVER hand-edit an .html sibling. The .md is the source of truth; regenerate the HTML from it.
• NEVER cite a file or line number you have not actually read.

Voice rules