# Elderly Support deployment — 16 October 2026

## Active installation

- Project: `mamserver:/var/www/html/artcare`.
- Public host: `https://elderly.mam-app.org`; MAM-style sign-in: `/login`.
- Account: existing `ElderlyEntry@MAM`, user type 21; password was not reset.
- Registration: `/elderly-support/register`; management: `/elderly-support/register/manage`.
- Monitoring checklist: `/elderly-support/followup`; management: `/elderly-support/followup/manage`.
- Monthly report: `/elderly-support/reports/monthly`; authenticated Excel export from the same page.
- Database connection and physical database: `MAM_NAP`.
- Apache origin: `127.0.0.1:8089`, same project `public/` directory.
- Dedicated tunnel: `mam-elderly-support`, UUID `0582853d-dc8f-40c2-a15c-2eca95ee3f8d`.
- Tunnel service: `cloudflared-elderly-support.service`; configuration: `/etc/cloudflared/elderly-support.yml`; readiness endpoint: `127.0.0.1:20249/ready`.

The existing main tunnel configuration at `/root/.cloudflared/config.yml` was not edited or restarted. Apache received a graceful reload to add the loopback listener and virtual host. Other PHP/ART/Child Support services were not stopped. The public host inherits the existing Cloudflare Access sign-in; the user confirmed reaching Elderly Support after completing it.

The local source and deployed runtime are kept aligned using an explicit SHA-256 manifest. The current runtime consists of 52 files, including four minimal shared integration files from the registration phase: Kernel, RouteServiceProvider and both User model copies. Production Composer resolves `App\Models\User` from `app/remote_models/Models/User.php`, so both copies carry the access helper. The MAM-style elderly login is module-owned; existing shared login views/controllers are not overwritten. Phase 3 changed only Elderly module files.

## Database and secrets

The registration phase applied only `database/migrations/2026_10_16_000100_create_elderly_support_registration_tables.php`, explicitly with `--database=MAM_NAP --path=... --force`. It created `elderly_support_registers`, `elderly_support_sync_events` and `elderly_support_sync_counters`. Phase 3 applied only `2026_10_16_000200_create_elderly_support_followup_tables.php`, adding `elderly_support_followups`, `elderly_support_followup_sync_events` and `elderly_support_followup_sync_counters`. Both counters have their initialization row. No unrelated pending migration or role-column change was run.

The persistent elderly payload secret was generated privately on mamserver. It is distinct from Child Support and was not copied to the local `.env` or included in deployment archives. Existing credentials were preserved. The live `.env` is owned by `zeya:www-data`, mode 0640. Preserve the server secret and private backups when replacing a server; changing it makes earlier encrypted payloads unreadable.

## Deployment artifacts and backups

Local deployment package: `outputs/elderly-support-deploy-20261016/`.

Remote staging/results: `/var/www/html/artcare/storage/app/elderly-support-deploy-20261016/` (private, outside `public/`).

- Initial source/environment backup: `/var/www/html/artcare/.local-backups/elderly-support-20261016T035334Z`.
- Registration/login/PWA correction backup: `/var/www/html/artcare/.local-backups/elderly-support-review-20261016T041044Z`.
- Apache/tunnel activation backup: `/root/elderly-support-activation-20261016T040247Z`.

The root activation script is retained at `scripts/elderly-support/activate-origin.sh`. Its successful activation output included an empty `/dev/null` config diagnostic before DNS creation; DNS creation and tunnel readiness succeeded. The retained script now uses the valid dedicated configuration for that DNS command. No rerun is required.

## Verification and limits

| Check | Evidence |
| --- | --- |
| Existing application routes | All 94 pre-existing route definitions preserved; now 25 Elderly host routes |
| Main service continuity | Apache and original Cloudflare process identities/start times retained; ART login 200 and Child Support register 302 remained healthy |
| Dedicated origin and tunnel | Port 8089 listening; tunnel ready with four connections |
| Public HTTPS and account login | TLS certificate verification passed; user confirmed reaching Elderly Support through Cloudflare Access and signing in with the existing account |
| Guest protection and PWA dependencies | Phase 3: 24 read-only live origin checks passed, including no-store 401 APIs, all four shells, login, manifest, worker, styles, scripts and both icons |
| Local automated checks after corrections | 28 backend integration, 19 real-Chrome browser, and 4 JavaScript logic checks passed; synthetic data on disposable MySQL |
| Registration source | Printed questions in registration images 1–3 checked; see `SOURCE_COMPARISON.md` |

