The main addition is a transient-message protection layer designed for the exact case you described: a message appears in ChatGPT, then disappears after voice mode ends, refresh, navigation, or a ChatGPT-side rollback.

• RootLine now performs a fast provisional capture after ~320 ms, instead of relying only on the existing ~1100 ms stable capture.
• That early capture can preserve visible assistant text even while ChatGPT is still updating.
• When the normal stable capture arrives later, RootLine promotes the provisional record rather than storing a duplicate.
• RootLine now forces a best-effort capture on:
• page hide
• browser refresh/navigation
• route/conversation changes
• pagehide
• beforeunload

The practical change is:

If a user or assistant turn becomes visibly readable in the ChatGPT window, RootLine now has a much better chance of preserving it locally even if ChatGPT later stops showing or returning that turn.

R0.0.30 also keeps the previous R0.0.29 global error-UI containment fix, so runtime errors should no longer expand normal UI rows into large red blocks.

The existing archive format and storage schema were preserved; this was an additive capture-hardening build, not a database migration.

RootLine R0.0.2 is a stability and hierarchy-focused release that also corrects a critical RootScribe verification issue.




RootScribe no longer treats existing archive JSON or backend transcript data as sufficient proof of completeness.

A PDF may now be marked as:

FULL CAPTURE VERIFIED

only after RootScribe successfully:

1. Opens and activates the target ChatGPT conversation.
2. Sweeps the live ChatGPT conversation.
3. Traverses the virtualized message list back to the start.
4. Confirms stable overlap and message identity between traversal windows.
5. Reconciles the swept conversation into RootLine storage.
6. Performs an independent archive readback verification.
7. Confirms the complete-capture verification gate.

Existing JSON and archived conversation data may still be used for recovery and reconciliation, but they can no longer authorize a Complete PDF on their own.

If the live sweep cannot prove completeness, RootScribe must not report the export as a verified full capture.




RootLine now uses the normal release version:

R0.0.2


Previous Beta-style identifiers such as:

R0.0.1.B0.0.0.xx


are no longer used for normal releases.

Release files now follow the simplified naming convention:

RootLine.R0.0.2.zip
RootLine_Firefox_Addon_R0.0.2.xpi




Application versioning is now separated from RootLine storage compatibility.

The application version is:

R0.0.2


while storage compatibility is tracked independently through the RootLine storage schema.

This prevents normal application updates from incorrectly displaying a Storage Mismatch warning when the underlying data format remains compatible.



RootLine hierarchy behavior now supports safer and more flexible organization.


RootLine organizational containers may be deleted:

• Clusters
• Trees
• Branches

Chats themselves cannot be deleted through RootLine.

When a container containing Chats is deleted:

Delete Container
↓
Remove RootLine structure
↓
Preserve Chats
↓
Chats become Orphan Chats


The underlying ChatGPT conversations and local archives remain untouched.



A Cluster may be moved inside another Cluster and converted into a Tree where the hierarchy remains valid.

During conversion:

Cluster
├── Chat
└── Tree


can become:

Tree
├── Chat
└── Branch


Existing child Trees are converted to Branches.

A Cluster cannot be moved into anoth