[WELLMANIFEST] Reconcile adopted standards and verify Planfile delivery

[tom-sapletta-com]

Audit date: 2026-09-15. Scope: this repository only; planning, not authorization to modify source or deploy.

Observed local checkout SHA: dd1229fadf20a60ff21edd07c1937d3a136a4b89. Local declared adoption status: review-required.

Comparison is against observed GitHub default-branch commits and VERSION, not an assertion that every changed commit requires an upgrade.

No declarations means unavailable evidence, not proof that no standard is followed. Select applicable wellmanifest packs; do not install every pack indiscriminately.

• wellmanifest/new-project: adopted a22eb47ca0e7c06ac927d1c0d843eabb798bfadd (version 0.14.0); observed upstream 2b016654cff1a1ccef2c0d6126a9c2550ae6b37a (version 0.20.31); pin-differs-review-required. Declaration: .governance/manifest.lock.json.

Acceptance criteria

• Reconcile actual applicable standard adoptions with deployed/default-branch state; record unknowns and exemptions.
• For each differing pin, compare version and relevant artifacts; use the managed adopter in a separate bounded implementation ticket only when needed.
• Preserve project overrides, dirty work, historical tasks and stable document links; never edit managed hashes to bypass validation.
• Verify local Planfile ID to GitHub issue mapping and retry deduplication without broad bidirectional sync.
• Run managed governance and stack checks after any separately authorized adoption; report declared versus protected-CI coverage.

Existing related work (reconcile/reuse scope; do not duplicate implementation):

• [DOCS] Standaryzacja dokumentacji, uzgodnienie historii i deduplikacja #6

---

Strategy Metadata:

• deduplication_key: dev-quality-fleet-readiness-v1:autogrammar/vql
• planfile_id: VQL-005