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

Stand up registry.leeworks.dev container registry #4

New Issue
Open
opened 2026-05-18 21:20:04 +00:00 by 0xWheatyz · 33 comments
0xWheatyz commented 2026-05-18 21:20:04 +00:00
Owner
Copy Link
Copy Source

Per-API CI pipelines push images to registry.leeworks.dev/... — the registry needs to exist before any API can deploy.

Options

  1. Use Gitea's built-in container registry (per GITEA_CONTAINER_REGISTRY.md in 0xWheatyz/Talos) — likely best, no new infra
  2. Deploy distribution/distribution via Flux HelmRelease

Decide and document the choice in docs/registry.md. Then update Phase-4 docs in each API repo's ROADMAP.md to reference the right registry host.

Per-API CI pipelines push images to `registry.leeworks.dev/...` — the registry needs to exist before any API can deploy. ### Options 1. Use Gitea's built-in container registry (per GITEA_CONTAINER_REGISTRY.md in 0xWheatyz/Talos) — likely best, no new infra 2. Deploy `distribution/distribution` via Flux HelmRelease Decide and document the choice in `docs/registry.md`. Then update Phase-4 docs in each API repo's ROADMAP.md to reference the right registry host.
0xWheatyz added the roadmapphase-0 labels 2026-05-18 21:20:04 +00:00
AI-Manager added the P1agent-readymedium labels 2026-05-19 00:27:48 +00:00
AI-Engineer was assigned by AI-Manager 2026-05-19 05:05:09 +00:00
AI-Manager commented 2026-05-19 05:05:20 +00:00
Owner
Copy Link
Copy Source

Triage by @AI-Manager: Assigned to @AI-Engineer. Delegating to @architect agent.

This requires an architecture decision (built-in Gitea registry vs distribution/distribution) before implementation. The architect should evaluate both options, document the decision in docs/registry.md, and then implement.

Priority: HIGH (blocks API CI image pushes).

**Triage by @AI-Manager**: Assigned to @AI-Engineer. Delegating to @architect agent. This requires an architecture decision (built-in Gitea registry vs distribution/distribution) before implementation. The architect should evaluate both options, document the decision in docs/registry.md, and then implement. Priority: HIGH (blocks API CI image pushes).
AI-Manager commented 2026-05-19 10:07:02 +00:00
Owner
Copy Link
Copy Source

[Repo Manager Triage]

Priority: P1 (Phase 0 blocker)
Delegated to: @devops
Reason: Stand up container registry at registry.leeworks.dev. Evaluate Gitea built-in registry vs distribution/distribution. Infrastructure deployment.

This issue has been triaged and is ready for the assigned agent to pick up.

**[Repo Manager Triage]** Priority: P1 (Phase 0 blocker) Delegated to: @devops Reason: Stand up container registry at registry.leeworks.dev. Evaluate Gitea built-in registry vs distribution/distribution. Infrastructure deployment. This issue has been triaged and is ready for the assigned agent to pick up.
AI-Manager commented 2026-05-24 23:23:08 +00:00
Owner
Copy Link
Copy Source

✅ Decision documented in PR #20 (merged)

docs/registry.md is now on main with the architecture decision:

Decision: Use Gitea's built-in container registry (not a separate distribution/distribution deployment)

Rationale: No new infra, integrated auth, OCI-compliant, works natively with Gitea Actions CI.

Registry host: registry.leeworks.dev (proxied to gitea.leeworks.dev via Nginx Ingress)

Image naming: registry.leeworks.dev/leeworks-agents/:

All API repos' Phase 4 docs should reference: registry.leeworks.dev/leeworks-agents/{zip-enrichment,holidays,air-quality}:latest

Human operator action: Ensure Gitea packages are enabled (app.ini [packages] ENABLED=true) and add ingress for registry.leeworks.dev as described in docs/registry.md.

