coulomb/issue-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
issue-core/registry/capabilities/capability.infotech.issue-tracking.md
tegwick f88e9a28fe
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Build and Publish Container Image / build-and-push (push) Successful in 1m22s
Details
feat: implement ISSUE-WP-0005 connector mapping and scope alignment 
Add MappingService (work_record_uuid ↔ external id), project/map CLI with
outward push-status, optional TaskSpec work_record fields, boundary-sync
policy, and packaging/capability framing cleanup. Mark WP-0005 finished.
2026-07-22 00:25:06 +02:00

2.6 KiB
Raw Permalink Blame History

id: capability.infotech.issue-tracking name: External Issue Tracker Connector summary: Backend-agnostic CLI/Python connector to Gitea/Forgejo (and SQLite cache) with work-record UUID ↔ external issue mapping. Not the fleet work origin. owner: issue-core status: draft domain: infotech tags:

  • issue-tracking
  • connector
  • work-record maturity: discovery: current: D4 target: D5 confidence: high rationale: INTENT.md, SCOPE.md, CAPABILITY-issue-tracking.yaml, mapping design, boundary-sync policy, AGENT_INTEGRATION.md. availability: current: A2 target: A3 confidence: high rationale: Python package + CLI (list/create/project/map) installable via pip; mapping store shipped; MCP not yet available. external_evidence: completeness: level: C2 confidence: medium basis: scope_vs_intent_and_consumer_expectations satisfied_expectations:
    • Gitea + local SQLite backends
    • CLI with JSON output; project/map commands
    • work_record_uuid optional on TaskSpec
    • credential handling via env vars (GITEA_API_TOKEN, ISSUE_CORE_API_KEY) broken_expectations: [] out_of_scope_expectations:
    • Fleet task origin / intake promotion (work-record canon)
    • Default IssueSink for internal findings (activity-core) reliability: level: R1 confidence: low basis: consumer_quality_signals known_reliability_risks:
    • manual backend configuration (auto-detect planned)
    • no built-in issue locking beyond assignee+state
    • inward boundary sync not shipped discovery: intent: Project and operate on external issue trackers with a stable link to work-record UUIDs; never replace file-first work records as coordination substrate. includes:
    • unified Python API and CLI over Gitea/SQLite issue operations
    • work_record_issue_map store + project/map/push-status
    • local offline cache and backend sync
    • credential handling via environment variables excludes:
    • originating workplans/tasks/intake
    • MCP server (planned)
    • multi-agent fleet board semantics on Forgejo assumptions: [] use_cases: [] research_memos: [] availability: current_level: A2 target_level: A3 current_artifacts:
    • Python package (issue_core)
    • 'issue CLI (including project/map)' target_artifacts: [] consumption_modes:
    • cli
    • library import
    • rest (optional [api] extra) relations: depends_on: [] supports: [] related_to:
    • capability.activity.event-coordinate evidence: documentation:
    • INTENT.md
    • SCOPE.md
    • CAPABILITY-issue-tracking.yaml
    • docs/uuid-external-id-mapping.md
    • docs/boundary-sync-and-status-mapping.md