issues Search Results · language:Dune language:JavaScript language:Java language:Java language:JavaScript language:HTML
Filter by
39.8M results
Purpose
Single tracking board for cooldown-phase execution status, dependencies, and next actions.
Current determination
Architecture proof: COMPLETE
Demonstration proof: COMPLETE
Controlled same-owner ...
cooldown
dependency-formation
priority:P0
status:active
Problem
The project includes local automation and browser-control surfaces. Even for a local-first tool, those endpoints should
have clear trust boundaries and defensive defaults.
Proposed implementation ...
Problem
Important runtime files such as data/surf-db.json are intentionally ignored, but a new contributor needs clear bootstrap
steps or fixtures to understand expected data shape.
Proposed implementation ...
Problem
Ports and service URLs are scattered across files and documentation. This makes local orchestration fragile and raises
the chance of mismatched docs.
Proposed implementation
Introduce a shared ...
Problem
The ML sidecar includes a SQLite schema, but runtime behavior still centers on JSON preview data and placeholder
forecasting. This limits reproducibility and auditability.
Proposed implementation ...
Problem
server.js is a large single file that combines routing, filesystem access, data shaping, automation hooks, and response
formatting. This increases blast radius for small changes.
Proposed implementation ...
Problem
The root index.html is over 5,000 lines and mixes markup, styling, and application logic. This makes review, testing,
and feature work unnecessarily risky.
Proposed implementation
Move reusable ...
Problem
apps/corridor-forge/server.js references report export files under apps/corridor-forge/exports/, but those assets are
absent from the repository. A fresh clone cannot reproduce that view or behavior. ...
Problem
The repo has several independent HTTP services, but there is no automated verification that they start, expose health
endpoints, or respond with expected baseline payloads.
Proposed implementation ...
Problem
The current GitHub Actions configuration assumes a conventional npm project, but this repository is a multi-service
prototype with standalone Node entrypoints and no root dependency manifest. ...

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.