✅ **Decision documented in PR #20 (merged)** docs/registry.md is now on main with the architecture decision: **Decision: Use Gitea's built-in container registry** (not a separate distribution/distribution deployment) Rationale: No new infra, integrated auth, OCI-compliant, works natively with Gitea Actions CI. Registry host: registry.leeworks.dev (proxied to gitea.leeworks.dev via Nginx Ingress) Image naming: registry.leeworks.dev/leeworks-agents/<repo>:<sha> All API repos' Phase 4 docs should reference: registry.leeworks.dev/leeworks-agents/{zip-enrichment,holidays,air-quality}:latest **Human operator action:** Ensure Gitea packages are enabled (app.ini [packages] ENABLED=true) and add ingress for registry.leeworks.dev as described in docs/registry.md.
AI-Manager commented 2026-05-25 00:06:17 +00:00
Owner
Copy Link
Copy Source

📋 Agent cycle 2026-05-25 — @devops status update

Decision (from docs/registry.md): Use Gitea's built-in container registry — no new infra needed.

  • Registry host: registry.leeworks.dev (proxied via ingress to Gitea)
  • Image naming: registry.leeworks.dev/leeworks-agents/{zip-enrichment,holidays,air-quality}:latest

ACTION REQUIRED (human operator):

  1. Ensure [packages] ENABLED = true in Gitea app.ini
  2. Add DNS record: registry.leeworks.dev → cluster ingress IP
  3. Add Traefik/Nginx ingress rule: registry.leeworks.dev → Gitea service (for OCI package endpoints)
  4. Test: docker login registry.leeworks.dev with a Gitea token

Once the registry is reachable, all three API repo CI pipelines can push images and this issue can close.

📋 **Agent cycle 2026-05-25 — @devops status update** **Decision (from docs/registry.md):** Use Gitea's built-in container registry — no new infra needed. - Registry host: `registry.leeworks.dev` (proxied via ingress to Gitea) - Image naming: `registry.leeworks.dev/leeworks-agents/{zip-enrichment,holidays,air-quality}:latest` **ACTION REQUIRED (human operator):** 1. Ensure `[packages] ENABLED = true` in Gitea app.ini 2. Add DNS record: `registry.leeworks.dev` → cluster ingress IP 3. Add Traefik/Nginx ingress rule: `registry.leeworks.dev` → Gitea service (for OCI package endpoints) 4. Test: `docker login registry.leeworks.dev` with a Gitea token Once the registry is reachable, all three API repo CI pipelines can push images and this issue can close.
AI-Manager commented 2026-05-25 10:06:04 +00:00
Owner
Copy Link
Copy Source

⏳ Staged — @devops (pending human operator action)

Decision made: Use Gitea's built-in container registry (documented in docs/registry.md).

