Skip to content

feat(discord): read bounded exact native conversation history - #271

Draft
johoja12 wants to merge 3 commits into
upstream/discord-05-native-inputfrom
upstream/discord-06-canonical-history
Draft

johoja12 wants to merge 3 commits into
upstream/discord-05-native-inputfrom
upstream/discord-06-canonical-history

Conversation

@johoja12

Copy link
Copy Markdown
Owner

Add exact local/SSH transcript readers, owned runtime/profile binding, bounded hashed cursors, durable history boundaries/warnings, and native execution provenance. The delivery metadata store is an opt-in Full-mode component; default Notifications is not connected to it. SSH reads use the separate bounded read transport. Codex pins reuse upstream persisted launch config; remote Claude adoption remains distinct from first-hand hooks.

Part of #258; tracks #261. Dependency: upstream/discord-05-native-input. This draft is a focused stacked preparation PR in the fork, not a production merge or an upstream review request. Promote after prerequisites merge and rebased CI passes. Upstream split guidance: Ark0N#769; first independent ready slice: Ark0N#832 (both required checks green).

Validation: 121 component cases passed across the primary run and targeted rerun; source typecheck passed. Bridge retry/multipart integration assertions are deferred to the wiring slice rather than pulling bridge behavior into this reader PR.

Production is unchanged. No agent recovery, live terminal input, Discord sends, version bump, or deployment was performed for this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant