[rubentalstra]

What changed and why

The working discipline and the guards that keep the book at https://ferropix.eu/ in step with the code, ported from the siblings (FerroEHR's docs-website rule and docs-claims guard, the family book's writing-style guard, the changelog guard's shape for the same-PR rule).

• .claude/rules/docs-website.md, path-scoped to the site: layout and URLs, the family-book split, the same-PR rule, authoring rules (built versus planned with a tracker link, sibling wiring said as planned, no typed versions), what a gate checks and what only review can, the toolchain and the 1440/390 light/dark look before a website PR merges.
• CLAUDE.md: the "Keep the book current" hard rule, the guards in the repo map, the rule and the new hook in the discipline list. /phase-done gains the book check; the pull request template asks for it; a memory note records the owner's order.
• scripts/checks/book-guard.sh (CI book-guard, pull requests): a change to crates/*/src/**, a crate's [features], app/**, docker/**, deploy/** or a compose file must touch website/book/src, or carry the new no-book label (added to scripts/gh/labels.sh and created). A version bump, a dependency move or a test alone is no surface: the book renders versions.
• scripts/checks/docs-claims.sh (CI docs-claims): every published crate has its page and its row on the crates page; its Features table names exactly the features of its Cargo.toml, both ways; no page types its current version; every section that says "planned" links a FerroHEALTH tracker issue or milestone.
• scripts/checks/writing-style.sh (CI docs-claims, and the new docs_style.sh PostToolUse hook on every edit): em dashes, the buzzword list and AI attribution over the published prose (website, root and crate markdown).
• All three have a --self-test, run by the self-tests job, and both new jobs are in the required conclusion.
• The book: the owner's decision that lookups by a patient identifier use POST, in the security page, the ihe-iti PIXm and PDQm sections, the configuration table and the getting-started example (now .invoked_by(Invocation::Post)): the planned PIX Manager accepts $ihe-pix by GET (ITI-83) and by POST with a Parameters body (FHIR R4 Operations §3.2.0.1) and logs no URL query (The PIX Manager answers $ihe-pix by POST as well as GET, and no request log records a URL query #52); FerroHEALTH clients call by POST so a BSN never appears in a URL; proxies must not log query strings. The "keeping the book current" page lists the four guards, and two "test harness" phrasings are reworded for the writing-style guard.

Closes #48

Licensing of contributions

• I accept the terms in CONTRIBUTING.md § Licensing of contributions: I have the right to submit this work, I license it under the project licence of the version it lands in, and I grant the Licensor the relicensing right stated there.

Checklist

• Every conformance decision cites the specification (the IHE ITI Technical Framework, PIXm, PDQm, HL7 FHIR R4, HL7 v2), never memory and never another implementation.
• Rust gates pass, once the workspace has a member: no Rust changes.
• Every refusal the change adds has an asserted negative test, and no test was weakened to pass.
• Shell and workflow files are clean: shellcheck --severity=style, actionlint, zizmor --min-severity=low .github/, and the self-test of every script the change touches.
• CHANGELOG.md has an [Unreleased] entry.
• The book under website/book/src is updated for every user-visible change.
• No patient data, real identifier, key, token or password in a fixture, test or example.
• Every commit is signed.
• No AI or assistant attribution anywhere in the commits or this PR.