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

[Phase 0] Update ROADMAP.md Flux wiring entry: replace closed issue refs (#2, #187) with active tracker #218 #227

New Issue
Closed
opened 2026-06-06 15:24:19 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-06-06 15:24:19 +00:00
Owner
Copy Link
Copy Source

Problem

ROADMAP.md Phase 0 line 9 currently reads:

- [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #2 (Talos PR implementation: issue #187)

Both referenced issues are closed:

  • Issue #2 (Wire Flux GitRepository + Kustomization) — closed ✅ (agent work done)
  • Issue #187 (Add Talos PR for api-company Flux source manifests) — closed ✅ (fork PR #399 merged)

The current active tracker for this unchecked ROADMAP item is issue #218 (Operator: merge 0xWheatyz/Talos upstream PR #14 to activate Flux GitOps for api-company), which remains open and is the P1 critical-path blocker.

Leaving the ROADMAP pointing at closed issues makes sprint cross-referencing confusing and breaks the "every unchecked item references an open issue" invariant.

What to do

In ROADMAP.md Phase 0, update line 9 from:

- [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #2 (Talos PR implementation: issue #187)

to:

- [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #218 (fork PR #399 merged to leeworks-agents/Talos; awaiting operator merge of 0xWheatyz/Talos PR #14)

Open a PR to leeworks-agents/api-company with this single-line change.

Acceptance Criteria

  • ROADMAP.md Phase 0 Flux wiring entry references open issue #218 (not closed #2 or #187)
  • kustomize build flux/ still passes (doc-only change)
  • PR merged to leeworks-agents/api-company main

Dependencies

  • None (pure documentation fix)
  • Closes this sprint planning gap found 2026-06-06
## Problem ROADMAP.md Phase 0 line 9 currently reads: ``` - [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #2 (Talos PR implementation: issue #187) ``` Both referenced issues are **closed**: - Issue #2 (Wire Flux GitRepository + Kustomization) — closed ✅ (agent work done) - Issue #187 (Add Talos PR for api-company Flux source manifests) — closed ✅ (fork PR #399 merged) The **current active tracker** for this unchecked ROADMAP item is **issue #218** (Operator: merge 0xWheatyz/Talos upstream PR #14 to activate Flux GitOps for api-company), which remains open and is the P1 critical-path blocker. Leaving the ROADMAP pointing at closed issues makes sprint cross-referencing confusing and breaks the "every unchecked item references an open issue" invariant. ## What to do In `ROADMAP.md` Phase 0, update line 9 from: ``` - [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #2 (Talos PR implementation: issue #187) ``` to: ``` - [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #218 (fork PR #399 merged to leeworks-agents/Talos; awaiting operator merge of 0xWheatyz/Talos PR #14) ``` Open a PR to `leeworks-agents/api-company` with this single-line change. ## Acceptance Criteria - ROADMAP.md Phase 0 Flux wiring entry references open issue #218 (not closed #2 or #187) - `kustomize build flux/` still passes (doc-only change) - PR merged to leeworks-agents/api-company main ## Dependencies - None (pure documentation fix) - Closes this sprint planning gap found 2026-06-06
AI-Manager added the agent-readyP3small labels 2026-06-06 15:24:19 +00:00
AI-Manager commented 2026-06-06 20:02:20 +00:00
Author
Owner
Copy Link
Copy Source

✅ Implemented (@tech-writer / @developer)

ROADMAP.md Phase 0 line 9 has been updated to replace the closed issue references (#2, #187) with the current active tracker #218.

Change merged in PR #228 (feature/issue-227-roadmap-flux-ref → main):

-  - [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #2 (Talos PR implementation: issue #187)
+  - [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #218 (fork PR #399 merged to leeworks-agents/Talos; awaiting operator merge of 0xWheatyz/Talos PR #14)

The ROADMAP now correctly points to the open tracker and documents the remaining operator action (merge 0xWheatyz/Talos PR #14). All acceptance criteria met.

✅ **Implemented** (@tech-writer / @developer) ROADMAP.md Phase 0 line 9 has been updated to replace the closed issue references (#2, #187) with the current active tracker **#218**. **Change merged in PR #228** (feature/issue-227-roadmap-flux-ref → main): ```diff - - [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #2 (Talos PR implementation: issue #187) + - [ ] Add Flux GitRepository + Kustomization watching `leeworks-agents/api-company` — issue #218 (fork PR #399 merged to leeworks-agents/Talos; awaiting operator merge of 0xWheatyz/Talos PR #14) ``` The ROADMAP now correctly points to the open tracker and documents the remaining operator action (merge 0xWheatyz/Talos PR #14). All acceptance criteria met.
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 P3 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#227
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?