## Program ID update

The user-confirmed ID rule is deployed: clinic `HTY`, `SPT`, `SDG` or `TL`, year `26`, and a manually entered five-digit serial from `00001` to `99999`, stored as one string such as `HTY-26-00001`. Three controls compose the ID; browser and server validation agree, leading zeros survive offline/reload/sync, and changing the code preserves the registration UUID. Duplicate combined IDs remain rejected.

Seven module files were updated without a migration or service restart. Backup: `/var/www/html/artcare/.local-backups/elderly-support-id-20261016T045523Z`. Patch staging/results: `/var/www/html/artcare/storage/app/elderly-support-id-20261016/`; local copy: `outputs/elderly-support-id-20261016/`. The full local runtime package was refreshed and still contains 29 files. There were no production registrations at this patch's preflight; no record data was rewritten.

After this update, 31 backend, 20 browser and 5 JavaScript checks passed on disposable local data. Live read-only checks passed for all 19 origin endpoints/assets and five production PHP format cases. Worker cache is now `elderly-support-shell-v4-program-id-20261016`; refresh online after saving current work to load the new controls.

The automated write/sync browser suite was not run against the live database. No production test case was inserted or deleted. Actual account login was confirmed by the user through Cloudflare Access. That phase originally required browser password setup. The direct-entry update below supersedes that flow: both forms open after MAM login. A real device’s installation/offline cycle through Cloudflare Access still needs device confirmation. Firefox/Safari, native installation prompts, follow-up, reports and source-format Excel export remain outside the completed verification.

Read-only origin checks can be repeated on mamserver without migrations or service changes:

```bash
python3 /var/www/html/artcare/storage/app/elderly-support-deploy-20261016/verify-origin.py
```

Do not run the disposable database fixture tests against production or deploy the QA router as a public entry point.

## Phase 3 follow-up deployment

Deployed with `scripts/elderly-support/deploy-phase3.py`. It checked the existing source checksums, the physical `MAM_NAP` database and uncached routes/configuration before changing files. Eighteen module runtime files were installed atomically per file, with new dependencies and the specific follow-up migration before activating the pages. The full backup package now contains 36 runtime files.

- Private backup: `/var/www/html/artcare/.local-backups/elderly-support-phase3-20261016T105956Z`.
- Server staging, migration logs and result: `/var/www/html/artcare/storage/app/elderly-support-phase3-deploy-20261016/`.
- Local deployment copy: `outputs/elderly-support-phase3-deploy-20261016/`.
- Only the follow-up migration was invoked; the existing registration count stayed at one, and follow-up tables began with zero cases. No live test registration/visit was inserted or deleted.
- Environment/secrets were unchanged. Apache and both tunnel process IDs were retained; ART login remained 200 and Child Support registration remained 302. No service was restarted.
- Verification: 31 registration backend, 35 follow-up backend, 20 registration browser, 20 follow-up browser and 6 core checks passed locally. All 24 production origin checks passed.

The phase 3 release originally used the same offline password for both forms; the direct-entry update supersedes that requirement. Browser storage upgrades add follow-up stores while preserving the earlier account key and registration data/queue. The test suite verified a version-one vault upgrade and an offline parent/visit sync. Save open work before refreshing online to load the new navigation and worker. Sign-out clears the identity heading as well as form and table data.

See [PHASE_3.md](PHASE_3.md) for the source comparison, visit snapshots, management filters, sync/deletion behavior and remaining scope.

## Direct entry update — extra password removed

Registration, monitoring checklist and both management pages now open directly after MAM login. Create/Unlock/Lock vault controls and routine offline password setup are removed. The browser remembers its account-specific encryption key automatically. Older encrypted data and queues remain intact with optional one-time recovery, which does not block new entry. See [DIRECT_ENTRY.md](DIRECT_ENTRY.md).

