- 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
- 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
- replace .opencode/agents/*.md with the cleaned alkssh versions,
adapted to alkforge constraints (coordinator prompt, implementation
conventions, poc dir name, fail-closed feature wording)
- adopt the alkssh sdd_process.md (project name alkforge)
- write AGENTS.md for the assembly: family stack conventions,
no-deformation rule, alkvault/no-env posture, fail-closed door
features, alkgen SSR rules, license hygiene, and the em-dash rule
(convention 16)
- placeholder README pending the 0.1.0 push
Verified: no em dashes or spaced-hyphen separators in AGENTS.md,
README.md, docs/, .opencode/agents/
glm-5.3-flash