Stage 5: gitea push + secret scan evidence

This commit is contained in:
krisf committed 2026-10-08 23:01:21 -04:00
1 parent e25dd4e0a1
commit 4f1207b1b8
1 file changed
+5
+5
View File
@@ -45,3 +45,8 @@
- Vision card: manifest + interest/province scoring, image with gradient fallback.
- `tests/ui.smoke.js` — headless DOM shim driving the full flow: **17/17 PASS** (caught & fixed 3 real bugs: missing get/set on assumptions step, SVG path helper signature, stamp rounding).
- Served smoke: python http.server 8099 → /, css, js, manifest, png all 200.
## Stage 5 — Gitea ✅
- Repo `krisf/retire-planner` created via Gitea API (Basic auth from `~/.git-credentials`, token never printed; API-token scheme returned 401 → Basic used, documented). `git push -u origin main` → `* [new branch] main -> main` on https://gitea.krisforbes.ca/krisf/retire-planner.git.
- Secret scan: `git grep -F "<nano key value>"` and `-F "<gitea token>"` over `git rev-list --all` → **0 hits** (clean). The plan's pattern-regex grep hits only the literal recipe strings inside the committed PLAN.md/REPORT.md + `scripts/gen_all.sh` (which *reads* the key from `~/.hermes/.env` at runtime, never embeds it). Deviation noted: plan's grep is self-contradictory (committing PLAN.md is also required and PLAN.md contains the pattern strings).
- `.gitignore` excludes `.fetch/`, `dsh-run.log`, duplicate `site/vision/*.jpeg`.