Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 77 Pull Requests 10 Actions Packages Projects Releases Wiki Activity

Web Console: Project registry API evolution (Phase 1) #635

New Issue
Open
opened 2026-07-10 14:38:50 -05:00 by jcwalker3 · 1 comment
jcwalker3 commented 2026-07-10 14:38:50 -05:00
Owner
Copy Link
Copy Source

Problem statement

MVP project registry (#427) serves list/detail from webui/data/projects.registry.json. The console needs a stable project registry API with project status, guided onboarding fields, and multi-project readiness for traffic-control and allocator-aware operators.

User and operational impact

Operators cannot programmatically inventory projects or see onboarding gaps; multi-repo workflows stay ad hoc.

Scope

  • Evolve GET /api/projects → versioned API with status, remotes/orgs/repos, onboarding checklist state, optional last-seen health.
  • Keep file-based registry compatible or migrate schema with version field.
  • Read-only in Phase 1.
  • Document guided onboarding steps as structured data.

Explicit non-goals

  • No full multi-tenant SaaS admin.
  • No secrets in registry JSON.
  • No LLM work assignment from registry alone.

Required implementation investigation

webui/project_registry.py, project_views.py, projects.registry.json, #427, #631, #632, multi-project notes in observability ADR.

Proposed architecture or implementation direction

Schema version bump if needed; DTO with status, onboarding[], remote links; validate on load fail-closed.

Security and workflow-safety requirements

No credentials in registry; redacted connection status only.

Acceptance criteria

  1. Versioned project registry API documented.
  2. Status + onboarding checklist exposed.
  3. Invalid registry fails closed with actionable error.
  4. Tests cover valid registry, missing project, schema validation.
  5. HTML views remain compatible or share DTO.

Required tests

Registry load/validate tests; API route tests.

Observability and audit requirements

Registry load failures optional health dependency.

Dependencies and linkage

Canonical issue state

STATE: ready-for-author
WHO_IS_NEXT: author
NEXT_ACTION: Evolve project registry API + tests
NEXT_PROMPT: Author implements registry API evolution only; PR; stop

Required final evidence

PR with schema, API, tests, docs.

Required final response and handoff expectations

Brief PR handoff to reviewer.

## Problem statement MVP project registry (#427) serves list/detail from `webui/data/projects.registry.json`. The console needs a stable **project registry API** with project status, guided onboarding fields, and multi-project readiness for traffic-control and allocator-aware operators. ## User and operational impact Operators cannot programmatically inventory projects or see onboarding gaps; multi-repo workflows stay ad hoc. ## Scope * Evolve `GET /api/projects` → versioned API with status, remotes/orgs/repos, onboarding checklist state, optional last-seen health. * Keep file-based registry compatible or migrate schema with version field. * Read-only in Phase 1. * Document guided onboarding steps as structured data. ## Explicit non-goals * No full multi-tenant SaaS admin. * No secrets in registry JSON. * No LLM work assignment from registry alone. ## Required implementation investigation `webui/project_registry.py`, `project_views.py`, `projects.registry.json`, #427, #631, #632, multi-project notes in observability ADR. ## Proposed architecture or implementation direction Schema version bump if needed; DTO with `status`, `onboarding[]`, remote links; validate on load fail-closed. ## Security and workflow-safety requirements No credentials in registry; redacted connection status only. ## Acceptance criteria 1. Versioned project registry API documented. 2. Status + onboarding checklist exposed. 3. Invalid registry fails closed with actionable error. 4. Tests cover valid registry, missing project, schema validation. 5. HTML views remain compatible or share DTO. ## Required tests Registry load/validate tests; API route tests. ## Observability and audit requirements Registry load failures optional health dependency. ## Dependencies and linkage * Parent: #631 · Extends: #427 · Related: #632 ## Canonical issue state ```text STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Evolve project registry API + tests NEXT_PROMPT: Author implements registry API evolution only; PR; stop ``` ## Required final evidence PR with schema, API, tests, docs. ## Required final response and handoff expectations Brief PR handoff to reviewer.
jcwalker3 added the type:featurestatus:readyworkflow-hardeningdashboard labels 2026-07-10 14:38:51 -05:00
jcwalker3 commented 2026-07-10 14:49:14 -05:00
Author
Owner
Copy Link
Copy Source

Canonical Issue State

STATE:
ready-for-author

WHO_IS_NEXT:
author

NEXT_ACTION:
Implement project registry API evolution; link PR to vision #652 and roadmap #653 Phase 1

NEXT_PROMPT:

AUTHOR prgs Gitea-Tools. Implement #635. Vision #652 · Roadmap #653 Phase 1 · Umbrella #631 · Extends #427. Lock; branches/; PR; stop. Closing ≠ #652 complete.

WHAT_HAPPENED:
Linked to #652/#653. Not recreated.

WHY:
Initial batch linkage.

RELATED_ISSUES:
#652 #653 #631 #427

RELATED_PRS:
none

BLOCKERS:
none

VALIDATION:
existing retained

LAST_UPDATED_BY:
jcwalker3 / prgs-author / author / 2026-07-10

## Canonical Issue State STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Implement project registry API evolution; link PR to vision #652 and roadmap #653 Phase 1 NEXT_PROMPT: ```text AUTHOR prgs Gitea-Tools. Implement #635. Vision #652 · Roadmap #653 Phase 1 · Umbrella #631 · Extends #427. Lock; branches/; PR; stop. Closing ≠ #652 complete. ``` WHAT_HAPPENED: Linked to #652/#653. Not recreated. WHY: Initial batch linkage. RELATED_ISSUES: #652 #653 #631 #427 RELATED_PRS: none BLOCKERS: none VALIDATION: existing retained LAST_UPDATED_BY: jcwalker3 / prgs-author / author / 2026-07-10
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
No labels dashboard status:ready type:feature workflow-hardening
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#635