Skip to content

issues Search Results · language:Dune language:Python language:HTML language:JavaScript language:JavaScript language:HTML

Filter by

47M results  (750 ms)

47M results

Part of #5170 — Control Room v2. Depends on A5. Per the user s condition: per-session activity must NOT be lost — surface it inside the Control Room. Scope - Remove the standalone per-session Control ...
control-room-v2

Part of #5170 — Control Room v2. Depends on A1 (A4 for live data). Build the Control Room section matching the north-star HTML brief. Scope - New section/route reachable from chroxy nav (the Control ...
control-room-v2

Part of #5170 — Control Room v2. Depends on A1, A3. Wire the survey to the WS protocol. Scope - New handler module (e.g. handlers/control-room-handlers.js): host_status_request → resolve repo set ...
control-room-v2

Part of #5170 — Control Room v2. Depends on A2. Given the repo set, produce a RepoStatus per repo. Scope - For each repo (injection seams _execFile/_now; never call real git/gh in tests): - ...
control-room-v2

Part of #5170 — Control Room v2. Depends on nothing (pure server util). Resolve the set of repos the Host Status survey covers. Scope - New module (e.g. packages/server/src/control-room/repo-set.js): ...
control-room-v2

Observed problem During the #302–#305 robustness goal, three avoidable rework cycles shared one root cause: authoring into a constrained/gated surface before checking the constraint, so an existing gate ...

Part of #5170 — Control Room v2. Add the wire contract for the Host/Repo Status Control Room. Scope - New @chroxy/protocol Zod schemas + TS types: - host_status_request (client → server): { ...
control-room-v2

- Missing benchmarks on existing trained models - Missing evidence on current observations

Motivation When using the userflow api programatically we don t have a way to cleanup in case of cancelation or error. Idealy the API exposes some destruction or dispose logic to avoid having to wait ...

Why taOS integrates many fast-moving third-party upstreams. Missing a new feature we could adopt, or a breaking change heading our way, is a real cost. We need a tracked inventory of what we depend on ...
Issue origami icon

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 Issues
ProTip! Restrict your search to the title by using the in:title qualifier.
Issue origami icon

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 Issues
ProTip! Restrict your search to the title by using the in:title qualifier.