Issue 69 Project-Owned Wiki Sync Drift

Problem

hi update --check reports an intentionally customized apps/wiki/scripts/sync-content.mjs as changed managed harness drift. This sets checkFailed and exits 1 even when pack drift, baseline drift, stale files, and every other managed-file check are clean.

The repository owns this wiki synchronization implementation after initial scaffolding and may customize it for its documentation topology.

Required Behavior

• hi scaffold init and setup flows may continue creating the default apps/wiki/scripts/sync-content.mjs when needed.
• hi update --check must treat an existing apps/wiki/scripts/sync-content.mjs as project-authored: do not report it in changedFiles or staleFiles.
• When that script is the only difference, checkFailed must be false and the command must not set exit code 1.
• Apply-mode update must not overwrite the existing customized script.
• Other managed wiki scaffold files must remain checked and writable.

Scope

This fix is intentionally limited to the exact monorepo path reported by issue #69: apps/wiki/scripts/sync-content.mjs. It does not broaden ownership policy for app/wiki, standalone wiki, or other managed wiki files.

Acceptance Criteria

1. A public runUpdate regression proves a customized sync script alone yields a clean check result.
2. The same regression proves other wiki scaffold drift is still reported.
3. Apply mode resolves real wiki drift without changing the customized script.
4. Existing update tests no longer require the project-owned script to be reported or replaced; scaffold-generation coverage remains intact.
5. Focused update tests and CLI typechecking pass.
6. Operator docs and the canonical routed wiki runbook state the ownership boundary accurately.

Dependency Readiness

No Stack Required.