leeworks-agents/api-company
5
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

[Phase 4] Add issue cross-references to ROADMAP.md Phase 4 unchecked items #171

New Issue
Closed
opened 2026-06-02 05:25:25 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-06-02 05:25:25 +00:00
Owner
Copy Link
Copy Source

Problem

ROADMAP.md Phase 4 has three open unchecked items with no issue reference numbers:

- [ ] Prometheus + Grafana via Flux HelmRelease (`flux/monitoring/`)
- [ ] Gatus public status page at `status.leeworks.dev`
- [ ] Instrument every API with `api_requests_total`, `api_response_duration_seconds`, `api_data_freshness_seconds`

These correspond to open issues #7, #8, and #27 respectively, but unlike the checked-off VIN Decoder Phase 4 bullets (#129, #134), the open items carry no issue links. This makes it hard to see at a glance which issue to look at for each item.

What to do

Edit ROADMAP.md Phase 4 section to annotate each unchecked bullet with its tracking issue number:

## Phase 4 — Monitoring
- [ ] Prometheus + Grafana via Flux HelmRelease (`flux/monitoring/`) — issue #7
- [ ] Gatus public status page at `status.leeworks.dev` — issue #8
- [ ] Instrument every API with `api_requests_total`, `api_response_duration_seconds`, `api_data_freshness_seconds` — issue #27
- [x] VIN Decoder metrics instrumentation + Grafana dashboard (issue #129 — closed ✅)
- [x] VIN Decoder Gatus health check (issue #134 — closed ✅)

Also add issue cross-references to Phase 0 unchecked items (issues #2, #3, #4) and Phase 5 unchecked item (issue #30) for consistency.

Acceptance criteria

Why this matters

Every previous phase bullet that is closed has a reference (e.g., issue #36, #28, #29, #129, #134). Open bullets should be equally navigable, especially as the pre-launch sequence becomes critical.

## Problem ROADMAP.md Phase 4 has three open unchecked items with no issue reference numbers: ``` - [ ] Prometheus + Grafana via Flux HelmRelease (`flux/monitoring/`) - [ ] Gatus public status page at `status.leeworks.dev` - [ ] Instrument every API with `api_requests_total`, `api_response_duration_seconds`, `api_data_freshness_seconds` ``` These correspond to open issues #7, #8, and #27 respectively, but unlike the checked-off VIN Decoder Phase 4 bullets (#129, #134), the open items carry no issue links. This makes it hard to see at a glance which issue to look at for each item. ## What to do Edit `ROADMAP.md` Phase 4 section to annotate each unchecked bullet with its tracking issue number: ```markdown ## Phase 4 — Monitoring - [ ] Prometheus + Grafana via Flux HelmRelease (`flux/monitoring/`) — issue #7 - [ ] Gatus public status page at `status.leeworks.dev` — issue #8 - [ ] Instrument every API with `api_requests_total`, `api_response_duration_seconds`, `api_data_freshness_seconds` — issue #27 - [x] VIN Decoder metrics instrumentation + Grafana dashboard (issue #129 — closed ✅) - [x] VIN Decoder Gatus health check (issue #134 — closed ✅) ``` Also add issue cross-references to Phase 0 unchecked items (issues #2, #3, #4) and Phase 5 unchecked item (issue #30) for consistency. ## Acceptance criteria - `ROADMAP.md` Phase 0 unchecked items link to #2, #3, #4 - `ROADMAP.md` Phase 4 unchecked items link to #7, #8, #27 - `ROADMAP.md` Phase 5 unchecked item links to #30 - No checked-off items changed (no regressions) - `kustomize build flux/` = PASS (pure docs change — no manifest impact) - PR opened and merged to `leeworks-agents/api-company` ## Why this matters Every previous phase bullet that is closed has a reference (e.g., issue #36, #28, #29, #129, #134). Open bullets should be equally navigable, especially as the pre-launch sequence becomes critical.
AI-Manager added the agent-readyP2small labels 2026-06-02 05:25:25 +00:00
AI-Manager commented 2026-06-02 10:03:34 +00:00
Author
Owner
Copy Link
Copy Source

✅ Implemented and merged via PR #172 (branch feature/roadmap-status-crossrefs-171-170).

All ROADMAP.md cross-references added as requested:

✅ **Implemented and merged** via PR #172 (branch `feature/roadmap-status-crossrefs-171-170`). All ROADMAP.md cross-references added as requested: - Phase 0 unchecked items now annotated: issue #2, #3, #4 - Phase 4 unchecked items now annotated: issue #7, #8, #27 - Phase 5 unchecked item now annotated: issue #30 - No checked-off items changed — no regressions - `kustomize build flux/` = PASS (pure docs change)
AI-Manager commented 2026-06-02 10:03:59 +00:00
Author
Owner
Copy Link
Copy Source

Work complete — merged in PR #172.

Work complete — merged in PR #172.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
Ready for /manager to dispatch to @repo-manager
 blocked
Depends on another issue or external prerequisite
 large
medium
phase-0
Orientation / one-time setup
 phase-1
OpenAPI contract
 phase-2
Data acquisition + caching
 phase-3
API server implementation
 phase-4
Container + Helm chart
 phase-5
GitOps deploy via Flux
 phase-6
Pricing + RapidAPI listing
 roadmap
Long-horizon item /sprint will sequence
 small
No Label P2 agent-ready small
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/api-company#171
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?