27 lines
3.8 KiB
Markdown
27 lines
3.8 KiB
Markdown
# Acceptance evidence, 2026-09-11
|
|
|
|
This audit updates stale Werkbaum explanations. It does not close the application goal or substitute automated tests for the remaining operator observations. The 2026-09-09 status audit remains a historical snapshot.
|
|
|
|
## Inspected evidence
|
|
|
|
- Git revision `ab2e3d5584c372a11226042974fdd958bef0b88c` contains invitation language selection, persisted invitation language, login-mail preference resolution and account initialization. Local service/migration tests and targeted browser evidence are recorded in `invitation-language.md`.
|
|
- Werkator's latest-build API reported that revision as successful, duration 646 seconds, artifact key `main_jvm-5c494a9689b3-2026-09-11T03_09_38.305683273Z-a8c726a36b04`. Its Firefox log reported 21 scenarios and 140 steps passed. The public `/api/v1/info` returned `0.1.95-SNAPSHOT`; no build remained active at that observation.
|
|
- The original automatic run had been missed although Gitea and the CI checkout contained the revision. The missing run was started through Werkator's existing origin-head build control after confirming no active build. This establishes successful build/deployment, not the cause or repair of the missed automatic trigger.
|
|
- `ReminderDispatcher`, `ReminderQueue`, `WebPushTransport` and `PushRuntimeConfiguration` implement delivery, scheduling, retry/ledger behavior and maintenance gating. `SettingsView` loads `push-settings.js`; the custom worker includes `push-worker.js`. These components are not missing implementation. `push-gherkin.md` records controlled service coverage; `web-push-transport.md` records production activation. Neither proves notification display on a physical phone.
|
|
- Gherkin suite classes and step definitions exist under `src/test/kotlin/de/javagil/werkjournal/acceptance`, and `tools/ci-jvm` runs them. WJ-033 remains physical notification/browser acceptance; WJ-024 remains provider-backup acceptance.
|
|
- Real-H2 rollback and release-tool boundaries are documented in `migration-rollback-acceptance.md`, `consecutive-rollback-acceptance.md`, `failed-rollback-acceptance.md`, `upload-activation-acceptance.md`, `ci-artifact-acceptance.md` and `deployment-failure-acceptance.md`.
|
|
- `docs/RUNBOOK.md` specifies concrete deployment paths, port, service, maintenance, operator backup/restore and recovery procedures. Its provider-restore section explicitly leaves raw provider snapshot retrieval and import acceptance open.
|
|
|
|
## Remaining evidence needed
|
|
|
|
| Requirement | Current evidence | Missing evidence |
|
|
| --- | --- | --- |
|
|
| Physical Android/PWA | Operator confirmed installed version 0.1.90 and correct petrol journal icon | Remaining real-device offline/draft/UI observations and device/browser details |
|
|
| Real email/account flow | Operator confirmed initial signup and a second invited account | Complete documented return-login/device acceptance; code-versus-link observations are not fully specified |
|
|
| Background push / WJ-033 | Implemented, deterministic service/worker coverage and server activation documented | Actual phone notification while backgrounded and dated click, including next-day opening |
|
|
| Hostsharing provider restore / WJ-024 | Operator backup/probe and automated rollback coverage | Representative provider snapshot retrieval, consistency and approved raw-tree restore/import exercise |
|
|
| Trixie | Migration checklist exists | Execution against the target upgraded host; no OS upgrade has been performed in this work |
|
|
| Release | Functional implementation and CI evidence above | Completion of the outstanding acceptance requirements |
|
|
|
|
No production data was changed by this documentation audit. No email, push, provider-support request or device interaction was initiated. No new tests were run for these text-only corrections; evidence scope remains the scope of the cited checks.
|