This section records the current documentation-review limits separately from the historical RC issue list below. An unrun check is missing evidence, not proof of a product defect or a successful release.
Current review gates
- Free/Pro source differs from the pinned ZIPs with the same version labels. The full comparison includes checkout/payment/service code, template metadata and language/build assets as well as the canonical license origin. The affected workflows need delivery alignment before shipped claims.
- Some package-owned guides/manifests still use pre-rename identities or historical schema/version assumptions. Current examples follow actual bootstrap/interfaces; owning sources are not silently edited here.
- Prior offline suites retain failures for obsolete assertions, incomplete stubs and old shortcode fixtures. New native/source checks do not turn those whole suites green.
- Free’s current POT extraction check is stale while its MO/JSON build check passes against existing catalogs. Do not infer complete source-string coverage from generated-file consistency.
- Aurelia 1.3.7’s optional sample-hotel wizard needs Free 3.28.1, above this review’s Free 3.28.0 baseline. Its licensing compatibility metadata also needs reconciliation with the current shared runtime source/README.
- Two earlier published Documentation bodies have namespace/backslash drift. Canonical revisions and private HTML are separate from target repair; the publisher update/round-trip lane must verify actual body bytes.
- Real WPML/Polylang sessions, OTA feeds/API acceptance, licensed theme/Pro UI, real gateway settlement/refunds and Internet mail delivery require separate environment evidence.
Publication and history
All 104 current articles are review revisions, not automatically publishable because files exist. The working publisher 0.2.0 has rehearsed private staging, target fingerprints, resume and protected rollback on disposable data. That evidence does not deploy it or repair the two actual target bodies. The exact release and target batch still require approval and readback before publication.
Do not invent a universal refund/retry flow, full anonymity, instant OTA locking, no-JavaScript card payment or blanket accessibility certification to work around a gap. Keep capability, source/package/runtime and historical evidence explicit.
See the compatibility matrix and the owning operational/troubleshooting guides for specific recovery boundaries.
Historical release record
The following RC-era text is preserved as a historical record, with heading depth adjusted only. Its versions, acceptance statements and review status describe that earlier record; they are not a new current-release or publication approval.
Product 1.0 RC known issues
This list is intentionally visible because Product 1.0 is a release candidate, not a stable launch. The last known-good package pair is Free 3.28.0-rc.7, Pro 1.36.0-rc.7 and Aurelia 1.1.0-rc.8; do not substitute an untracked ZIP or reuse a version label for different bytes.
External iCal blocks may be delayed until the next scheduler interval. A failed fetch, parse, license or storage operation must preserve the last known-good snapshot and keep its external blocks enforced; it must not silently release occupancy. Check iCal health, UTC timestamps and the source error log before forcing a retry. The existing Booking.com and Agoda API channel remains a separate Advanced Integration and follows its own callback and credential diagnostics.
WooCommerce checkout can be blocked by currency, number-of-decimals or strict order mismatch. Compare the server order and payment ledger rather than browser totals. A single_language provider state is valid and should render a stable label, while a missing evidence state means the report cannot yet support a product-defect claim. Theme cache or stale responsive assets require a real HTTP check after cache invalidation. Escalate with redacted logs, versions, route, locale, viewport and UTC time; never attach credentials, live iCal URLs, payment secrets or production database dumps. These are operational caveats, not permission to bypass the launch gate.
