Start Here

GCD-WEB-282 · v1.0.0 · Free · MIT

PRESERVE-WHAT-WORKS

This package is not permission to redesign the website, replace its router, change routes, restyle pages, alter navigation, rewrite the homepage, or disturb authentication, checkout, analytics, SEO, APIs, databases, mobile behavior, or unrelated accessibility behavior.

Touch only one reviewed settled-navigation integration point, its exact title adapter, one host-owned live region, and the approved heading or main focus target.

Before installation

  1. Save the source revision and deployed artifact.
  2. Record current title, focus, scroll, live-region, router, analytics, and error behavior.
  3. Identify a truthful content-ready signal and stable route key.
  4. Read README.md, INTEGRATION.md, SECURITY.md, and ROLLBACK.md.

Install and test

  1. Copy the package without changing unrelated files.
  2. Run npm test, npm run check, and npm run example.
  3. Connect the smallest possible host-owned adapter.
  4. Test link, form, back/forward, redirect, slow content, error, nested, and same-route cases.
  5. Run keyboard, browser, screen-reader, mobile, title, SEO, analytics, hydration, and critical-journey regressions.

Failure and recovery

If an effect fails, record the exact effect without personal data and restore the prior bounded integration. The controller advances state only after all requested callbacks resolve, but it does not automatically undo earlier host effects.

Compatibility and limits

The core is framework-neutral ESM with zero dependencies. Framework and assistive-technology behavior differs. This package cannot prove focus placement, announcement delivery, usability, WCAG conformance, or production correctness.

PRESERVATION CONFLICT / REVIEW REQUIRED

Stop if integration requires router replacement, route restructuring, global CSS, forced focus on every render, a homepage change, or an unrelated rewrite. Use the pure planner for review and choose the smallest compatible alternative.

Rollback and publish next step

Remove the bounded callback, restore checkpointed code and attributes, run the regression matrix, redeploy the previous artifact, and verify production. Publish only after the exact target matrix passes and retain the checkpoint through the monitoring window.