- Five Elderly runtime files deployed on 16 October 2026 at 11:52:20 UTC.
- Private source backup: `/var/www/html/artcare/.local-backups/elderly-support-direct-entry-20261016T115220Z`.
- Remote patch/results: `/var/www/html/artcare/storage/app/elderly-support-direct-entry-20261016/`; local copy: `outputs/elderly-support-direct-entry-20261016/`.
- No migration or database rewrite, route change, environment/secret change, or service restart. All 94 existing routes and 25 Elderly routes are unchanged. Apache and both Cloudflare process IDs are retained.
- Local validation: 66 backend, 6 core and 52 Chrome browser checks passed with synthetic records on disposable MySQL. Live read-only origin checks: 24/24 passed. ART login remains 200 and Child Support registration 302. Dedicated tunnel readiness is healthy; public HTTPS verifies successfully and retains the existing Cloudflare Access redirect.
- Worker cache: `elderly-support-shell-v6-direct-entry-20261016`. Save current work and refresh online. The full runtime backup remains 36 files and is aligned with the installed source by SHA-256.

These changes supersede earlier password/setup statements in historical phase notes. Automated write scenarios were not run against production; no live test record was inserted or removed. A real device’s HTTPS installed-app offline cycle through Cloudflare Access remains a device-level check.

## Registration paper-detail correction

Reviewed all five source images again, using only printed prompts. Registration definition version 4 adds co-resident relationships and daily activities, the correct caregiver neighbour question, and separate cooking/bathing/laundry choices. Caregiver inputs are grouped immediately after Health and care, beside Has a current caregiver. The historical family answer remains a separate hidden field; existing narratives and saved records are preserved. See [SOURCE_COMPARISON.md](SOURCE_COMPARISON.md).

- Deployed at 20261016T120419Z with two runtime files: the registration definition and PWA worker.
- Private backup: `/var/www/html/artcare/.local-backups/elderly-support-paper-details-20261016T120419Z`.
- Patch, checksums and verification: `storage/app/elderly-support-paper-details-20261016/` on mamserver; `outputs/elderly-support-paper-details-20261016/` locally.
- No migration, database rewrite, environment change, route change or service restart. All 94 existing and 25 Elderly routes remain identical; Apache and both tunnel process IDs are retained.
- Validation: 33 registration backend checks, 6 core checks, 7 focused Chrome scenarios and 24 local origin checks passed. Live read-only origin checks also passed 24/24. Write tests used disposable localhost and synthetic data.
- Worker: `elderly-support-shell-v7-registration-details-20261016`. Save current work and refresh online to obtain the updated form. The 36-file full runtime backup is aligned with the installed source.

## Affirmative / negative answer codes

Both forms now save affirmative answers as integer 1 and negative answers as integer 2. HTML option values are `1` and `2`; labels remain readable, and unanswered controls remain blank/null. Existing text-valued records, queues, events and receipts are interpreted through explicit aliases, preserving their meaning and retry fingerprints. See [ANSWER_CODES.md](ANSWER_CODES.md).

- Registration definition version 5; follow-up definition version 2. Applies to 26 visible selects and the hidden historical caregiver-family field; sex and other category values are retained.
- Deployed at 20261016T123619Z with 11 Elderly-owned runtime files. Private source backup: `/var/www/html/artcare/.local-backups/elderly-support-answer-codes-20261016T123619Z`.
- Server staging/results: `storage/app/elderly-support-answer-codes-20261016/`; local copy: `outputs/elderly-support-answer-codes-20261016/`.
- No migration, bulk data rewrite, encryption-secret/environment change, route change or service restart. All 94 existing and 25 Elderly route definitions remain identical; Apache and both Cloudflare process IDs are retained.
- Validation: 43 registration backend, 38 follow-up backend, 8 core, 60 Chrome browser and 24 local origin checks passed. Live origin checks passed 24/24. Write suites used disposable local MySQL and synthetic records.
- Server reads expose numeric codes for historical encrypted answers; new writes persist numeric codes with their current definition version. Existing historical ciphertext is not rewritten in bulk. Frozen operations retain their original request bodies for safe retries.
- Old pages receive a no-store refresh-required response for data exchange. Save current work and refresh online; pending work remains available. Browser export is schema version 3 with `answer_code_version: 1`.
- Worker: `elderly-support-shell-v8-answer-codes-20261016`. Full local and remote runtime backups contain the same 36 installed files with matching SHA-256 checksums.

