harness/core
4
0
Fork 0
Code Issues Pull requests 7 Projects Releases 142 Packages 1 Wiki Activity Actions

feat: persist assignment hashtags on Main and worker output #208

Closed
severus-snape wants to merge 0 commits from feat/hashtag-output-labels into main
pull from: feat/hashtag-output-labels
merge into: harness:main
Conversation 0 Commits - Files changed -
severus-snape commented 2026-11-01 18:05:36 +00:00
Collaborator
Copy link

Small additional vertical slice on PR #206, actual base e554df3. Fresh operator authorization: Los, bauen! #hashtags.

Capture normalized tags only from trusted operator channel input, persist them with originating inbox/assignment metadata, inherit through existing dispatcher dependency anchors. Main outbox renders a canonical sorted #hashtags #rollout · prefix; worker status/questions and late result delivery use exact stored execution labels, never the newer conversation topic. Internal worker transport remains raw. No autofocus/context switching/routing/memory expansion. Legacy and API work remains untagged; /hashtags commands and index do not ingest generated labels.

Evidence: npm run typecheck, npm run build, full npm test 1188/1188 pass. Regression tests: direct Main without dispatcher, API spoofing, queued/restarted work, persisted outbox retry without duplicate labels, worker question/status/result labels after new topic, cross-conversation denial, native/external SDK transcript/index boundaries.

Independent owner ReviewService + dedicated ReviewWorkers on real persistent review ledger: passed, no findings, fingerprint a9718350a58509869a26549ad5d45eeae157657bbd11f8ea720452e76b783250; exact tree 81233e882d. Earlier P2 attention-delivery label gap fixed and re-reviewed; complete ledger history retained. Protected commit/push/publish assertions passed before and after commit.

Activation dependency: existing v0.1.134 rollout remains exclusively owned by worker 97cc012c. This PR does not duplicate or change that rollout. Normal integration/release/GitOps only after gates and prior rollout dependency; no direct main push or GitHub merge. No live activation claimed by this PR.

Small additional vertical slice on PR #206, actual base e554df3. Fresh operator authorization: Los, bauen! #hashtags. Capture normalized tags only from trusted operator channel input, persist them with originating inbox/assignment metadata, inherit through existing dispatcher dependency anchors. Main outbox renders a canonical sorted #hashtags #rollout · prefix; worker status/questions and late result delivery use exact stored execution labels, never the newer conversation topic. Internal worker transport remains raw. No autofocus/context switching/routing/memory expansion. Legacy and API work remains untagged; /hashtags commands and index do not ingest generated labels. Evidence: npm run typecheck, npm run build, full npm test 1188/1188 pass. Regression tests: direct Main without dispatcher, API spoofing, queued/restarted work, persisted outbox retry without duplicate labels, worker question/status/result labels after new topic, cross-conversation denial, native/external SDK transcript/index boundaries. Independent owner ReviewService + dedicated ReviewWorkers on real persistent review ledger: passed, no findings, fingerprint a9718350a58509869a26549ad5d45eeae157657bbd11f8ea720452e76b783250; exact tree 81233e882da3e6dea8bbd970529de59bb3d39842. Earlier P2 attention-delivery label gap fixed and re-reviewed; complete ledger history retained. Protected commit/push/publish assertions passed before and after commit. Activation dependency: existing v0.1.134 rollout remains exclusively owned by worker 97cc012c. This PR does not duplicate or change that rollout. Normal integration/release/GitOps only after gates and prior rollout dependency; no direct main push or GitHub merge. No live activation claimed by this PR.
severus-snape closed this pull request 2026-11-01 18:05:52 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
harness/core!208
No description provided.