Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Begins
Icod.TermInfo 1.13.0as Persistent-Raster Runtime Evidence Interchange and Integration.The release is intended to remove the manual bridge currently required after external/live verification: callers should no longer need to manufacture lifecycle/placement evidence, calculate final source ordinals, merge snapshots, and reclassify by hand.
The architecture remains deliberately protocol-neutral:
TermInfo still performs no live terminal I/O and retains no production dependency on
Icod.Terminal.Planning authorities
Icod.TermInfo-Post-1.0-Development-Roadmap.mdIcod.TermInfo-1.13.0-Persistent-Raster-Runtime-Evidence-Interchange-and-Integration-Roadmap.mddocs/superpowers/specs/2026-09-13-1.13.0-runtime-evidence-interchange-design.mdThe active long-range roadmap now identifies 1.13.0 as the next development line and defers multi-protocol preference/negotiation until after runtime-evidence interchange is mature.
Planned tranches
Compatibility boundary
1.13 must preserve:
Icod.Terminal.JSON v5 is planned to add exactly:
persistentRasterRuntimeObservationSetpersistentRasterRuntimeIntegrationExplicit exclusions
This release does not include live probing by TermInfo, protocol/backend identifiers, backend ranking/preference, multi-protocol negotiation, terminal-brand heuristics, session/resource identities, scene/layout policy, animation, image transport, or generic JSON deserialization.
The PR remains draft while the written design is reviewed. No production implementation has started yet.