## Data dictionary download

All four registration/follow-up pages now include **Download data dictionary (Excel)**. The same non-personal workbook covers both forms and is cached for offline download. It includes 62 registration rows (58 form fields, status and three compatibility aliases), 37 follow-up rows (36 fields and status), 99 value-code entries, a guide and record/export metadata. English/Burmese labels, typed values, requirements, conditional chains, validation and source references are included. See [DATA_DICTIONARY.md](DATA_DICTIONARY.md).

- Deployed at 20261016T124954Z with three runtime files: the workbook, shared form shell and PWA worker.
- Private backup: `/var/www/html/artcare/.local-backups/elderly-support-dictionary-20261016T124954Z`.
- Server staging/results: `storage/app/elderly-support-dictionary-20261016/`; local copy: `outputs/elderly-support-dictionary-20261016/`.
- No migration, record rewrite, configuration/secret change, route change or service restart. All 94 existing and 25 Elderly routes remain identical, with the same Apache/tunnel process IDs.
- Verification: 734 read-only workbook checks against current definitions; rendered workbook sheets and desktop/mobile button layout reviewed; five Chrome scenarios passed, including identical online and offline downloads from each of the four pages. Local and live origin checks passed 25/25. No patient test record was written.
- Worker: `elderly-support-shell-v9-data-dictionary-20261016`. Save current work and refresh online to load the download button and cache the dictionary.
- The full runtime backup now includes 37 files. The XLSX checksum and source definition hashes are retained in the dictionary manifest. The local builder and verifier regenerate/audit it when the forms change.

## Monthly report view and Excel export

The navigation now includes **Monthly report**, calculated from saved registration and monitoring records using the source workbook’s 15 indicators. Month/year and All saved/Completed only filters apply to both the view and export. The exported `Monthly_report` sheet follows the source layout, and a second sheet documents definitions and data-quality notices. See [MONTHLY_REPORT.md](MONTHLY_REPORT.md) for exact period, repeat-visit and current-outcome rules.

- Deployed at 20261016T131123Z with 12 application files (8 new).
- Private backup: `/var/www/html/artcare/.local-backups/elderly-support-monthly-report-20261016T131123Z`.
- Server staging/results: `storage/app/elderly-support-monthly-report-20261016/`; local copy: `outputs/elderly-support-monthly-report-20261016/`.
- No database migration, case write, environment change, cache clear or service restart. All 94 unrelated routes and 25 pre-existing Elderly routes were preserved; three report routes bring Elderly routes to 28.
- Local verification: 43 registration regression checks, 42 report backend checks, 10 report browser scenarios, 5 existing dictionary browser scenarios, 100 read-only Excel/source checks. Export and mobile screenshots were visually reviewed. All 30 read-only origin checks passed.
- Worker: `elderly-support-shell-v10-monthly-report-20261016`. Save current work and refresh online to obtain the new navigation. Only the empty report shell/static assets are cached; figures and exports require an online authorized session.
- A read-only production calculation/export check passed on `MAM_NAP` for both filters, with all 15 Excel totals matching and its private temporary file removed. HTTPS still presents the existing Cloudflare Access sign-in (TLS verification passed); an authenticated production browser session remains user-controlled.
- Local and remote full runtime archives/manifests now contain 45 files. Production data is never included in these archives.

## Browser Excel export in source column order

**Export browser records (Excel)** now downloads exactly `Register` and `Fup_Checklist`, with source headers/order in the first 49 / 35 columns and added form fields/status afterward. It includes this browser account’s saved data and pending changes, works offline, and contains no report sheet. IDs/phones stay text, dates are sortable, binary answers remain numeric 1/2, and source year/month helpers have cached formulas. See [BROWSER_EXPORT.md](BROWSER_EXPORT.md). The dictionary was updated to version 1.1 for the new export format.

