docs: role-based user manual V0.1 (review draft) with real system screenshots

[baozhoutao]

What

Adds the role-based user manual V0.1 (review draft) — one volume, one chapter per business role — plus the 62 screenshots it is built on, and the Word build that produces it.

• docs/手册/KPI考核管理系统-操作手册.md — markdown source (single source of truth)
• docs/手册/图片/*.png — 62 screenshots
• docs/交付/KPI考核管理系统-操作手册-V0.1.docx — Word deliverable
• scripts/md2docx.cjs — now embeds markdown image lines
• package.json — new docs:manual script
• README.md — manual added to the document table

Structure

Chapters are derived from the permission model (six positions), not from the menu tree:

1. Common operations (sign in, workbench, app switcher, queues, password, Excel export)
2. HR reviewer — indicator library, plan versions, review steps, participating subjects, indicator assignment, per-person split, disputes, publishing, review/reject, bonus points, adjustment approval, archiving, audit query
3. Department reporter — find the sheet, fill actual values, bulk import, submit, handle rejection, request a data adjustment
4. Branch checker — my checks, confirm, raise a dispute
5. HR head — approve bonus points, approve adjustments
6. Executive leader — final approval, results and dashboard
7. Cross-role FAQ table

• Appendix A: chapter ↔ screen index (for keeping the manual in sync with UI changes)
• Appendix B: 3–5 verifiable practice tasks per role

Every operation follows the fixed four-part shape: context → steps with annotated screenshot → how to confirm it worked → common problems.

Screenshots

All 62 screenshots come from a live instance seeded with demo data, each captured while signed in as the target role's own demo account (five demo accounts with business-style Chinese names and example.com addresses), with red boxes and numbered badges injected over the button or field the step refers to. The demo data was produced by walking one continuous business line end to end: plan configuration → publish (including a failed completeness check) → data entry → submit (including the blocked incomplete submit) → branch check (dispute, then confirm) → HR reject → re-review and approve → bonus points → source-data and result adjustments → leader approval → archive snapshot → audit query.

Word build

scripts/md2docx.cjs gains one rule: a line of the form [alt](图片/x.png) becomes a centred ImageRun scaled to the text width (PNG dimensions read from the IHDR chunk, so no image dependency is added). Captions keep the existing centred-caption rule. Everything else is unchanged — the design proposal build is byte-identical:

$ node scripts/.tmpcheck/md2docx.old.cjs docs/00-设计方案.md /tmp/old.docx
$ node scripts/md2docx.cjs docs/00-设计方案.md /tmp/new.docx
/tmp/old.docx 315947 c7453610e9ccf03bc41b6f9675a6f240
/tmp/new.docx 315947 c7453610e9ccf03bc41b6f9675a6f240

(md5 of word/document.xml; the zip container itself is not byte-reproducible because docx embeds fresh ids.)

pnpm typecheck passes. No src/ file is touched.

Notes for review

The manual documents the interface as it behaves today. Interface issues noticed while writing it (object and field labels resolving to the English bundle, raw status values and identifiers surfacing in the audit list and the person-score chart, a technical prefix on error toasts, the check-task decision maker/time not being stamped, a required status field with no default on new adjustment records) are reported separately as candidate work items rather than worked around here.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VR2khJ3Me96btawVsfG6jb

---

Generated by Claude Code