alkdev/alkforge
6
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
6 Commits 1 Branch 0 Tags
main
Commit Graph
6 Commits
Author SHA1 Message Date
glm-5.3-flash 92519fa0c9 docs: de-bias the deployment walk (usage-through-the-incumbent is not needs) 
- add sect 11 correction lenses: three meanings of zero usage,
  residue-vs-workflow (branches are core SDD scaffolding, stale
  branches are cleanup debris), no incumbent surface-shape
  inheritance (alkcall ACL model, not gitea's anonymous OpenAPI),
  workarounds are unmet-need signals, the primary user (the SDD
  workflow) is invisible to telemetry; 0.1 = day-to-day replication,
  gitea catalog is a selective long-term backlog
- re-bucket: branching load-bearing (was inertia residue); stale
  branches deferred as per-branch migration decisions
- new finding (owner-stated): push-mirrors to GitHub for all public
  OSS repos, currently half-implemented with a plaintext PAT on
  gitea; alkforge posture = alkvault reference + assembly-layer
  bearer injection (alkhttp precedent); migration step added
  (enumerate + rotate, never copy); new OQ-FG-11 seeds the 0.1
  scope question
- clarify why issues/PRs/wiki/CI were unused: in-session workflows
  and distrust of gitea, not no-need-forever
 2026-11-07 14:30:22 +00:00
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
glm-5.3-flash 95399b46a2 chore(process): adopt family collaboration setup mirrored from alkssh 
- 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/
 2026-11-07 06:39:44 +00:00
glm-5.3-flash 7d70bfadd5 init 2026-10-25 02:35:08 +00:00