3 Commits

Include renames

Author	SHA1	Message	Date
glm-5.3-flash	17e041e149	docs: host-access pass closes the deployment walk residues ... - 52 repos (35 public + 17 private incl. alkfamily): both halves of ADR-002's scope sentence are already operational; new-repo default is private - visit patterns: web surface is crawler/scan noise (42k reqs, ~12.8k IPs over 2 days); real git transport is near-100% SSH - non-git SSH usage: none authorized in 72h; pure git door - key inventory: ~10 accounts, 12 ed25519 keys, no tokens/webhooks/ protected branches; DB-verified zero usage of issues/PRs/LFS/ actions across both halves - migration sizing corrected: ~158 MB git on disk (DB size column stale); backup locations remain a cutover-plan verification - OQ-FG-09 gains a live precedent: blob-heavy crawls burned gitea CPU until bounded	2026-11-07 13:39:39 +00:00
glm-5.3-flash	620a41c6a2	docs: deployment walk enumerates the live gitea surface (OQ-FG-01) ... - behavior-only walk of git.alk.dev (gitea 28.3.0): findings in docs/research/deployment-walk.md - headline: forge is a git host + public landing page only (issues/ PRs/wiki/releases/LFS/CI all zero-usage inertia); whole-org anonymous read is the operative grant; single-branch direct-push model by per-agent accounts; tags are the release surface - phase-0.md: sect 3 filled with summary + link, OQ-FG-01 resolved with residues, asks list gains the verified web-browse-queries item, POC item 1 marked done, checklist item checked	2026-11-07 13:30:59 +00:00
glm-5.3-flash	e6867eaaed	docs(research): draft phase 0 findings ... - objective and settled stack (family ADR-002, published crate map) - load-bearing gitea surface template with walk rules (OQ-FG-01) - provisional needs-to-stack mapping and draft permission posture - upstream asks list draft (OQ-07 items per door) - seeded open questions OQ-FG-01..10, POC candidates, and the phase 0 convergence checklist Verified: dash hygiene check clean	2026-11-07 06:39:44 +00:00