sync-code-to-doc

Run sync_code_to_doc.py to generate a grouped change report from git diff, then follow the 7-step workflow: map changes to docs via doc-sync-mapping.yaml, resolve full context through manifest.yaml, locate affected sections, produce an action-list plan, get user confirmation, apply chapter-level edits, and run consistency checks.

Use the --base origin/main flag, which runs git diff origin/main...HEAD to report the accumulated committed changes of dev relative to main. This must be done before promote, since after promotion the working tree is clean and the default diff returns no changes.

After promote, code commits are merged into dev=main HEAD and the working tree is clean, so git diff HEAD is empty and the script exits with code 4. Documentation sync must run before commit in default mode or before promote using --base origin/main.

The --check-docs mode checks documentation index consistency without relying on git diff: dead README indexes, missing index entries, broken links, orphan documents, dead code/ links, out-of-bounds #L line anchors, and stale code-block comments. It exits with code 5 when inconsistencies are found.

The change is flagged as DOC-CONFLICT in the action plan and is never applied automatically. The plan lists suggested structural adjustments, and the document structure may only be changed after explicit user confirmation, since existing chapter structure is controlled.

It requires code/rpi5/manifest.yaml to exist for resolving full source context of modified .diff files, and it only covers the code/rpi5 archive mapped by doc-sync-mapping.yaml. It does not update code/rpi5/README.md mapping tables or perform full document rewrites.