glm-5.3-flash
17e041e149
- 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
alkforge
The alk family's near-term assembly: a minimal forge replacing the
gitea deployment, built as an assembly on alkgit's core (family
ADR-002, /workspace/@alkdev/alkfamily/docs/architecture/decisions/002-alkforge-gitea-replacement.md).
It composes family crates rather than re-implementing them: alkgit (+ alkgit-substrate) as the git core, alkssh (git feature) and alkhttp as the transport doors, alkgen for server-side rendering, alkstore and alkblobs for persistence, alkvault for secrets, and alkcall as the substrate underneath. reverse-proxy fronts the deployment.
Status: SDD phase 0 (research docs only). See
docs/research/phase-0.md and the family docs for the current design
direction. The README proper gets written when the crate is near
publish (v0.1.0).
License: MIT OR Apache-2.0.