Follow-up to #137 (pending-task list redesign).
The #137 click-to-expand context row surfaces a task's parent-commit SHA and (for evaluator rows) the variant's work-branch name as text, because there is no browser-facing repo-browse URL contract in the web-ui today. The CLI exposes only an in-network --forgejo-url and an informational --clone-url (reference/services/web-ui/src/eden_web_ui/cli.py) — neither is a browser browse-URL.
To make the parent-commit / work-branch references clickable links into a repo browser (e.g. Forgejo's web view), the web-ui needs a browser-facing browse-URL contract:
- a new CLI flag / app-state value for the operator-facing repo-browser base URL (distinct from the in-network clone URL);
- template wiring in the expansion (and likely the executor/evaluator claim pages) to build
<browse-base>/commit/<sha> and <browse-base>/src/branch/<branch> links.
Adding this widens scope past #137's web-ui-module-only boundary (it introduces a new operator-facing config surface), so it was deferred per #137 plan §D.3 / §11.
Follow-up to #137 (pending-task list redesign).
The #137 click-to-expand context row surfaces a task's parent-commit SHA and (for evaluator rows) the variant's work-branch name as text, because there is no browser-facing repo-browse URL contract in the web-ui today. The CLI exposes only an in-network
--forgejo-urland an informational--clone-url(reference/services/web-ui/src/eden_web_ui/cli.py) — neither is a browser browse-URL.To make the parent-commit / work-branch references clickable links into a repo browser (e.g. Forgejo's web view), the web-ui needs a browser-facing browse-URL contract:
<browse-base>/commit/<sha>and<browse-base>/src/branch/<branch>links.Adding this widens scope past #137's web-ui-module-only boundary (it introduces a new operator-facing config surface), so it was deferred per #137 plan §D.3 / §11.