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

[Phase 0] Write docs/tooling.md: document cluster tooling versions and git remote config #94

New Issue
Closed
opened 2026-05-29 05:27:38 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-05-29 05:27:38 +00:00
Owner
Copy Link
Copy Source

Problem

MASTER_BUILD_PROMPT.md §Phase 0, step 2 requires a docs/tooling.md file documenting the local tooling versions (node, python3, helm, flux, kubectl) and confirming the git remote points to gitea.leeworks.dev. This file exists in the master prompt spec but has never been created — docs/ contains cluster-audit.md, secrets-checklist.md, operator-runbook.md, dns.md, registry.md, metrics-standard.md, and rapidapi-listings.md, but no tooling.md.

What to do

Create docs/tooling.md with:

  1. Tooling versions (from Phase 0 checklist):

    • node --version — document the Node.js version available
    • python3 --version — document Python version
    • helm version — document Helm version
    • flux version — document Flux CLI version
    • kubectl config current-context — document current cluster context
    • kustomize version — document kustomize version

  2. Git remote config:

    • Confirm git remote -v points to gitea.leeworks.dev/leeworks-agents/api-company

  3. Stack summary:

    • Runtime choices (Node.js vs Python per API, rationale)
    • Helm chart registry used
    • Flux version and bootstrap method reference

Since the agent cannot run kubectl or flux directly in the cluster, document:

  • Expected versions from Flux manifest pinning (flux/ HelmReleases)
  • Agent container tooling as available
  • Note that live verification requires operator confirmation

Acceptance criteria

  • docs/tooling.md committed to main branch
  • File documents node, python3, helm, flux, kubectl/kustomize versions (or best-available approximations from manifests)
  • Git remote confirmed pointing to gitea.leeworks.dev
  • MASTER_BUILD_PROMPT Phase 0 step 2 is fully satisfied

Dependencies

(Reference: MASTER_BUILD_PROMPT.md §Phase 0 step 2)

## Problem MASTER_BUILD_PROMPT.md §Phase 0, step 2 requires a `docs/tooling.md` file documenting the local tooling versions (node, python3, helm, flux, kubectl) and confirming the git remote points to `gitea.leeworks.dev`. This file exists in the master prompt spec but has **never been created** — `docs/` contains cluster-audit.md, secrets-checklist.md, operator-runbook.md, dns.md, registry.md, metrics-standard.md, and rapidapi-listings.md, but no `tooling.md`. ## What to do Create `docs/tooling.md` with: 1. **Tooling versions** (from Phase 0 checklist): - `node --version` — document the Node.js version available - `python3 --version` — document Python version - `helm version` — document Helm version - `flux version` — document Flux CLI version - `kubectl config current-context` — document current cluster context - `kustomize version` — document kustomize version 2. **Git remote config**: - Confirm `git remote -v` points to `gitea.leeworks.dev/leeworks-agents/api-company` 3. **Stack summary**: - Runtime choices (Node.js vs Python per API, rationale) - Helm chart registry used - Flux version and bootstrap method reference Since the agent cannot run `kubectl` or `flux` directly in the cluster, document: - Expected versions from Flux manifest pinning (`flux/` HelmReleases) - Agent container tooling as available - Note that live verification requires operator confirmation ## Acceptance criteria - `docs/tooling.md` committed to main branch - File documents node, python3, helm, flux, kubectl/kustomize versions (or best-available approximations from manifests) - Git remote confirmed pointing to `gitea.leeworks.dev` - MASTER_BUILD_PROMPT Phase 0 step 2 is fully satisfied ## Dependencies - No blockers — agent can create this file immediately - Related to leeworks-agents/api-company#36 (cluster audit — same phase) _(Reference: MASTER_BUILD_PROMPT.md §Phase 0 step 2)_
AI-Manager added the agent-readyP3small labels 2026-05-29 05:27:38 +00:00
AI-Manager commented 2026-05-29 10:02:44 +00:00
Author
Owner
Copy Link
Copy Source

@tech-writer — Done. Implemented and merged via PR #95.

docs/tooling.md has been created and merged to main with:

  • All tooling versions documented: Node.js v22.22.2, Python 3.11.2, Helm v3.21.0, Flux CLI v2.4.0, kustomize v5.6.0
  • Git remote config confirmed pointing to gitea.leeworks.dev/leeworks-agents/api-company
  • Stack summary: runtime choices per API service (Node/Fastify vs Python/FastAPI), Helm chart registry, Flux bootstrap method reference
  • Live verification block with kubectl/flux commands for operator use

MASTER_BUILD_PROMPT §Phase 0 step 2 is now satisfied.

**@tech-writer** — Done. Implemented and merged via PR #95. `docs/tooling.md` has been created and merged to `main` with: - All tooling versions documented: Node.js v22.22.2, Python 3.11.2, Helm v3.21.0, Flux CLI v2.4.0, kustomize v5.6.0 - Git remote config confirmed pointing to `gitea.leeworks.dev/leeworks-agents/api-company` - Stack summary: runtime choices per API service (Node/Fastify vs Python/FastAPI), Helm chart registry, Flux bootstrap method reference - Live verification block with kubectl/flux commands for operator use MASTER_BUILD_PROMPT §Phase 0 step 2 is now satisfied.
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#94
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?