feat: apply feedback updates and streamline online delivery

AGENTS.md

@@ -1,8 +1,11 @@
 # Repository instructions
 
-## Online and offline parity
+## Online-only release policy
 
-- Every user-facing feature, fix, data update, and behavior change must be included in both the online app and the offline app.
-- Keep shared behavior in `src/` whenever possible. If an online-only dependency is introduced, add or update the corresponding offline alias or adapter under `offline/`.
-- Treat `npm run build:offline` as a required verification step for every repository change, in addition to the relevant tests, checks, and online build.
-- Do not commit generated `offline-dist/` or `release/` artifacts unless the user explicitly requests packaged artifacts; these directories are ignored build outputs.
+- The supported product and release target is the online app, including the GitHub Pages deployment.
+- Do not run `npm run build:offline` or `npm run package:offline` during implementation, verification, commits, releases, or deployments.
+- Do not create, commit, upload, or publish standalone offline builds, `offline-dist/` output, or offline ZIP artifacts.
+- Online/offline feature parity is no longer required. Legacy offline-related source may remain only where the online Pages build still depends on shared adapters.
+- Verify repository changes with the relevant tests, `npm run check`, `npm run build`, and `npm run build:pages` when preparing a deployment.
+- Do not bump the package version, create version-specific release notes, create tags, or publish GitHub Releases for routine online commits and deployments unless the user explicitly requests them.
+- Use `UPDATES.md` as the single user-facing update history and include only changes that affect service users.