Shumora 1.0.0

Changes since Shumora 0.1.0.

Terminals

Rename AI Workspace to Terminals and improve navigation for managing Pi sessions.
Arrange sessions in nested split layouts, resize panes, and move or merge tab groups without restarting their terminals.
Reorder session tabs by dragging them horizontally and keep tabs usable in narrow groups.
Choose a working folder for individual sessions and for new terminals created in a group.
Improve Pi executable discovery when Shumora is launched from a desktop environment.

Bring existing Pi agents together for an automatic discussion, with a topic, optional participant roles, and either you or an AI participant as moderator.
Run two discussion rounds with a turn for your input after each round, followed by a final summary. Continue without a message when you have nothing to add.
Read discussions in a group-chat layout: agent replies on the left, your messages on the right, consecutive messages grouped by author, and a clearly labeled final summary.
Use larger message text, a dedicated scrolling conversation, a consistent message composer, and a member list available from the discussion header.
Keep your reading position when replies arrive. A new-message button lets you jump to the latest replies when you are ready.
Pause, resume, stop, or take over moderation without leaving the discussion. Switching pages does not interrupt it.
Render Markdown replies with raw HTML and remote images disabled.
Package the Council bridge extension outside the application archive so the external Pi runtime can load it in installed builds.
Show agent connection and availability states. Newly opened Shumora Pi terminals connect automatically; existing unconnected terminals are not silently restarted.
Use each participant's existing model, credentials, and context. Tools are blocked during Council turns: discussion does not execute proposed work.

View the focused terminal's Git repository status, current branch, changed-file count, and line-change statistics from the workspace toolbar.
Review staged and unstaged changes in a side-by-side diff, including untracked files and conflict markers.
Stage or unstage files, stage or unstage all changes, and discard changes with confirmation.
Create commits from Shumora. Optionally generate an editable commit message from the staged diff using a selected model through 9router.
Search, create, and switch local or remote branches, with confirmation when changes or other active sessions may be affected and an option to stash before switching.
Fix repository-status visibility and split-layout integration after the source-control merge.
Reload the selected diff after status refreshes so edits remain visible even when line counts are unchanged or the file is untracked.

Browse the Pi package gallery for extensions, skills, themes, and prompts, with search, type filters, sorting, and pagination.
Open standalone package details with previews, installation status, and install, update, repair, or uninstall controls for your personal Pi configuration.
Add Pi plugin details and lifecycle management for supported global npm installations.
Show package and plugin update banners scoped to the current Library section, with more stable loading layouts.
Keep installation output scoped to the current details visit and avoid showing a large empty output panel before an operation starts.
Recommend setup for missing Pi and optional 9router installations without silently installing them.

Add persistent English and Indonesian interface language preferences. Terminal output, user content, and AI replies remain unchanged.
Add an automatic theme option that follows the operating system, alongside the existing light and dark modes.
Unify application scrollbars across light and dark themes, including horizontal scrollbars, hover states, and high-contrast support. Terminal scrollbar chrome remains hidden.
Connect shared modal colors to the application palette, fixing the release-notes dialog and other default dialogs when switching themes.
Use the Shumora logo for application and platform packaging icons.

Pi must be installed separately and configured with access to a model provider. Package and plugin operations can require stopping active sessions first.
Council initially supports bridge-enabled Pi terminals and requires at least two available participants. Each participant uses its own model credits; final recommendations still require your review before execution.
Commit-message generation sends the staged diff to the selected model through 9router. Review sensitive changes before using it.
Session processes and workspace layouts are not restored automatically after exit.
Installers remain unsigned unless signing is configured separately. Version 1.0.0 does not imply that every platform or live-agent scenario has been validated.