docs(deploy): finalize publication evidence

This commit is contained in:
NuklearRabbit
2026-08-02 02:09:50 +02:00
parent b0dda775e6
commit 737fc33394
2 changed files with 21 additions and 11 deletions
+16 -5
View File
@@ -3,9 +3,9 @@
## Outcome
- Deployment: **PASS**
- Gitea publication: **BLOCKED — Chrome session is signed out**
- Intended Gitea URL: `https://gitea.itworx.tech/Jens/MobilityOps`
- Requested visibility: private (not yet created or verified)
- Gitea publication: **PASS**
- Gitea URL: `https://gitea.itworx.tech/Jens/MobilityOps`
- Visibility: private (verified in the Gitea web UI)
- Branch: `master`
- Verified baseline commit: `4bf9afbeff44088864e0844769d4dd0e4089d85b`
- Deployment implementation commit: `1e13943cffb2da8a328b5b1ea5e9b1fe73fdd774`
@@ -34,6 +34,19 @@ The existing SSH aliases resolve to the requested hosts and keys (`gitea.itworx.
for Gitea SSH and `unraid` for root access). No key was created, copied, or replaced.
The committed source was transferred from the workstation; Unraid has no Gitea key.
Repository publication used the SSH clone URL supplied by Gitea:
```bash
git remote add origin ssh://git@192.168.10.150:222/Jens/MobilityOps.git
git push -u origin master
git push origin --tags
```
Git and the Gitea web UI both verified `master` as the default branch, the full 15-commit
history, baseline commit `4bf9afbeff44088864e0844769d4dd0e4089d85b`, and zero tags.
The remote tree contains no `.env`, local database, `node_modules`, virtual environment,
test cache, build cache, Playwright output, or browser binaries.
```bash
git archive --format=tar.gz --output=<temporary-archive> <commit>
scp <temporary-archive> unraid:/mnt/user/appdata/mobilityops/.deploy/source.tar.gz
@@ -94,8 +107,6 @@ included here or in Git.
## Known limitations
- Gitea repository creation and web verification remain blocked until the requested Chrome
session is authenticated. SSH authentication itself is verified for user `Jens`.
- RAGcore and ITWorx MCP Hub are intentionally not connected yet.
- Demo authentication remains the accepted HMAC-cookie PoC mechanism.
- The dependency advisories already documented in final acceptance remain unchanged.