issues Search Results · language:Dune language:Python language:JavaScript language:HTML language:JavaScript language:CSS
Filter by
48.9M results
What happened
The RED stage test-count gate failed with no_new_test_functions_committed: found 0, need = 6 for both task-1 and task-2.
Both lanes have 6 acceptance criteria, but the skeleton file written ...
datum-bug
Summary
Sealed acceptance s whole premise is that a non-coder operator can vouch for a held-out exam they cannot read, using
only the spec + the author s plain-English coverage summary (spec 2026-06-12-sealed-acceptance-design.md; ...
The gap
Engram ships the scripts but not the agent-driven workflows that orchestrate them. For MCP / Claude users (the no-token,
non-technical path from #4), most of the value is in those recipes — and ...
enhancement
insight-wave s READMEs and docs lead with DACH, but the platform is genuinely multi-market and multilingual — and
several market-aware plugins hide the capability entirely. This epic surfaces the real, ...
change-request
epic
Goal
Author the Kinds release/ doesn t ship yet, so comms/lex/supage stop hand-rolling ordinary build/docs/release
capabilities. Highest risk in the program — most target Kinds have no canary family, ...
epic:standardization
Goal
Add reproducible generated Kotlin types from the current v1 JSON Schemas so the future mobile runtime can depend on
schema-shaped contracts without hand-written drift.
Parent Epic
- #5
Acceptance ...
area:contracts
priority:p1
type:feature
Goal
Fold the ordinary capabilities consumers currently hand-roll into the shared workflows as parametrized inputs/hooks — so
the consumer de-fats to a thin caller. These are fold-ins (we already have ...
epic:standardization
Goal
Converge every consumer onto the v3 pull-model seed. The single highest-payoff move in the audit: it refreshes managed
CLAUDE.md markers, lefthook shape, and bin/check residue + retired jargon for ...
epic:standardization
Goal
Remove dead/duplicate consumer-side cruft the audit grep-confirmed unreferenced or superseded. No upstream work — each
workstream is one or more single-task consumer PRs. This is the zero-risk ground-clearing ...
epic:standardization

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.