To manage a game scenario with trees and tabs, use the tree for the full scene structure, role-based tabs for the material in use, and a scene ID such as SC12 as the return anchor. The article-specific Stage 4 check used a saved working copy and recorded three open tabs: SC12.md, 人物表.md, and 進行メモ1.md. The saved layout was named 本編・人物・進行 (“Manuscript, Cast, Progress”).
The unsaved-warning sequence—warning, Cancel, Save, and readback after relaunch—came from a separate supplemental desktop check. Stage 4 remains partial. Visual three-pane rendering, automatic restoration to the same pane, and relaunch recovery of unsaved content were not verified.
Define manuscript, cast, and progress-memo roles
Keep SC01 through SC24 in scene order in the tree. In this test, SC12.md held the manuscript role, 人物表.md held the cast role, and 進行メモ1.md held the progress-memo role. The memo records the target scene, the last checked line, and the next action without replacing the manuscript or cast reference.
The dedicated copy also contained 分岐表.md, and its existence was verified. It was a separate reference candidate to open when needed, not one of the three tabs actually opened in Stage 4. The central role set is manuscript, cast, and progress memo.
Search for SC12, open three tabs, and save h3
Run the article-specific workflow as one continuous procedure:
- Create a dedicated copy containing SC01–SC24, the cast sheet, the branch table, and two saved memo stand-ins.
- Assign the manuscript, cast, and progress-memo roles, and name the layout
本編・人物・進行. - Search the tree for SC12 and confirm that it returns one SC12.md file.
- Open SC12.md, 人物表.md, and 進行メモ1.md, then save the three-role state as an h3 layout.
- Close and reopen the workspace, confirm that the three tab records still point to those same files, and verify the SC12 return anchor again.
The twelve-operation record returned scenario_files=24, cast_files=1, branch_files=1, memo_files=2, and layout_pattern=h3. It also returned tabs_before_close=3, tabs_after_reopen=3, reopened_tab_count=3, and tree_sc12_matches=1. Passing requires the measured roles and file paths, not merely a count of three tabs.
This result shows that the saved workspace record yielded the same three tab paths and the SC12 anchor after close/reopen. It does not show that three panes appeared in the expected visual positions or that each tab returned automatically to the same pane.
Keep the unsaved-warning check as a supplemental procedure
Use this separate procedure when checking an unsaved copy of SC12:
- Add a test line to the SC12 copy and close its tab to display the save warning.
- Choose Cancel first and confirm that both the tab and unsaved line remain in the editor.
- Recheck that the destination is the SC12 copy, then choose Save and close the copy.
- Relaunch the app, reopen the same copy, and read back the saved line.
The supplemental desktop check displayed Save, Don’t Save, and Cancel. After Cancel, the unsaved line remained. A separate saved version contained three lines and 25 characters, and its saved test line was displayed again after relaunch.
Don’t Save was verified only as a label indicating discard intent; it was not selected, so its result remains unverified. The relaunch check read saved content. It did not demonstrate recovery of content that remained unsaved when the app quit.
Preserve the Stage 4 and supplemental boundaries
Rune Studio’s public documentation describes a file tree, tabs, split views, saved layouts, and a warning before closing an unsaved tab. Those are Stage 3 product capabilities. The twelve article-specific operations are a Stage 4 check with saved samples; warning, Cancel, Save, and relaunch readback belong to the supplemental desktop check.
Because the CLI cannot create tabs that retain unsaved content, the two Stage 4 memos are saved stand-ins. Visual three-pane rendering, automatic restoration to the same pane, the result after selecting Don’t Save, and relaunch recovery of unsaved content remain unverified. The existing status, facts, and limits therefore remain partial.
If the working state breaks, return to the saved h3 layout 本編・人物・進行 and the original workspace. Reopen SC12.md, 人物表.md, and 進行メモ1.md from the role map, then search the tree for SC12 again. Do not infer or reconstruct unsaved content.
Keep the role map distinct from nearby layout work
STUDIO-589 aligns two drafts by scene headings. STUDIO-335 returns from a three-pane context to the next sentence. STUDIO-451 follows relative paths after manuscripts and images move. This article defines manuscript, cast, and progress-memo roles, finds SC12 in the tree, saves the measured three tabs and h3 layout, and checks the same roles and SC12 anchor after reopening.
The practical rule is to keep SC12.md, 人物表.md, and 進行メモ1.md fixed as the manuscript, cast, and progress-memo roles. For an unsaved warning, choose Cancel first and only read back content that was explicitly saved. The conclusion remains partial if you need proof of visual three-pane rendering, automatic same-pane restoration, or relaunch recovery of unsaved content. Tree, tab, and layout support is listed on the Rune Studio product page.