- Deployed at 20261016T150058Z with nine application files (four new).
- Private backup: `/var/www/html/artcare/.local-backups/elderly-support-browser-excel-20261016T150058Z`.
- Server staging/results: `storage/app/elderly-support-browser-excel-20261016/`; local copy: `outputs/elderly-support-browser-excel-20261016/`.
- No database mutation/migration, environment change, route change, cache clear or service restart. The 94 unrelated and 28 Elderly routes remain unchanged, as do all three service process IDs.
- Local checks: 43 backend regressions, six browser Excel scenarios (including four offline exports), eight registration/caregiver regression scenarios, five dictionary browser scenarios, 716 source/Excel checks across six synthetic workbooks, and 734 dictionary checks. Both exported sheet previews and changed dictionary metadata were reviewed. All 32 read-only live origin checks passed.
- Worker: `elderly-support-shell-v11-browser-excel-20261016`. Save current work and refresh online to load the Excel writer and new button. The module-owned ExcelJS 4.4.0 bundle and upstream MIT license are included locally; no CDN is used. Case workbooks never enter Cache Storage.
- Local and remote full runtime backups/manifests now contain 49 files, verified against deployed runtime hashes. Production cases and secrets are not in those archives.

## Automatic program IDs and General ID validation — 17 October 2026

New registration IDs are read-only and assigned from the account clinic: 71/72/81 → HTY, 73 → SPT, 84 → SDG, 74 → TL. Each area/year has its own shared five-digit sequence, continuing existing/deleted/reserved numbers. The browser reserves up to ten UUID-bound IDs for offline use; exhausted offline drafts receive a canonical ID during parent-first sync. Existing IDs stay unchanged. General / clinic ID, when supplied, accepts exactly 10, 11 or 12 digits in both forms and preserves leading zeros. See [AUTOMATIC_IDS.md](AUTOMATIC_IDS.md).

- Applied at 20261016T235222Z (UTC); 18 application files, including three new files.
- Private source backup: `/var/www/html/artcare/.local-backups/elderly-support-auto-ids-20261016T235222Z`. Staging/results: `storage/app/elderly-support-auto-ids-20261017/`; local copy: `outputs/elderly-support-auto-ids-20261017/`.
- Ran only `database/migrations/2026_10_17_000300_create_elderly_support_program_ids_table.php` with `--database=MAM_NAP --path=... --force`. It adds `elderly_support_program_ids` and its uniqueness constraints, bringing the module to seven tables. No existing table was altered, no other pending migration ran, and no production test record or ID reservation was created by verification. Preserve the reservation ledger after IDs are issued, including when reverting application code.
- All 94 unrelated and 28 pre-existing Elderly routes were preserved; the new authorized reservation endpoint brings Elderly routes to 29. No environment change, user/password update, cache clear or service restart. The user changed their own account clinic; the read-only live check confirms it is now mapped.
- Verification: 39 allocation checks including parallel processes and the final partial serial batch; 11 browser scenarios including all mappings, multiple tabs, lost responses, offline reload, exhausted pool and follow-up identity; 43 registration and 38 follow-up backend regressions; nine core tests; five dictionary browser scenarios and 734 dictionary checks. All 33 live origin checks and the read-only migration/mapping/validation check passed. HTTPS TLS validation and tunnel readiness passed.
- Definitions: registration 6, follow-up 3; dictionary 1.2; worker `elderly-support-shell-v12-automatic-ids-20261017`. Save work and refresh online.
- Full local and remote runtime manifests/archives now contain 52 files with matching installed-source hashes. No live cases, browser keys or production secrets are in the runtime archives.

## Larger form text and orange Burmese — 17 October 2026

Registration and follow-up pages, their management pages and details now use text 2px larger. English labels are 15px, controls 16px, and Burmese source labels/answers/content are emphasized at 18px in dark orange `#b45309`. English-only source labels stay neutral. Language classes are applied by script detection and do not change saved values. Line spacing accommodates Burmese glyphs and mobile wrapping. Scope is the four entry/management views; the monthly report keeps its existing typography.

