docs(polish): audit finale demo-afwerking
Verifies the actual branch HEAD against the deployed Unraid revision (they match) and corrects a one-commit-behind final-commit hash in artifacts/demo-release/final-summary.md (its own "record the hash" follow-up commit couldn't self-reference). Catalogues remaining MobilityOps/PoC mentions (including in knowledge-base procedure prose that gets quoted in answers), confirms no i18n exists, documents the Demo Guide's single-behaviour-at-all-desktop-widths gap, the inconsistent radio-vs-card decision styling in Data Quality, automation/ audit density, and exactly which dashboard rows aren't fully clickable. Notes the repository's primary branch is `master`, not `main`.
This commit is contained in:
@@ -8,10 +8,13 @@
|
||||
to `main`; no rebase/reset/squash/force-push; full git history preserved, as required)
|
||||
- **Start commit** (functional-completion baseline, already accepted):
|
||||
`e0c7ed60112510687627d20a957af91c8b9db7f8`
|
||||
- **Final commit**: `294a8176d196e42408c4e99c29ab142771fcec04` (the commit that added this
|
||||
file; a small follow-up commit records this hash explicitly, since a commit cannot
|
||||
self-reference its own hash — `git log -1` on this branch is the authoritative source
|
||||
if it has moved further since).
|
||||
- **Final commit**: `4a268c73515dc4f1d56c1aa2f231714654bffbb8` — verified via
|
||||
`git rev-parse HEAD` on `feat/mobilityops-functional-completion` and confirmed to match
|
||||
`/mnt/user/appdata/mobilityops/.deploy/source-revision` on the Unraid server exactly.
|
||||
(This corrects a self-reference gap in the immediately preceding pair of commits, which
|
||||
necessarily could not know their own hash at the time they were written; this is now
|
||||
the single, unambiguous, verified reference. The repository's primary branch is
|
||||
`master`, not `main` — no branch named `main` exists in this repository.)
|
||||
- **Live URL**: `http://192.168.10.150:1236`
|
||||
|
||||
## Demo organisation and context
|
||||
|
||||
Reference in New Issue
Block a user