Files
MobilityOps/docs/HISTORY_SANITATION_REQUIRED.md

28 lines
2.2 KiB
Markdown

# History Sanitation Required
This hygiene campaign removed generated operational evidence and private development state from the current tree and replaced maintained deployment instructions with portable configuration placeholders.
## Removed or sanitized current-tree material
- `artifacts/**/final-summary.md` and `artifacts/deployment/unraid-summary.md` containing a private Gitea URL, private host address, live service ports and operator-specific deployment evidence;
- `artifacts/design-validation/current/*.png` generated browser baselines;
- temporary current-state, UX, integration, functional and server-baseline audit documents;
- `PROJECT_STATE.md`, `FILE_INDEX.md`, `MASTER_BUILD_PROMPT.md`, `CLAUDE.md` and `START_HERE.md` development/agent bookkeeping;
- concrete private deployment targets in the maintained Unraid and demo runbooks.
The former blobs and earlier revisions remain reachable from commits preceding this branch. A normal merge does not remove them from Git history.
| Path family | Information type | Known refs | Why history sanitation is required |
|---|---|---|---|
| `artifacts/**` | live deployment summaries, internal service URLs and generated screenshots | commits reachable from `master` before this branch | private infrastructure and uncurated operational evidence remain in old objects |
| `PROJECT_STATE.md` and removed agent/state docs | development chronology, operational endpoints and AI workflow context | earlier `master` commits | not product source and may disclose private topology |
| `deploy/unraid/README.md`, `docs/demo-release/demo-runbook.md` | former concrete host, public domain and automation endpoint | earlier `master` revisions | current text is portable but old revisions retain the original values |
`HISTORY_REWRITE_REQUIRED` before making the existing Git history public.
## Remaining visual review
The intentionally retained synthetic demo screenshots under `artifacts/demo-release/screenshots/` must receive an owner visual review for browser chrome, account identifiers, private URLs and infrastructure details. Unapproved images should be removed from the current tree and any future public history.
No refs were rewritten, force-pushed or deleted by this campaign.