The committed release inventory is generated by the plugin source and preserved byte for byte.

Release artifacts

The original tagged manifest is retained exactly. The separate website export combines its registry metadata with supplemental sitemap, robots, verification, and REST route families, including optional MCP Adapter transport. It also reads publication limits directly from runtime constants. Its count describes supported route families, not the number of enabled URLs on an individual WordPress site.

Editable source and release validation

The tagged source contains the editable JavaScript and CSS shipped in the ZIP. Quick Setup uses WordPress’s wp.element directly; there is no JavaScript/CSS compilation step. After composer install, bash bin/package-candidate.sh reproduces the package from a source checkout, including a published tag. Assets are copied unchanged. For an unpublished candidate, composer release:build additionally validates the ZIP in disposable WordPress with Plugin Check.

A validated candidate is only one release step. Publication requires reviewed website content matching the exact source commit and channel. The full composer release workflow publishes the plugin, deploys the matching website, and verifies the production contracts, downloads and changelog on cybermaps.dev before reporting completion. composer release:status identifies pending steps; composer release:resume -- --tag vX.Y.Z finishes an interrupted website handoff without republishing the plugin. The repository’s release workflow documents dependencies, local installation, publication, and website handoff.

The 8.0.2 audit checkpoint records AI-assisted source reviews, native fault tests, and measurements from 1,000 to one million primary records. It retains incomplete operations, measured regressions, and remaining limitations. The mandatory release gate runs after that checkpoint.

Configuration roots

General settings live in cybermaps_settings. Discovery strategy, crawler policy, and identity have separately owned options and sanitizers. Read them through the plugin configuration store; preserve unrelated settings on partial saves.

Build an extension

Use the extension and lifecycle reference. An extension owns its namespace, settings, lifecycle, and release artifact. It must not replace CYBERMAPS or depend on its internal service container.

Site agent API

This website’s public read-only API reads these published pages. It is separate from the WordPress plugin’s optional authenticated MCP interface.