feat: supply bounded hashtag history before inference #212

Merged
severus-snape merged 1 commit from feat/hashtag-context-selection into main 2026-11-01 20:53:09 +00:00
Collaborator

Fresh operator authorization: Dann implementiere das! Small context-selection slice, base d79931c. No status-label changes borrowed from PR210; no new topic engine.

Host snapshots existing conversation-scoped hashtag references on the durable original assignment; exact worker dependencies and continuations inherit that snapshot. Before inference, native/external runtime history supplies at most eight deduplicated user excerpts (800 chars each), with source session/message IDs. Unknown tags report empty hits; no untrusted tool/quoted tag selection, recursive lookup, generated-context indexing, extra inference, reset or purge. Existing mixed SDK history remains: relevance, NOT hard isolation. Original permissions and current instructions retain precedence. Memory policy and /hashtags lookup unchanged.

Validation: typecheck + build pass; full npm test 1195/1195 pass. Initial full run had six missing Matrix native binary failures due ignore-scripts installation; installed the pinned dependency binary via its own downloader, then complete suite passed. Tests capture actual Harness prompt options for distinct alpha/beta, no-hit/untagged, native/external restart, exact restarted worker dependency after parent topic change, API spoof denial and cross-conversation denial.

Independent ReviewService + dedicated ReviewWorkers using persistent existing review ledger: passed with no findings, fingerprint 23f1cb9a83023c0bab5dbab1b2155465a399de93ca82b149b93000a47b1b7c27; commit/push/publish exact assertions allowed. HEAD 72b6e257c1, tree 586ce30273.

Main advanced independently through PR210/211; no rebase or unrelated diff borrowing. Normal required integration review/CI and coordinated GitOps only. No duplicate release/promotion, no live activation claimed, no GitHub merge. Publishing through existing owner pipeline after integration.

Fresh operator authorization: Dann implementiere das! Small context-selection slice, base d79931c. No status-label changes borrowed from PR210; no new topic engine. Host snapshots existing conversation-scoped hashtag references on the durable original assignment; exact worker dependencies and continuations inherit that snapshot. Before inference, native/external runtime history supplies at most eight deduplicated user excerpts (800 chars each), with source session/message IDs. Unknown tags report empty hits; no untrusted tool/quoted tag selection, recursive lookup, generated-context indexing, extra inference, reset or purge. Existing mixed SDK history remains: relevance, NOT hard isolation. Original permissions and current instructions retain precedence. Memory policy and /hashtags lookup unchanged. Validation: typecheck + build pass; full npm test 1195/1195 pass. Initial full run had six missing Matrix native binary failures due ignore-scripts installation; installed the pinned dependency binary via its own downloader, then complete suite passed. Tests capture actual Harness prompt options for distinct alpha/beta, no-hit/untagged, native/external restart, exact restarted worker dependency after parent topic change, API spoof denial and cross-conversation denial. Independent ReviewService + dedicated ReviewWorkers using persistent existing review ledger: passed with no findings, fingerprint 23f1cb9a83023c0bab5dbab1b2155465a399de93ca82b149b93000a47b1b7c27; commit/push/publish exact assertions allowed. HEAD 72b6e257c1aefdad8644c999115281f9fe77d197, tree 586ce302735576ef67b570b50373eb0dfed8c829. Main advanced independently through PR210/211; no rebase or unrelated diff borrowing. Normal required integration review/CI and coordinated GitOps only. No duplicate release/promotion, no live activation claimed, no GitHub merge. Publishing through existing owner pipeline after integration.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
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!212
No description provided.