feat: connector wave + hygiene — GT-527/529/530/477/480 DONE (503/532)#179
Conversation
…ter (GT-530c) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…T-527c) Add fetchBlueprintOwnership with injected BlueprintHttpClient port; maps via pure parseBlueprintOwnership (read-only, no lock-in). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Read-only infra seam behind the pure external-work ACL. Injected JiraHttpClient port keeps the adapter free of network config and unit-testable with a stub; fetchJiraWorkItems maps via parseJiraIssues (provenance preserved, id-less issues dropped, authorizesPhaseTransition stays false — guaranteed by the ACL). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…c' and 'origin/wf/gt-527c' into develop
…ONE (503/532) Driver integration of the second parallel wave (3 connector adapters, worktree-isolated, re-verified by build+test) + recovered board hygiene: - GT-529 → DONE: fetchJiraWorkItems + injected JiraHttpClient (read-only Jira connector over the ACL). - GT-530 → DONE: LangfuseEvidenceAdapter implements IObservabilityEvidenceSource (injected client). - GT-527 → DONE: fetchBlueprintOwnership (Port/Cortex) + loadBackstageOwnership complete the IDP connectors. - GT-477 → DONE: counter drift now guard-enforced (GT-476 armed on PR/push). - GT-480 → DONE: 0 non-canonical HECHO tokens remain. Barrel exports added by the driver. Verified: infra-providers 78/78, tsc clean, tracking guard green (532 gaps / 485 records). Counter → 503/532. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
📊 Bilingual Coverage ImpactPR Changes
Repository Coverage
✅ Good: All EN changes have ES counterparts. Generated by GitHub Actions |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1ff8385dc5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { | ||
| "id": "GT-529", | ||
| "closedAt": "2026-07-13", | ||
| "closureCommit": "856d2b56", |
There was a problem hiding this comment.
Use closure commits reachable from this change
Because this reviewed commit is a squash on top of 85595fd, the connector work is introduced by 4856f26 itself; git merge-base --is-ancestor 856d2b56 4856f26 returns false, as do the analogous checks for the GT-530/GT-527 commits below. In a checkout containing only this reviewed history, these new DONE records point to side-branch objects rather than the release commit, so the canonical closure registry loses reproducible traceability once those worktree branches are pruned. Record 4856f26 (or another commit that is actually reachable from the merged history) for these closures.
Useful? React with 👍 / 👎.
Integración (driver-serial) de la 2ª ola paralela (3 conectores en vivo, worktrees aislados, re-verificados por el driver con build+test) + higiene de board recuperada.
Cerrados (DONE + registros de cierre)
fetchJiraWorkItems+ puerto inyectableJiraHttpClient(conector Jira read-only sobre el ACL).LangfuseEvidenceAdapter implements IObservabilityEvidenceSource(cliente inyectado, delega enmapLangfuseTrace).fetchBlueprintOwnership(Port/Cortex) +loadBackstageOwnershipcompletan los conectores IDP.HECHOno canónicos.Verificación
infra-providers 78/78, tsc limpio, tracking guard 532 gaps / 485 records. Contador → 503/532. Exports de barrel añadidos por el driver. Los adaptadores son puros de config de red (cliente HTTP inyectable = testeable; fetch real = deploy).
🤖 Generated with Claude Code