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

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>

examples/agents/README.md

@@ -1,10 +1,10 @@
 # Agent Examples
 
-This directory contains working examples of autonomous agents using the Issue Facade for coordination.
+This directory contains working examples of autonomous agents using the Issue Core for coordination.
 
 ## Prerequisites
 
-1. **Install issue-facade**:
+1. **Install issue-core**:
    ```bash
    cd ../..
    pip install -e .

examples/agents/human_in_loop.py

@@ -27,9 +27,9 @@ from typing import Optional, List
 
 sys.path.insert(0, str(Path(__file__).parent.parent.parent))
 
-from issue_tracker.backends.gitea import GiteaBackend
-from issue_tracker.core.models import Issue, Label, User, Comment, IssueState
-from issue_tracker.core.interfaces import IssueFilter
+from issue_core.backends.gitea import GiteaBackend
+from issue_core.core.models import Issue, Label, User, Comment, IssueState
+from issue_core.core.interfaces import IssueFilter
 
 
 class HumanInLoopAgent:

examples/agents/monitoring_agent.py

@@ -28,9 +28,9 @@ from typing import List, Dict
 
 sys.path.insert(0, str(Path(__file__).parent.parent.parent))
 
-from issue_tracker.backends.gitea import GiteaBackend
-from issue_tracker.core.models import Issue, Label, User, Comment, IssueState
-from issue_tracker.core.interfaces import IssueFilter
+from issue_core.backends.gitea import GiteaBackend
+from issue_core.core.models import Issue, Label, User, Comment, IssueState
+from issue_core.core.interfaces import IssueFilter
 
 
 class MonitoringAgent:

examples/agents/multi_agent_pipeline.py

@@ -36,9 +36,9 @@ from typing import List
 
 sys.path.insert(0, str(Path(__file__).parent.parent.parent))
 
-from issue_tracker.backends.gitea import GiteaBackend
-from issue_tracker.core.models import Issue, Label, User, Comment, IssueState
-from issue_tracker.core.interfaces import IssueFilter
+from issue_core.backends.gitea import GiteaBackend
+from issue_core.core.models import Issue, Label, User, Comment, IssueState
+from issue_core.core.interfaces import IssueFilter
 
 
 class BaseAgent:

examples/agents/simple_task_executor.py

@@ -26,9 +26,9 @@ from pathlib import Path
 # Add parent directory to path for imports
 sys.path.insert(0, str(Path(__file__).parent.parent.parent))
 
-from issue_tracker.backends.gitea import GiteaBackend
-from issue_tracker.core.models import Issue, Label, User, Comment, IssueState
-from issue_tracker.core.interfaces import IssueFilter
+from issue_core.backends.gitea import GiteaBackend
+from issue_core.core.models import Issue, Label, User, Comment, IssueState
+from issue_core.core.interfaces import IssueFilter
 
 
 class SimpleTaskExecutor:

examples/feedback-example.md

@@ -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!**