- Applied at 20261017T000629Z (UTC), six presentation files. Private backup: `/var/www/html/artcare/.local-backups/elderly-support-form-type-20261017T000629Z`.
- Staging/results: `storage/app/elderly-support-form-type-20261017/`; local copy: `outputs/elderly-support-form-type-20261017/`.
- Browser measurements verified the exact +2px increase, 18px orange Burmese, neutral English-only source labels, both forms at desktop/390px phone widths, typed text and dropdown answers, and offline reload. Screenshots were reviewed; no JavaScript errors. All 33 read-only origin checks passed.
- No database migration, schema/data/routing/environment change or service restart. Existing Apache and both tunnel process IDs remained unchanged.
- Worker: `elderly-support-shell-v13-form-type-20261017`. Stylesheet and app script URLs are versioned. Save open work and refresh online. Full local/remote runtime backups remain 52 files with matching source hashes.


## Explicit save actions — 17 October 2026

Registration opening/reloading previously consumed a reserved number without creating a patient record. New forms now display the account area/year and assign a serial only after the user explicitly selects Save draft or Complete & save and field validation succeeds. Neither form submits on Enter in an input. Save actions freeze the controls and ignore duplicate clicks while in progress. Saved registration IDs and existing reservations are retained; unused reserved numbers can still cause gaps across devices, so the serial is not an enrollment count. Offline drafts without an ID pool can still be saved and receive their ID on explicit sync.

Verified with 11 browser scenarios (including both forms, no-save interactions, invalid answers, duplicate clicks, shared tabs, offline saves, lost reservation acknowledgement and parent-first sync), 39 server allocation checks and 9 core checks. Worker cache: `elderly-support-shell-v14-explicit-save-20261017`. Targeted deployment changes four runtime files; no migrations, production data changes, environment changes or service restarts. Full runtime backup remains 52 files.


## Manual Elderly program IDs — 20 October 2026

New registrations use an E prefix with no separators: HTY + year 26 + user serial 1 is stored as `EHTY2600001`. Area and year are selected independently of the account clinic; serial 1–99999 is entered manually and padded to five digits. No new IDs are allocated or reserved. The old reservation URL returns a reload message without writing. Existing IDs, UUIDs, old numbered offline drafts and follow-up links remain compatible. Server-accepted IDs stay fixed; unsynced manual IDs can be corrected after duplicate validation. Duplicate IDs are rejected, including concurrent submissions and reuse of deleted IDs. Save buttons remain explicit.

Registration schema 7; follow-up schema 3; dictionary 1.3; worker `elderly-support-shell-v15-manual-ids-20261020`. The Excel source layout remains unchanged. Verification: 43 registration backend checks, 41 manual-ID checks including competing processes, 38 follow-up checks, 42 report checks, 10 core checks, 13 manual-ID browser scenarios, 734 dictionary checks, 5 dictionary download browser scenarios and 33 origin checks. Targeted application deployment only: no migrations, database cleanup, test records, environment changes or service restarts. Updated runtime sources and their private backup remain aligned locally and on mamserver.


## Combined caregiver card — 20 October 2026

Merged the former 04 Caregiver details into the former 08 Requested support card. Support questions appear first, followed by all eleven caregiver fields. The combined title is Requested support and caregiver details. Cards and matching navigation now run 01–09: the combined card is 07, Assessment and approval is 08, and Program outcome is 09. Field keys, validation, conditional questions and recorded values are unchanged. Registration definition version 8; dictionary 1.4; worker `elderly-support-shell-v16-caregiver-card-20261020`. The five-file runtime patch requires no migration, case writes, environment update or service restart. Layout reviewed on desktop and a 390 px phone viewport; dictionary verification passed 734 checks.


## Remove follow-up Distribution card — 20 October 2026

Removed the former 06 Distribution card from follow-up entry and its navigation. Collection details is now 06 and the form has six cards. The five distribution fields remain hidden in the payload schema so opening, editing and offline saving old follow-ups retains their amounts, dates and distributor. Existing report and Excel source fields remain compatible. New entries do not ask for distribution values. Follow-up definition version 4; registration version 8; dictionary 1.5; worker `elderly-support-shell-v17-followup-layout-20261020`. Verified six cards and matching navigation, absence of visible distribution inputs, retention of all five old values after an offline edit/save, phone layout and 739 dictionary checks. Five runtime files change; no migrations, database cleanup, environment changes or service restart.


## Caregiver question position — 20 October 2026

