capture #49c: Gitea IssueTracker client (new outbound dependency) #52

New Issue

2026-06-22T20:27:10Z

mathias commented

2026-06-22 20:27:10 +00:00

Parent: #49 · Spec: specs/capture-bdd-spec.md §1 · Depends on: #51 (the IssueTracker port) · Blocks: #49d

Scope

Implement the IssueTracker port (#51) as a real Gitea client. This is the new outbound dependency the brain server does not have today — per the #49 ground-truth, the brain server does brain-local file ops only and knows nothing about Gitea. Isolated and testable against a Gitea test instance.

What to build

A concrete IssueTracker impl: CreateIssue(repo, title, body), CloseIssue(repo, number, comment), CommentIssue(repo, number, body). Owner is always mathias (hard-coded; never caller-supplied).
Gitea API HTTP client, injected into the brain server behind the IssueTracker interface (swappable/testable — the use-case never sees the concrete type).
Token handling: Gitea API token via env, never in argv or logs (AGENTS.md secret-handling; the 2026-06-11 base64-masking-defeat incident is the cautionary precedent). Token read once at construction.
Map Gitea responses to the Ticket receipt fields ({repo, number, action, url, ok}).

Acceptance criteria

Concrete IssueTracker implementing #51's port: create / close / comment
Owner forced to mathias; never read from caller input
Injected into the brain server behind the interface (constructor injection)
Token via env only; no secret in argv/logs; verify with a log-scrape test
Errors mapped to per-item receipt ok:false + message (best-effort; one failed ticket doesn't abort the call)
Tests against a Gitea test instance (or a recorded/faked transport): create, close, comment, error path
task check green

Notes

Decision from #49: the Gitea client lives in the brain server, injected behind the interface — not a separate composing service. This keeps capture as one use-case while keeping the dependency swappable. The interface boundary is what lets #51's use-case tests stay hermetic (fake tracker) while this issue tests the real wire.

**Parent:** #49 · **Spec:** `specs/capture-bdd-spec.md` §1 · **Depends on:** #51 (the `IssueTracker` port) · **Blocks:** #49d ## Scope Implement the `IssueTracker` port (#51) as a real Gitea client. This is the **new outbound dependency the brain server does not have today** — per the #49 ground-truth, the brain server does brain-local file ops only and knows nothing about Gitea. Isolated and testable against a Gitea test instance. ## What to build - A concrete `IssueTracker` impl: `CreateIssue(repo, title, body)`, `CloseIssue(repo, number, comment)`, `CommentIssue(repo, number, body)`. Owner is always `mathias` (hard-coded; never caller-supplied). - Gitea API HTTP client, injected into the brain server behind the `IssueTracker` interface (swappable/testable — the use-case never sees the concrete type). - **Token handling:** Gitea API token via env, **never in argv or logs** (AGENTS.md secret-handling; the 2026-06-11 base64-masking-defeat incident is the cautionary precedent). Token read once at construction. - Map Gitea responses to the `Ticket` receipt fields (`{repo, number, action, url, ok}`). ## Acceptance criteria - [ ] Concrete `IssueTracker` implementing #51's port: create / close / comment - [ ] Owner forced to `mathias`; never read from caller input - [ ] Injected into the brain server behind the interface (constructor injection) - [ ] Token via env only; no secret in argv/logs; verify with a log-scrape test - [ ] Errors mapped to per-item receipt `ok:false` + message (best-effort; one failed ticket doesn't abort the call) - [ ] Tests against a Gitea test instance (or a recorded/faked transport): create, close, comment, error path - [ ] `task check` green ## Notes Decision from #49: the Gitea client lives **in the brain server**, injected behind the interface — not a separate composing service. This keeps capture as one use-case while keeping the dependency swappable. The interface boundary is what lets #51's use-case tests stay hermetic (fake tracker) while this issue tests the real wire.

mathias referenced this issue

2026-06-22 20:27:28 +00:00

capture #49d: POST /capture REST adapter + OAuth2 + I1 gate (server-derived origin) #53

mathias referenced this issue

2026-06-22 20:28:20 +00:00

feat: uniform `capture` capability — REST+OAuth2 spine for session insight/ticket capture across all harnesses #49

mathias referenced this issue from a commit

2026-06-22 20:42:05 +00:00

feat(classification): data-sensitivity taxonomy + per-wing/repo tags (#50)

mathias referenced this issue

2026-06-22 20:42:25 +00:00

feat: capture classification taxonomy + per-wing/repo tags (#50, capture 49a) #56

mathias referenced this issue

2026-06-22 20:42:39 +00:00

capture #49a: classification taxonomy + per-wing/repo tagging (I1 prerequisite) #50

mathias referenced this issue

2026-06-22 21:22:06 +00:00

feat: CaptureService use-case + BrainStore extraction (#51, capture 49b) #57

mathias referenced this issue

2026-06-22 21:22:18 +00:00

capture #49b: CaptureService use-case + BrainStore extraction + ports/entities #51

mathias referenced this issue from a commit

2026-06-22 21:27:29 +00:00

refactor(capture): CloseIssue carries a closing comment (#52)

mathias referenced this issue from a commit

2026-06-22 21:27:29 +00:00

feat(gitea): IssueTracker client + inject into brain server (#52)

mathias referenced a pull request that will close this issue

2026-06-22 21:27:47 +00:00

feat: Gitea IssueTracker client + inject into brain server (#52, capture 49c) #58

mathias commented

2026-06-22 21:27:59 +00:00

Implemented — PR #58 (open, stacked on #57)

PR: #58 · base feat/capture-service (#52-only diff). Merge order: #56 → #57 → #58.

ingestion/internal/gitea/ — Client implementing capture.IssueTracker:

create / comment / close(+optional closing comment) over the Gitea REST API.
Owner const "mathias" — never a param; a caller can't redirect to another owner's repo.
Token: read once from BRAIN_GITEA_TOKEN, only ever in the Authorization header — never logged/argv. TestErrorPathDoesNotLeakToken proves the token never appears in an error string. gitea.New → nil when unconfigured.
Injected via mcp.Server.WithIssueTracker (constructor injection) + IssueTracker() accessor; main wires from BRAIN_GITEA_URL (default https://git.d-ma.be) + BRAIN_GITEA_TOKEN. Consumed by the use-case in #53.

Port refinement: CloseIssue gained a comment param to match this issue's spec; service passes the ticket body as the closing comment.

Deploy note: 1Password DMABE_GITEA_API_TOKEN → maps to BRAIN_GITEA_TOKEN in the k3s manifest (#55/infra). Secret never in repo/argv/logs.

All ACs met (httptest-backed: create/comment/close±comment/error/auth-header/owner-forcing); task check green.

Critical path next: #53 — POST /capture REST adapter + OAuth2 + the I1 sovereignty gate (server-derived origin). All three converging deps (#50 classification, #51 service, #52 tracker) are now in flight; #53 wires them together and adds the origin gate. After #53 = "capture works" for direct-REST harnesses.

## Implemented — PR #58 (open, stacked on #57) **PR:** https://git.d-ma.be/mathias/hyperguild/pulls/58 · base `feat/capture-service` (#52-only diff). Merge order: **#56 → #57 → #58**. `ingestion/internal/gitea/` — `Client` implementing `capture.IssueTracker`: - create / comment / close(+optional closing comment) over the Gitea REST API. - **Owner const `"mathias"`** — never a param; a caller can't redirect to another owner's repo. - **Token:** read once from `BRAIN_GITEA_TOKEN`, only ever in the `Authorization` header — never logged/argv. `TestErrorPathDoesNotLeakToken` proves the token never appears in an error string. `gitea.New` → nil when unconfigured. - Injected via `mcp.Server.WithIssueTracker` (constructor injection) + `IssueTracker()` accessor; `main` wires from `BRAIN_GITEA_URL` (default `https://git.d-ma.be`) + `BRAIN_GITEA_TOKEN`. Consumed by the use-case in #53. **Port refinement:** `CloseIssue` gained a `comment` param to match this issue's spec; service passes the ticket body as the closing comment. **Deploy note:** 1Password `DMABE_GITEA_API_TOKEN` → maps to `BRAIN_GITEA_TOKEN` in the k3s manifest (#55/infra). Secret never in repo/argv/logs. All ACs met (`httptest`-backed: create/comment/close±comment/error/auth-header/owner-forcing); `task check` green. **Critical path next: #53** — `POST /capture` REST adapter + OAuth2 + the I1 sovereignty gate (server-derived origin). All three converging deps (#50 classification, #51 service, #52 tracker) are now in flight; #53 wires them together and adds the origin gate. After #53 = "capture works" for direct-REST harnesses.

mathias closed this issue

2026-06-22 21:32:02 +00:00

mathias referenced this issue from a commit

2026-06-22 21:32:04 +00:00

Merge pull request 'feat: Gitea IssueTracker client + inject into brain server (#52, capture 49c)' (#58) from feat/capture-gitea-tracker into main

mathias referenced this issue

2026-06-22 22:21:35 +00:00

feat: capture relay — MCP capture tool for non-library harnesses (#55, capture 49f) #61

mathias referenced this issue

2026-06-23 05:29:05 +00:00

feat: uniform `capture` capability — REST+OAuth2 spine for session insight/ticket capture across all harnesses #49

Sign in to join this conversation.