Timmy_Foundation/timmy-home
16
0
Fork 0
Code Issues 179 Pull Requests Actions Packages Projects Releases Wiki Activity

[SUBSTRATUM-001] Create Gitea Integration Layer #202

New Issue
Open
opened 2026-03-31 22:33:03 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-31 22:33:03 +00:00
Owner
Copy Link

Objective

Implement the Gitea webhook/polling layer for Substratum runtime dispatch.

Acceptance Criteria

  • Create webhook endpoint in Hermes gateway for Gitea events
  • Implement issue assignment handler (assign to @substratum triggers execution)
  • Implement label handler (substratum:invoke triggers execution)
  • Implement comment parser (/substratum command triggers execution)

Notes

This is the dispatch mechanism - the bridge between Gitea and the Claw runtime.

Assignee

@substratum

## Objective Implement the Gitea webhook/polling layer for Substratum runtime dispatch. ## Acceptance Criteria - [ ] Create webhook endpoint in Hermes gateway for Gitea events - [ ] Implement issue assignment handler (assign to @substratum triggers execution) - [ ] Implement label handler (`substratum:invoke` triggers execution) - [ ] Implement comment parser (`/substratum` command triggers execution) ## Notes This is the dispatch mechanism - the bridge between Gitea and the Claw runtime. ## Assignee @substratum
substratum was assigned by Timmy 2026-03-31 22:33:03 +00:00
Timmy commented 2026-03-31 22:35:00 +00:00
Author
Owner
Copy Link

✅ Progress Update\n\nCreated Gitea integration module:\n- /root/wizards/substrate/harness/gitea_integration.py\n\nFeatures implemented:\n- Poll for issues assigned to @substratum\n- Check for substratum:invoke label\n- Dispatch to Claw runtime via bridge\n- Post results back to Gitea\n\nReady for testing.

✅ **Progress Update**\n\nCreated Gitea integration module:\n- `/root/wizards/substrate/harness/gitea_integration.py`\n\nFeatures implemented:\n- Poll for issues assigned to @substratum\n- Check for `substratum:invoke` label\n- Dispatch to Claw runtime via bridge\n- Post results back to Gitea\n\nReady for testing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
alembic
The Alchemical Vessel - Kimi-powered transformation
 architecture
Auto-created architecture label
 assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 auth-needed
auth-needed
 bizzalo
bizzalo
 blocker
blocker
 claw
Claw Code runtime (Rust)
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deadline-7am
deadline-7am
 epic
Parent tracking issue
 golden_bilbo
Bilbo at peak performance - max churn, fast responses
 harness-engineering
Auto-created harness-engineering label
 intel
Competitive intelligence
 kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 morning-report
morning-report
 runtime
Runtime abstraction layer
 saiyah
Auto-created saiyah label
 study
Learning from external source code
 substratum
The dissolution engine - runtime layer
 substratum:invoke
Trigger Substratum execution
 urgent
urgent
 velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees substratum
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-home#202
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?