Native Websites Ability Reference: Projects and Recovery

What Native websites needs before these load

These declarations ship in GoBuildWP Pro. Paid project operations depend on the licence and the site's capabilities and safety policy. The source also registers bounded read, export and recovery operations through a separate recovery path. Inspect actual availability after a licence change. Cloud preview needs the configured isolation service; declaring a preview operation does not prove that service is connected or healthy.

Native websites editions

pro

Agent skills shipped

native-site-generation

Start with the site and project revision

Inspect the site identity, current projects and environment before creating a project. Read the current status, files and diff before proposing a patch. A mutation carries an idempotency request ID and, after creation, the expected revision; stale revisions and conflicting requests are refused.

Project files and asset declarations are untrusted input. Static validation checks the submitted source, but does not replace the isolated preview or a real browser inspection. A draft project does not authorize executing its code on the live site.

Keep preview evidence and approval together

Request the configured Cloud preview only after reviewing the submitted files and validation findings. Inspect the returned result and verify the required pages and interactions independently. The website reference documents the declaration; it is not a completed compatibility or isolation test.

Installation, activation and recovery require Developer Full Access and explicit confirmation. Their inputs bind the artifact, installed state and environment hashes. Approval for a previous revision or different environment is not approval for the current operation. Read the actual request and current state before an authorized person approves it.

Recover code without restoring an old database

The project separates theme and companion artifacts from generated WordPress content. Use the content operations for their bounded content changes and inspect returned outcomes. Do not turn code recovery into a database restoration that would overwrite later posts, orders or submissions.

Before recovery, inspect the project's versions, target release and current site state. Use only the supported, approved recovery operation and verify the public site afterwards. Recovery of a managed artifact does not promise reversal of every external effect or every later edit.

Representative call sequence

This sequence describes the documented calls and checks to perform. It is not a recorded result from an installed WordPress site. Inspect returned errors and partial results, then verify the saved values and affected output before proceeding.

Review a managed theme project before considering execution on a site.

1. 01 wppilot/native-site-inspect Confirm site identity, projects and declared environment requirements.
2. 02 wppilot/native-site-status Read the project revision and its current workflow state.
3. 03 wppilot/native-site-diff Inspect the proposed file changes before validation or a preview request.
4. 04 wppilot/native-site-read-files Read the bounded file contents needed to review the proposal.