INTENT.md currently claims to be 'a single, observable place where tasks
land' -- exactly the landing-zone role CUST-WP-0060's founder-reviewed
architecture draft (WorkOrchestrationArchitectureDraft.md v0.2, section
4.2) assigned away from issue-core, decided while reviewing the live
incident this repo caused: activity-core's daily-todo-md-stale-review
routed through IssueSink -> issue-core -> Forgejo, producing 5 issues
nobody was meant to see (now paused).
5 tasks: rewrite INTENT.md/SCOPE.md/README/ROADMAP for the connector
framing (work records originate as repo files per ADR-001; issue-core
is the optional external-tracker projection), design (not implement)
the UUID<->external-id mapping surface, and file the activity-core-side
follow-up to fix the IssueSink default. Docs-only scope; stage-3
implementation work stays in the-custodian.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Forgejo .forgejo/workflows/publish-python-package.yml already publishes to the
Forgejo PyPI registry. CUST-WP-0059-T01.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Adds publish-forgejo and a workflow_dispatch/tag workflow so issue-core
0.2.x can be published to forgejo.coulomb.social before vergabe-teilnahme
drops Gitea lockfile URLs.
Legacy in-cluster gitea-http repos are archived (issue create 423). Route
the default ingestion backend to https://forgejo.coulomb.social with
the-custodian as the central automation task inbox.
Sync AGENTS.md, CLAUDE.md, and .claude/rules from updated project_rules
templates: workplan-first session protocol, legacy terminology footnote,
and GET /workplans/ examples.
Add supports/related_to for vergabe-teilnahme and activity-core, cite
SCOPE.md, update test count to 120 (verified), and document dual-canonical
relationship with CAPABILITY-issue-tracking.yaml.
Honest first-pass maturity vector grounded in README/docs/tests present
in this repo; no invented evidence. Flagged for human review before
publish. See reuse-surface history/2026-07-06-coverage-classification.md.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Broaden POST /issues/ so triggering_event_id is any non-empty traceability
string, enabling cron/scheduled activity-core emissions with stable keys like
"scheduled" while event-driven paths still send UUIDs. Document the railiance01
ArgoCD deployment path in docs/argocd-gitops.md and update ISSUE-WP-0003 task
status to reflect repo-side progress.
- Align agent files with on-disk workplan prefixes (infer from workplan ids)
- Set workplan domain to registered domain_slug; add topic_slug where applicable
- Repair frontmatter delimiter formatting; migrate legacy task status literals
- Regenerate AGENTS.md, CLAUDE.md, and .claude/rules from State Hub templates
Apply the new 'tooling' category (reusable internal tooling/infrastructure)
from the Repo Classification Standard. First-pass agent classification.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
First-pass agent classification per the Repo Classification Standard v1.0
(canon-repo-classification); pending human review.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Introduce Dockerfile, entrypoint, and k8s/railiance manifests for the
ArgoCD GitOps pilot (ISSUE-WP-0003). Rename the Gitea PyPI build arg to
GITEA_PYPI_INDEX_URL so pip still resolves dependencies from PyPI.
Callers using the pre-rename `issue-tracker` command now get a clear
stderr message pointing them at `issue-core` (or the short `issue`
alias) and exit code 2, instead of `command not found`.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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>
Workplan for renaming issue-facade → issue-core and implementing the
POST /issues/ task ingestion endpoint required by activity-core's IssueSink
adapter. Covers rename, state hub registration, INTENT.md, SCOPE.md, REST
endpoint, and NATS design stub.
Hub workstream: 1135fc1d-1f46-4e35-886d-04cc3b8050b6
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Add comprehensive CHANGELOG following Keep a Changelog format to document
the architecture refactoring and feedback capability implementation.
Documented in v1.0.0:
- ReusableCapabilitiesArchitecture specification
- Feedback capability with visible directory structure
- Detachment facility for capability removal
- Enhanced documentation (CLAUDE.md, README.md, examples)
- Directory visibility changes (.feedback → feedback)
- Explicit family declaration (CAPABILITY-issue-tracking.yaml)
Also includes version history from v0.1.0 through v0.9.0 and
upgrade notes for migrating to v1.0.0.
Closes the documentation gap referenced in TODO.md.
Update directory structure diagrams and copy examples to use
the new visible feedback/ directory instead of hidden .feedback/
This ensures all documentation is consistent with the
ReusableCapabilitiesArchitecture v0.1 specification.
Refactor issue-facade to conform to the new ReusableCapabilitiesArchitecture
specification, improving discoverability and establishing consistent patterns
for capability integration.
Architecture Changes:
- Rename .feedback/ → feedback/ (visible user interface)
- Rename CAPABILITY.yaml → CAPABILITY-issue-tracking.yaml (explicit family)
- Keep .capability/ hidden (evolving implementation infrastructure)
File Updates:
- Updated all documentation references (.feedback → feedback)
- Updated .capability/feedback script paths
- Updated Makefile, README.md, CLAUDE.md, examples
- Fixed CAPABILITY.yaml → CAPABILITY-issue-tracking.yaml references
New Tools:
- Created .capability/detach script for clean capability removal
- Supports git submodule and directory-based integrations
- Generates detachment manifest for re-integration guidance
Rationale:
- feedback/ is visible: encourages user participation, shows capability identity
- .capability/ is hidden: implementation details that will evolve
- CAPABILITY-<family>.yaml: explicit family declaration, supports multiple capabilities per repo
- Underscore prefix pattern: flatter hierarchy, clear signal of integration
This aligns with the principle that capabilities are conceptual units
designed for natural language integration by devhumans and devagents,
not just technical libraries.
See ReusableCapabilitiesArchitecture.md for complete specification.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Transform Issue Facade from a universal CLI tool into an agent coordination platform with comprehensive documentation and enhanced capabilities for autonomous coding agents.
Major Changes:
- Complete README rewrite focusing on agent-driven coordination
- New comprehensive documentation (AGENT_INTEGRATION.md, CLAUDE.md, ROADMAP.md)
- Capability integration setup with CAPABILITY.yaml and integration scripts
- Enhanced Makefile with local development targets for easier workflows
Bug Fixes:
- Fix schema initialization using executescript() for multi-line SQL support
- Disable FTS5 triggers due to compatibility issues (documented for future re-enablement)
Features:
- Enhanced CLI list command with full parameter passthrough
- New examples directory with agent integration patterns
- New comprehensive test suite (test_core_models.py, test_local_backend.py)
Code Quality:
- Remove @cached_property decorators for Label properties (simplification)
- Clean up test organization (removed old test_gitea_integration.py)
This milestone establishes Issue Facade as a production-ready coordination layer for multi-agent software development, with clear integration paths and comprehensive developer documentation.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
