[Phase 1] Retain existing poller as backstop — fold into new architecture #9
Labels
No labels
[cloud]
[cross]
[done]
[homelab]
[phase-1]
[phase-2]
[phase-3]
[phase-4]
cloud
cross
done
homelab
ingestion
integration
phase-1
phase-2
phase-3
phase-4
subagent-auto
subagent-build
subagent-gpu
subagent-reason
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
starsetbyte/aether#9
Loading…
Reference in a new issue
No description provided.
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?
Context
The existing Forgejo issue poller (homelab/cross label detection) must not be discarded. It becomes the recovery backstop once webhooks are the fast path.
What to build
Refactor the existing poller to use the unified normalization path (issue #7).
Poller responsibilities:
Poll frequency:
The poller must NOT independently assign work. Issues with
homelab/crosslabels are translated into Aether offer events (observation-only in Phase 1).Both webhook and poll paths share deduplication state.
Acceptance