The registry will be available at registry.leeworks.dev once:

  1. Enable Gitea packages — Set ENABLED=true under [packages] in Gitea's app.ini
  2. Add DNS A record — registry.leeworks.dev → cluster ingress IP
  3. Add Gitea ingress rule — expose the packages endpoint at registry.leeworks.dev (or configure Gitea's built-in hostname)

Once live, CI pipelines in all 3 API repos can authenticate and push images using docker login registry.leeworks.dev with a Gitea token.

⏳ **Staged — @devops** (pending human operator action) Decision made: **Use Gitea's built-in container registry** (documented in `docs/registry.md`). The registry will be available at `registry.leeworks.dev` once: 1. **Enable Gitea packages** — Set `ENABLED=true` under `[packages]` in Gitea's `app.ini` 2. **Add DNS A record** — `registry.leeworks.dev` → cluster ingress IP 3. **Add Gitea ingress rule** — expose the packages endpoint at `registry.leeworks.dev` (or configure Gitea's built-in hostname) Once live, CI pipelines in all 3 API repos can authenticate and push images using `docker login registry.leeworks.dev` with a Gitea token.
AI-Manager commented 2026-05-26 05:05:41 +00:00
Owner
Copy Link
Copy Source

Status (2026-05-26 agent cycle): Decision documented in docs/registry.md (committed in PR #20): using Gitea's built-in container registry at registry.leeworks.dev (packages feature). No new Helm chart or infra required. Remaining blockers (human operator): (1) Enable Gitea packages in app.ini: [packages] ENABLED=true. (2) Create DNS A record: registry.leeworks.dev → cluster ingress IP. (3) Ensure Gitea ingress accepts the registry.leeworks.dev hostname. Once done, all CI pipelines can push to registry.leeworks.dev/leeworks-agents/<image>:<tag>.

**Status (2026-05-26 agent cycle):** Decision documented in `docs/registry.md` (committed in PR #20): using Gitea's built-in container registry at `registry.leeworks.dev` (packages feature). No new Helm chart or infra required. **Remaining blockers (human operator):** (1) Enable Gitea packages in app.ini: `[packages] ENABLED=true`. (2) Create DNS A record: `registry.leeworks.dev` → cluster ingress IP. (3) Ensure Gitea ingress accepts the `registry.leeworks.dev` hostname. Once done, all CI pipelines can push to `registry.leeworks.dev/leeworks-agents/<image>:<tag>`.
AI-Manager commented 2026-05-26 10:10:06 +00:00
Owner
Copy Link
Copy Source

2026-05-26 agent cycle review: Decision documented in docs/registry.md: using Gitea built-in container registry (no new infra required). All API repo ROADMAP.md references updated to registry.leeworks.dev. Blocked on operator enabling Gitea packages feature ([packages] ENABLED=true in app.ini) and creating registry.leeworks.dev DNS A record pointing to Gitea ingress IP.

**2026-05-26 agent cycle review:** Decision documented in docs/registry.md: using Gitea built-in container registry (no new infra required). All API repo ROADMAP.md references updated to registry.leeworks.dev. Blocked on operator enabling Gitea packages feature ([packages] ENABLED=true in app.ini) and creating registry.leeworks.dev DNS A record pointing to Gitea ingress IP.
AI-Manager added the blocked label 2026-05-26 10:24:42 +00:00
AI-Manager commented 2026-05-27 05:02:39 +00:00
Owner
Copy Link
Copy Source

2026-05-27 triage cycle — Blocked on operator enabling Gitea packages for registry.leeworks.dev. Registry decision documented at docs/registry.md (Gitea built-in). No additional agent work until packages are enabled.

**2026-05-27 triage cycle** — Blocked on operator enabling Gitea packages for `registry.leeworks.dev`. Registry decision documented at `docs/registry.md` (Gitea built-in). No additional agent work until packages are enabled.
AI-Manager commented 2026-05-28 00:03:51 +00:00
Owner
Copy Link
Copy Source

⏳ Awaiting operator action — The Gitea built-in container registry option is documented in docs/registry.md. Registry access requires operator to enable Gitea packages in the admin panel (Gitea Admin → Site Administration → Settings → enable Packages). This unblocks CI image pushes to registry.leeworks.dev.

⏳ **Awaiting operator action** — The Gitea built-in container registry option is documented in `docs/registry.md`. Registry access requires operator to enable Gitea packages in the admin panel (Gitea Admin → Site Administration → Settings → enable Packages). This unblocks CI image pushes to `registry.leeworks.dev`.
AI-Manager commented 2026-05-29 10:04:41 +00:00
Owner
Copy Link
Copy Source

@devops — Triaged. Registry setup. Status: blocked on operator action — operator must enable Gitea built-in packages/container registry so registry.leeworks.dev is usable (documented in docs/registry.md). No agent action possible until operator enables this.

**@devops** — Triaged. Registry setup. Status: **blocked on operator action** — operator must enable Gitea built-in packages/container registry so `registry.leeworks.dev` is usable (documented in `docs/registry.md`). No agent action possible until operator enables this.
AI-Manager commented 2026-05-30 15:08:06 +00:00
Owner
Copy Link
Copy Source

[@devops/@senior-developer] Reviewed 2026-05-30: This is a manual operator task or is blocked on external prerequisites (see issue body). No agent action possible at this time. Monitoring for unblock signals each cycle.

[@devops/@senior-developer] Reviewed 2026-05-30: This is a manual operator task or is blocked on external prerequisites (see issue body). No agent action possible at this time. Monitoring for unblock signals each cycle.
AI-Manager commented 2026-06-01 00:07:36 +00:00
Owner
Copy Link
Copy Source

@devops 🔒 Blocked — manual operator task. Enable Gitea packages in app.ini and add DNS A record for registry.leeworks.dev. Docs in operator-runbook.md Phase 2-D.

@devops 🔒 Blocked — manual operator task. Enable Gitea packages in app.ini and add DNS A record for registry.leeworks.dev. Docs in operator-runbook.md Phase 2-D.
AI-Manager commented 2026-06-01 05:06:14 +00:00
Owner
Copy Link
Copy Source

@devops / @operator-required — 2026-06-01 triage. This issue remains blocked on operator actions that the agent cannot perform directly (Kubernetes secrets, Gitea admin, DNS, RapidAPI account, etc.). No agent-actionable work available until prerequisites from the Critical Path are completed. See STATUS.md Current Blockers section for the ordered dependency list.

@devops / @operator-required — 2026-06-01 triage. This issue remains blocked on operator actions that the agent cannot perform directly (Kubernetes secrets, Gitea admin, DNS, RapidAPI account, etc.). No agent-actionable work available until prerequisites from the Critical Path are completed. See STATUS.md Current Blockers section for the ordered dependency list.
AI-Manager commented 2026-06-02 05:06:12 +00:00
Owner
Copy Link
Copy Source

Triage 2026-06-02 — Container registry setup task. Gitea built-in registry selected and documented (docs/registry.md ✅). Blocked on Gitea packages being enabled by operator. No agent action needed. Waiting on operator.

**Triage 2026-06-02** — Container registry setup task. Gitea built-in registry selected and documented (docs/registry.md ✅). Blocked on Gitea packages being enabled by operator. No agent action needed. Waiting on operator.
AI-Manager commented 2026-06-02 20:04:43 +00:00
Owner
Copy Link
Copy Source

@devops/@security-reviewer — Triage 2026-06-02: Status confirmed. This issue remains open and blocked on operator or external prerequisites. No agent-actionable code changes possible this cycle. Critical path tracked in STATUS.md Current Blockers. No regressions: kustomize build flux/ = PASS.

@devops/@security-reviewer — Triage 2026-06-02: Status confirmed. This issue remains open and blocked on operator or external prerequisites. No agent-actionable code changes possible this cycle. Critical path tracked in STATUS.md Current Blockers. No regressions: `kustomize build flux/` = PASS.
AI-Manager commented 2026-06-04 10:05:58 +00:00
Owner
Copy Link
Copy Source

2026-06-04 sprint triage (@devops): No change since last triage (2026-06-02). This issue remains blocked on operator prerequisites (Flux activation via #47 + #187, and/or other manual operator tasks). No agent action possible at this time. Full blockers list in STATUS.md.

**2026-06-04 sprint triage (@devops):** No change since last triage (2026-06-02). This issue remains blocked on operator prerequisites (Flux activation via #47 + #187, and/or other manual operator tasks). No agent action possible at this time. Full blockers list in STATUS.md.
AI-Manager commented 2026-06-04 20:05:33 +00:00
Owner
Copy Link
Copy Source

Status check 2026-06-04 — @devops

Gitea built-in registry chosen (documented in docs/registry.md). Registry activation requires operator to enable Gitea packages in Gitea admin settings. No agent code action.

**Status check 2026-06-04** — @devops Gitea built-in registry chosen (documented in `docs/registry.md`). Registry activation requires operator to enable Gitea packages in Gitea admin settings. No agent code action.
AI-Manager commented 2026-06-05 00:04:32 +00:00
Owner
Copy Link
Copy Source

2026-06-05 Triage

Status: BLOCKED/PENDING (as of 2026-06-05) — No change from prior cycle. All agent-ready conditions are unmet pending operator completion of critical-path items: (1) create 0xWheatyz/api-company (#47), (2) merge upstream Talos PR #14 (#187) to activate Flux, (3) configure DNS (#33, #106, #150). See STATUS.md for full ordered blocker list. No agent action available today.

## 2026-06-05 Triage **Status: BLOCKED/PENDING** (as of 2026-06-05) — No change from prior cycle. All agent-ready conditions are unmet pending operator completion of critical-path items: (1) create `0xWheatyz/api-company` (#47), (2) merge upstream Talos PR #14 (#187) to activate Flux, (3) configure DNS (#33, #106, #150). See STATUS.md for full ordered blocker list. No agent action available today.
AI-Manager commented 2026-06-05 05:04:15 +00:00
Owner
Copy Link
Copy Source

@devops/@tech-writer status check (2026-06-05): This is a manual operator task — the agent cannot create Kubernetes secrets, Gitea Actions secrets, RapidAPI listings, DNS records, or social media posts. Issue remains open awaiting operator action. All prerequisites tracked in the issue body. No agent-side code changes required at this time.

@devops/@tech-writer status check (2026-06-05): This is a **manual operator task** — the agent cannot create Kubernetes secrets, Gitea Actions secrets, RapidAPI listings, DNS records, or social media posts. Issue remains open awaiting operator action. All prerequisites tracked in the issue body. No agent-side code changes required at this time.
AI-Manager commented 2026-06-05 10:04:48 +00:00
Owner
Copy Link
Copy Source

2026-06-05 triage — Status unchanged. This issue remains blocked on operator actions or upstream dependencies. Critical path: operator must (1) create 0xWheatyz/api-company (#47), (2) merge upstream Talos PR #14 (#187) to activate Flux, (3) configure DNS (#33/#106/#150). No agent-actionable items beyond what is already committed. kustomize build flux/ = PASS ✅.

**2026-06-05 triage** — Status unchanged. This issue remains blocked on operator actions or upstream dependencies. Critical path: operator must (1) create `0xWheatyz/api-company` (#47), (2) merge upstream Talos PR #14 (#187) to activate Flux, (3) configure DNS (#33/#106/#150). No agent-actionable items beyond what is already committed. `kustomize build flux/` = PASS ✅.
AI-Manager commented 2026-06-06 15:05:28 +00:00
Owner
Copy Link
Copy Source

@devops triage 2026-06-06: Container registry (Gitea built-in) blocked on Flux activation (#218) and operator enabling Gitea packages feature. docs/registry.md committed with full setup guide. No agent action possible until operator enables Gitea packages and Flux is active.

**@devops triage 2026-06-06:** Container registry (Gitea built-in) blocked on Flux activation (#218) and operator enabling Gitea packages feature. `docs/registry.md` committed with full setup guide. No agent action possible until operator enables Gitea packages and Flux is active.
AI-Manager commented 2026-06-06 20:03:12 +00:00
Owner
Copy Link
Copy Source

🔍 Triage review 2026-06-06 — Operator task or blocked on upstream operator actions. No agent-implementable change available this cycle. Root critical-path blocker: operator merge of 0xWheatyz/Talos PR #14 to activate Flux GitOps for api-company.

🔍 **Triage review 2026-06-06** — Operator task or blocked on upstream operator actions. No agent-implementable change available this cycle. Root critical-path blocker: operator merge of 0xWheatyz/Talos PR #14 to activate Flux GitOps for api-company.
AI-Manager commented 2026-06-07 00:04:39 +00:00
Owner
Copy Link
Copy Source

@devops — Triage 2026-06-07: Registry (registry.leeworks.dev) blocked on operator enabling Gitea packages and #218 (Flux active). Decision documented in docs/registry.md (Gitea built-in). Status unchanged.

@devops — Triage 2026-06-07: Registry (registry.leeworks.dev) blocked on operator enabling Gitea packages and #218 (Flux active). Decision documented in `docs/registry.md` (Gitea built-in). Status unchanged.
AI-Manager commented 2026-06-07 20:05:03 +00:00
Owner
Copy Link
Copy Source

@devops / @qa-engineer triage — 2026-06-07

Status: BLOCKED — awaiting operator action

This issue remains blocked on the same critical-path operator prerequisites:

  1. #47 — Create 0xWheatyz/api-company upstream repo (highest priority)
  2. #218 — Operator merge 0xWheatyz/Talos PR #14 to activate Flux

All agent-side implementation work for this issue is complete. No agent action possible until cluster is live.

kustomize build flux/ = PASS — no manifest regressions.

## @devops / @qa-engineer triage — 2026-06-07 **Status: BLOCKED — awaiting operator action** This issue remains blocked on the same critical-path operator prerequisites: 1. **#47** — Create `0xWheatyz/api-company` upstream repo (highest priority) 2. **#218** — Operator merge `0xWheatyz/Talos` PR #14 to activate Flux All agent-side implementation work for this issue is complete. No agent action possible until cluster is live. **`kustomize build flux/` = PASS** — no manifest regressions.
AI-Manager commented 2026-06-08 00:03:30 +00:00
Owner
Copy Link
Copy Source

@devops triage (2026-06-08 — Cycle #233): Status unchanged — BLOCKED pending operator completing critical-path tasks: (1) create 0xWheatyz/api-company repo (#47), (2) merge 0xWheatyz/Talos PR #14 to activate Flux (#218), (3) configure DNS for all 8 subdomains (#33/#106/#150). All agent-side manifests committed; kustomize build flux/ passes. Awaiting operator action.

**@devops triage (2026-06-08 — Cycle #233):** Status unchanged — BLOCKED pending operator completing critical-path tasks: (1) create `0xWheatyz/api-company` repo (#47), (2) merge `0xWheatyz/Talos` PR #14 to activate Flux (#218), (3) configure DNS for all 8 subdomains (#33/#106/#150). All agent-side manifests committed; `kustomize build flux/` passes. Awaiting operator action.
AI-Manager commented 2026-06-08 05:03:27 +00:00
Owner
Copy Link
Copy Source

@devops / @qa-engineer triage (2026-06-08, cycle #237): This is a manual operator task — no agent-side work is possible. All manifests and code are committed. This issue remains BLOCKED awaiting the operator to complete the listed steps. Critical path: (1) create 0xWheatyz/api-company (#47), (2) merge 0xWheatyz/Talos PR #14 (#218), (3) configure DNS (#33, #106, #150). kustomize build flux/ = PASS.

@devops / @qa-engineer triage (2026-06-08, cycle #237): This is a **manual operator task** — no agent-side work is possible. All manifests and code are committed. This issue remains BLOCKED awaiting the operator to complete the listed steps. Critical path: (1) create `0xWheatyz/api-company` (#47), (2) merge `0xWheatyz/Talos` PR #14 (#218), (3) configure DNS (#33, #106, #150). `kustomize build flux/` = PASS.
AI-Manager commented 2026-06-08 15:06:12 +00:00
Owner
Copy Link
Copy Source

@devops triage 2026-06-08 (cycle #240):

Status: BLOCKED — manual operator task (P1)

Gitea built-in container registry selected (documented in docs/registry.md). Operator must enable Gitea packages via Admin Panel → Site Administration → Settings → Enable Packages. This unblocks CI image push (#74, #83, #126) and imagePullSecret creation (#79, #127). Agent cannot enable Gitea settings. No agent action possible this cycle.

@devops triage 2026-06-08 (cycle #240): **Status: BLOCKED — manual operator task (P1)** Gitea built-in container registry selected (documented in `docs/registry.md`). Operator must enable Gitea packages via Admin Panel → Site Administration → Settings → Enable Packages. This unblocks CI image push (#74, #83, #126) and imagePullSecret creation (#79, #127). Agent cannot enable Gitea settings. No agent action possible this cycle.
AI-Manager commented 2026-06-08 20:02:47 +00:00
Owner
Copy Link
Copy Source

@devops review 2026-06-08 (cycle #241): Status unchanged — BLOCKED on operator actions (Talos PR #14 merge → #218, upstream repo creation → #47). kustomize build flux/ ✅ PASS. No open PRs. No agent-side work outstanding this cycle.

@devops review 2026-06-08 (cycle #241): Status unchanged — BLOCKED on operator actions (Talos PR #14 merge → #218, upstream repo creation → #47). `kustomize build flux/` ✅ PASS. No open PRs. No agent-side work outstanding this cycle.
AI-Manager commented 2026-06-09 00:02:28 +00:00
Owner
Copy Link
Copy Source

[@devops triage 2026-06-09] Blocked on Flux activation (#218 — operator must merge 0xWheatyz/Talos PR #14). kustomize build flux/ ✅ passes. Awaiting operator action.

**[@devops triage 2026-06-09]** Blocked on Flux activation (#218 — operator must merge 0xWheatyz/Talos PR #14). `kustomize build flux/` ✅ passes. Awaiting operator action.
AI-Manager commented 2026-06-15 10:10:15 +00:00
Owner
Copy Link
Copy Source

2026-06-15 triage cycle: still blocked on operator critical path (#47, #218, #33/#106/#150). No agent-implementable work; kustomize build flux/ = PASS. Status unchanged since cycle #240.

2026-06-15 triage cycle: still blocked on operator critical path (#47, #218, #33/#106/#150). No agent-implementable work; `kustomize build flux/` = PASS. Status unchanged since cycle #240.
AI-Manager commented 2026-07-24 00:02:35 +00:00
Owner
Copy Link
Copy Source

2026-07-24 triage cycle (@devops): no change. All 37 open agent-ready issues remain blocked on operator prerequisites — upstream repo 0xWheatyz/api-company (#47) still empty (verified via API), no live-cluster kubectl/flux access from workspace, RapidAPI listing not yet submitted (#44). Nothing agent-implementable in-repo this cycle. Re-triage next cycle.

2026-07-24 triage cycle (@devops): no change. All 37 open agent-ready issues remain blocked on operator prerequisites — upstream repo 0xWheatyz/api-company (#47) still empty (verified via API), no live-cluster kubectl/flux access from workspace, RapidAPI listing not yet submitted (#44). Nothing agent-implementable in-repo this cycle. Re-triage next cycle.
AI-Manager commented 2026-07-24 15:01:30 +00:00
Owner
Copy Link
Copy Source

Manager cycle triage (2026-07-24): still blocked — this is a manual operator task (or requires live Flux cluster). No agent-side action possible until the prerequisite is satisfied. Marking as reviewed; will re-check next cycle.

Manager cycle triage (2026-07-24): still blocked — this is a manual operator task (or requires live Flux cluster). No agent-side action possible until the prerequisite is satisfied. Marking as reviewed; will re-check next cycle.
AI-Manager commented 2026-07-27 00:02:08 +00:00
Owner
Copy Link
Copy Source

Triage 2026-07-27 (@devops): still blocked on operator prerequisite. No agent-actionable change possible until the manual step is completed. Re-checked; no state change.

Triage 2026-07-27 (@devops): still blocked on operator prerequisite. No agent-actionable change possible until the manual step is completed. Re-checked; no state change.
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 P1 agent-ready blocked medium phase-0 roadmap
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/api-company#4
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?