Moved only Has a current caregiver directly after Disability category in card 03 Health and care. Remaining caregiver inputs stay in card 07 and retain their existing conditions. No field key, answer value, validation or saved data changes. Registration schema 9; follow-up schema 4; dictionary 1.6; worker `elderly-support-shell-v18-caregiver-position-20261020`. Verified the single question's DOM position, cross-card Yes/No visibility and desktop/phone layouts; dictionary verification passed 739 checks. Five runtime files change; no migration, case writes, environment update or service restart.


## Browser-only registration lookup for follow-up — 20 October 2026

Added Go to follow-up beside the full ID in registration Identity. It checks an exact full-ID match in the current browser account, then opens a new checklist linked by that saved registration's UUID. Its saved identity/contact snapshot is copied without saving either form. Follow-up Select registration now contains only the full-ID input and Find registration action, plus selected-record confirmation text. Removed the source selector, registration list and pagination. Blank, partial, name and clinic-ID queries do not match; casing/outer whitespace are tolerated. New selection and saved-visit opening never fetch missing registrations automatically. Use the existing explicit Download action to populate the browser first.

Deleted, pending deletion, unreadable, conflicting or ambiguous browser IDs are blocked. Saved visit parent UUIDs remain fixed. Repeating a search for the same parent preserves visit answers; changing parent protects unsaved answers with the existing discard flow. The lookup, ID shortcut and explicit saves work offline. No patient row is created by a lookup or navigation. Worker `elderly-support-shell-v19-browser-lookup-20261020`; schema/dictionary versions remain unchanged. Verified 12 browser scenarios, including absent server-only IDs, cross-account records, duplicates, legacy IDs, missing cached parent, offline phone use and no registration API lookup, plus 33 read-only origin checks. Four runtime files change; no migration, database cleanup, environment update or service restart.


## Edit registrations from Identity — 20 October 2026

Added Find registration to edit beside Go to follow-up in registration Identity. It matches the composed full ID against saved registrations in the current browser account and loads the existing record into the same form, with its UUID, revision, server version and saved values. Cancelled discard confirmation preserves unsaved answers. Pressing Find again while already editing that registration preserves current edits. Missing, deleted, pending deletion, unreadable, conflicting and ambiguous IDs remain blocked by the shared lookup. Saving uses the original UUID, updating its browser row and existing server version on explicit Sync. No lookup or record loading creates a row or saves changes. Cached records and unsynced drafts can be edited offline; server-accepted IDs stay fixed.

Worker `elderly-support-shell-v20-identity-edit-20261020`; schema and dictionary versions remain unchanged. Verified eight Identity-edit browser scenarios, including a real disposable server update with one matching registration, offline edits, unsynced draft updates and no implicit record fetch, plus all twelve follow-up lookup regressions and 33 origin checks. Four runtime files change; no migrations, production test data, database cleanup, environment updates or service restart. Local and remote runtime backups remain aligned.

## Calendar and typed date entry — 20 October 2026

Applied 20261020T035950Z with private server backup `/var/www/html/artcare/.local-backups/elderly-support-date-inputs-20261020T035950Z`. Nine Elderly runtime files changed. Registration, follow-up and visit-date filters now offer a native calendar beside DD-MM-YYYY text entry. DD-MM-YY expands to 2000–2099; compact six/eight-digit and legacy slash entry are accepted. Valid typed dates normalize on blur; incomplete/impossible dates are retained for correction. Original source date hints are rendered with hyphens on entry forms.

Payload/API dates remain ISO YYYY-MM-DD. Manual program IDs, explicit saving, record UUIDs, historical data and source-based Excel date formatting are preserved. Dictionary 1.7 documents the new entry format; form schemas stay registration 9 / follow-up 4. Worker cache: `elderly-support-shell-v21-date-inputs-20261020`.

Validation: 11 core tests, 8 date browser scenarios, 12 browser parent-lookup scenarios, 8 identity-edit scenarios, 739 dictionary checks, PHP/JS syntax checks and 33/33 read-only live-origin checks. Calendar popup and 390px layout reviewed; offline edit/reload and ISO browser storage verified using disposable local fixtures only. Production routes (94 existing + 29 Elderly), environment and service PIDs unchanged. No migrations or service restarts. Full 52-file runtime archive/stage refreshed on the workstation and server.
