Give hot ops shared attributes, and close an interaction with a flagged Meta op

[TrueDoctor]

No description provided.

[cubic-dev-ai]

1 issue found across 10 files

Confidence score: 3/5

• In node-graph/rfcs/document-format.md, retiring Meta can remove the only interaction_end marker after the last write, leaving undo without the boundary it uses to stop. Preserve that marker or ensure the replacement format provides an equivalent boundary.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="node-graph/rfcs/document-format.md">

<violation number="1" location="node-graph/rfcs/document-format.md:160">
P2: Dropping the `Meta` op at retirement removes the only `interaction_end` marker when the boundary follows the last write. Undo walks the first-parent chain and stops only at an `interaction_end` boundary, so it would merge this interaction into the previous one. State that retirement sets `interaction_end` on the author's last retired delta before dropping the `Meta` op.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>