Docs/code sync: code-to-docs process + catch-up for #778-#800#802
Merged
Conversation
The code → docs half of the two-way docs/code sync. The skill (.claude/skills/code-to-docs) is the operational procedure: classify a diff, map it to pages three ways (feature / audience / grep for exact strings), update FACTS.md first, ground every claim in code, verify links + build, and ship as a review PR. The developer-internal page documents the process and records the planned docs → code direction. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…tor) Ran the code-to-docs process over everything merged since the corpus was written (v2.0.5 is still the production release, so new features carry the dembrane-next-only tag): - FACTS.md: Ask home + agent toolset + assistant memory/context, the Monitor route, workspace + user settings sections, account-deletion reality (server endpoint only, no UI - do not document a button). - features/chat-and-ask.md + users/host/chat-and-ask.md (the reported stale page): agentic mode as it ships today - Ask home, starter chips, Templates menu, progress + Stop, named citations, docs answers, proposals-for-review, reach-out, memory. - features/account-and-security.md + users/host/account-and-settings.md: the Assistant memory surface (view + remove, owner-only). - users/host/managing-your-workspace.md: assistant context + workspace memory in General settings. - features/recording.md + users/host/collecting-conversations.md: the Monitor - participant flow lanes, audio warnings, transcription progress, Live & recent. - features/dembrane-next.md: table now lists agentic mode (expanded), assistant memory & context, and the Monitor. - users/developer-internal/chat-and-agent.md: the real 20-tool set, proposal flow, memory scopes, workspace-context prompt line. All UI labels copied from source; site builds (84 pages); new page linked from map + section index. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
spashii
added a commit
that referenced
this pull request
Jul 6, 2026
Follow-up to #802 (which caught up docs for #778–#800). Documents the **live mic-level meter** added to the Monitor in #803. The Monitor now shows a per-recording level meter (from the participant beacon's `audio_level`, 0..1 RMS) so the host can *see* audio is actually flowing — not just that chunks are landing — with a soft "check the mic isn't muted" nudge when it goes silent. Updated, all grounded in the shipped labels: - `docs/_authoring/FACTS.md` — Monitor per-conversation rows now list the mic-level meter - `docs/features/recording.md` — "Is the audio coming in?" bullet - `docs/users/host/collecting-conversations.md` — host retelling Build: `folder2website` clean (84 pages, no broken links/anchors). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sets up the code → docs half of the two-way docs/code sync, saves the process itself as a skill + a docs page, and proves it by running the process over everything merged since the docs corpus was written. (Trigger: docs.echo-next.dembrane.com/users/host/chat-and-ask.html was stale.)
The process (commit 1)
.claude/skills/code-to-docs/SKILL.md— the operational skill: classify the diff (user-observable or not; "no docs impact" is a valid conclusion), map it to pages three ways (owning feature page / every audience retelling / grep the docs for exact strings the diff touched), updateFACTS.mdfirst, ground every claim in the code (never the PR description; copy UI labels exactly), trickle to related pages, verify links + build, ship as a PR. Never a direct push — the review is the point.docs/users/developer-internal/maintaining-docs.md— the process documented for humans, including the planned docs → code direction (docs edit becomes the spec, trickles to code by references, also reviewed). Linked from the section index andmap.md.The catch-up run (commit 2)
Input: PRs #778–#800 (everything user-visible since the corpus landed on 2026-07-03). Production is still v2.0.5 (2026-06-24) and
ENABLE_AGENTIC_CHATis off in production, so new features carry the dembrane next only tag per the existing convention._authoring/FACTS.md,features/chat-and-ask.md,users/host/chat-and-ask.mdfeatures/account-and-security.md,users/host/account-and-settings.md,users/host/managing-your-workspace.md, FACTSfeatures/recording.md,users/host/collecting-conversations.md, FACTSfeatures/dembrane-next.md(3-row table)users/developer-internal/chat-and-agent.mdChecked, deliberately left alone:
DELETE /user-settings/account, suspend + 30-day purge) but no frontend UI shipped — so no page documents a button. Recorded as a warning in FACTS so nobody documents it prematurely.users/host/getting-help.md: already accurate (written with Chat polish batch 2: honesty, recovery, links, Ask home #793).features/organisations-and-workspaces.md: doesn't enumerate settings fields; no change needed.Verification: every UI label was copied from source by a code sweep (exact
Trans/tstrings — this caught four labels that would otherwise have been documented wrong, e.g. the error badge readsError, not "Transcription error"; the docs-chooser cards areOpen documentation/Open chat documentation). All relative links + my new anchors resolve; the site builds clean with folder2website (84 pages; new page reachable from map.md).Pre-existing issue observed, not fixed here: 27 stale heading anchors on older pages (tiers/roles/partner pages) — links open the right page but don't scroll. Good first target for the next docs sweep.
🤖 Generated with Claude Code