fix: retain originating hashtags in native activity and dispatcher status #210
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/hashtag-status-labels"
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?
Depends on harness/plugins#35; pins canonical renderer e04f7d8. No generated-only edit. Stored exact assignment tags reach the first starting snapshot and Main/Worker terminal activity. Worker forwarding overwrites event tags from retained execution; lifecycle notifications use same origin and hide ordinary UUID decoration while preserving exact /dispatch answer controls. No current-conversation fallback.
Context adequacy: docs/hashtag-context-assessment.md; bounded no-model repro proves A/B tags retain the same SDK session and conversation memory key. Tags are labels/search, NOT isolation. Existing Matrix threads are the smallest existing history boundary; no new architecture.
Tests: full suite 1195/1195 (118.9s), typecheck/build passed. Actual channel->canonical renderer, initial timing, late A after B, worker spoof resistance, legacy, execution reload, native restart, exact question controls, prior outbox retry/restart tests. Independent ReviewService+ReviewWorkers using existing review-executions.json: passed, no findings; fingerprint 793fa553ff62c6763c2e81b06ede2a61900b31ad45250a10830acf061f515243. No GitHub merge. No live rollout claim until GitOps/image/health evidence.