coulomb/issue-core
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Projects Releases Wiki Activity

feat: rename to issue-core and add task ingestion endpoint

Browse Source 
Renames the package, distribution, CLI alias, Makefile targets, and
working directory from issue-facade to issue-core, signalling its
role as the authoritative task lifecycle manager for the Coulomb org
(peer to activity-core, rules-core, project-core).

Adds POST /issues/ ingestion endpoint for activity-core's IssueSink,
under a new optional [api] extra. The endpoint is served by `issue
serve`, authenticates via the ISSUE_CORE_API_KEY env var (Bearer or
X-API-Key header), and routes the TaskSpec payload to the configured
default backend with full traceability metadata embedded in
sync_metadata.

- T01: Python package issue_tracker -> issue_core, dir rename
- T02: registered in state hub under custodian domain
- T03: INTENT.md (what it is, what it isn't, how it fits)
- T04: SCOPE.md (in/out-of-scope, integration boundaries)
- T05: POST /issues/ via FastAPI + Uvicorn, 9 unit tests
- T06: docs/nats-task-ingestion.md design stub

Closes ISSC-WP-0001.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Bernd Worsch
2026-05-17 05:16:27 +02:00
parent 99ea1fbc45
commit b605d970e3
38 changed files with 1324 additions and 361 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
examples/feedback-example.md
View File

@@ -1,6 +1,6 @@
# Feedback System Example
This example demonstrates how to submit feedback about the issue-facade capability.
This example demonstrates how to submit feedback about the issue-core capability.
## Quick Feedback Submission
@@ -8,7 +8,7 @@ This example demonstrates how to submit feedback about the issue-facade capabili
```bash
# Navigate to the capability directory
cd capabilities/issue-facade
cd capabilities/issue-core
# Submit quick text feedback
./.capability/feedback submit "The sync command is very slow when dealing with repositories that have 5000+ issues. Would love to see a progress indicator or batch processing to speed this up."
@@ -68,17 +68,17 @@ EOF
### Method 3: From Master Project
If you're working in a master project that integrates issue-facade:
If you're working in a master project that integrates issue-core:
```bash
# From your master project root
cd ~/my-master-project
# Write feedback
cat > feedback-for-issue-facade.md << 'EOF'
cat > feedback-for-issue-core.md << 'EOF'
## Feature Request: GitHub Backend
We're using issue-facade for our Gitea repos, but our company also has
We're using issue-core for our Gitea repos, but our company also has
50+ repositories on GitHub. Would love to have a GitHub backend so we
can use the same CLI for all our issue tracking.
@@ -91,8 +91,8 @@ We'd be happy to contribute or test!
EOF
# Copy to capability's feedback directory
cp feedback-for-issue-facade.md \
capabilities/issue-facade/feedback/inbound/$(date +%Y%m%d)-github-backend.md
cp feedback-for-issue-core.md \
capabilities/issue-core/feedback/inbound/$(date +%Y%m%d)-github-backend.md
```
## Feedback Categories
@@ -286,4 +286,4 @@ If you have questions about the feedback system itself, that's also feedback!
---
**Thank you for helping make issue-facade better through your feedback!**
**Thank you for helping make issue-core better through your feedback!**