drift detection

Content integrity

Every mirrored page (/cowork/*, /claude-tag/*) is hashed at the moment it's pulled from Anthropic's own docs. The hash is the first 16 hex characters of sha256(file bytes), computed by scripts/gen-hashes.py and checked into src/manifest.ts next to the page it covers.

This catches drift the same way git diff catches any other change: re-run the generator, and any upstream edit to a mirrored page shows up as a changed hash on that one line — instead of silently going stale while this site keeps serving the old text as if it were current.

How to check for drift

1. Re-fetch the current upstream pages into docs/docs/claude.com/docs/{cowork,claude-tag}/ (the source this site's content is drawn from).
2. Run python3 scripts/gen-hashes.py — it recomputes every hash and rewrites src/manifest.ts in place.
3. git diff src/manifest.ts. A changed hash value on a line means that page drifted upstream; the slug/title/desc around it tell you which page to re-copy and re-read before redeploying.

The cloudflare/ section is original writing with no upstream to drift from — its hash is a local-integrity checksum only, catching an accidental hand-edit that skipped regeneration.

Cowork (mirrored from claude.com)

Claude Tag (mirrored from claude.com)

Cloudflare (original writing, not mirrored)