Creates missing versioned starter content without silently overwriting owner-edited WordPress pages and records the applied content release.
Owner edits win
The setup operation creates missing content and records the applied content version. Future managed-content updates may update only content still proven unchanged from the prior starter hash; owner-edited content is preserved.
Fresh installation
A fresh setup receives the complete current starter tree. An existing site may rerun setup to create newly introduced pages, documentation, menus, and posts without deleting content.
Scope
This starter page defines the questions, boundaries, evidence, and failure modes that should be recorded before a capability is presented as supported.
Engineering considerations
- Identify the source, version, target environment, and owner.
- Separate observed values from estimates and externally reported values.
- Record trade-offs, unsupported cases, and fallback behavior.
- Link performance statements to a compatible benchmark methodology.
Verification questions
- What exact artifact, revision, backend, and environment were reviewed?
- Which assumptions could change the result?
- Which data should be retained so another engineer can reproduce the conclusion?