WIZ-5 Stack detection + starter-pack file #700
No reviewers
Labels
No labels
area:agents
area:dashboard
area:database
area:design
area:design-review
area:flows
area:infra
area:meta
area:security
area:sessions
area:webhook
area:workdir
security
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/claude-hooks!700
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "boss/676"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #676
Server-side stack detection scanning each watched repo's manifest files via
ForgePort.readFile, plus a staticconfig/starter-packs.jsonper stack.Test plan
bun test apps/server/src/http/handlers/onboarding-stack.test.ts— 18 passjust qa— typecheck + biome check + biome format + 3059 server tests all greenpackage.json+Cargo.toml→{ typescript: 0.5, rust: 0.5 }{}starter-packs.jsonparses + everyapplies_toreferences a real roleCI green. All ACs met: detect-stack endpoint with 60s cache + normalised weights,
{}on no-manifest, starter-packs file with 5 required stacks (typescript/rust/python/go/ruby), Zod schema with real-role enforcement, both routes wired correctly in main.ts.Nit (non-blocking):
DETECT_CACHE_TTL_MS_PLUS_ONEis hardcoded 60_001 in the test; if the handler TTL changes the test constant will not warn — worth exporting the constant, but not a blocker.