@chanlerdev/scorel 0.0.1 → 0.0.2

package/docs/spec/ship/S0077-auxiliary-session-title-generation.md

@@ -0,0 +1,95 @@
+# S0077: Auxiliary Session Title Generation
+
+## Goal
+
+Generate a useful session title after the first chat message without blocking the
+main assistant turn.
+
+The title pipeline should use the configured `auxiliary` model so small metadata work
+does not consume the user's primary/standard working model.
+
+## Scope
+
+### 1. Persistent title event
+
+Add a persistent metadata event:
+
+- `type`: `session_title_updated`;
+- `title`: sanitized generated or user-provided title;
+- `source`: `model` or `user`;
+- optional `model`: selected model summary used by model generation;
+- optional `derivedFrom`: event id and seq that the title was derived from.
+
+The event is not part of the conversation tree and must not render as a chat turn.
+Session summaries use the latest `session_title_updated.title`, then fall back to
+`session_header.meta.title`, then the session id.
+
+The event is intentionally reusable for future manual rename UX. V1 only implements
+`source: "model"`.
+
+### 2. Auxiliary model title generation
+
+After the first user message in a session:
+
+- if the session has no explicit header title and no prior title update event;
+- start a sidecar title generation task using role `auxiliary`;
+- do not block the main assistant runtime turn;
+- append `session_title_updated` when generation succeeds;
+- write diagnostics only when generation fails.
+
+The title prompt uses only the first user message text and a small system prompt. It
+must not use the full conversation context.
+
+Title generation runtime must not register coding tools.
+
+### 3. GUI/WebUI/session summary projection
+
+Session lists and top bars should pick up title update events through existing event
+streams and summary refresh paths. Transcript projectors ignore the event.
+
+## Not In Scope
+
+- Manual rename UI.
+- Title regeneration controls.
+- Deleting title history.
+- Streaming title generation tokens.
+- Blocking session creation or first assistant turn on title generation.
+
+## Acceptance Criteria
+
+- A first user message with no existing title can append `session_title_updated`.
+- Title generation uses the `auxiliary` role selection.
+- Explicit `CreateSessionMeta.title` suppresses automatic title generation.
+- Existing title update events suppress duplicate model generation.
+- Session summaries prefer the latest title update event.
+- GUI/WebUI transcript projectors ignore title metadata events.
+- Future manual rename can use the same event type with `source: "user"`.
+
+## Test Requirements
+
+- Protocol tests cover the new persistent event shape.
+- Session store tests cover append/load validation for title events.
+- Daemon embedded tests cover first-message auxiliary title generation and explicit-title suppression.
+- Session summary tests cover latest title event wins.
+- GUI/WebUI projector tests cover ignoring title metadata events.
+- Run focused tests plus `pnpm typecheck && pnpm test`.
+
+## Impacted Files
+
+- `packages/protocol/src/events.ts`
+- `packages/protocol/src/index.test.ts`
+- `packages/core/src/session/index.ts`
+- `packages/core/src/session/session.test.ts`
+- `packages/daemon/src/index.ts`
+- `packages/daemon/src/embedded/embedded.test.ts`
+- `packages/daemon/src/projects/sessions.ts`
+- `apps/gui/src/renderer/chatbox/projector.ts`
+- `apps/webui/lib/events/projector.ts`
+- `docs/ROADMAP.md`
+
+## Risks And Boundaries
+
+- Title generation appends a persistent metadata event, so `currentSeq` advances.
+- V1 should not update summary sort order solely because a model generated a title.
+- If auxiliary model config is missing or invalid, the chat should continue and only a
+  diagnostic should be written.

package/docs/spec/ship/S0078-gui-provider-settings-forward-config-and-simplification.md

@@ -0,0 +1,150 @@
+# S0078: GUI Provider Settings Forward Config And Simplification
+
+## Goal
+
+Keep the GUI model settings path forward-only after the S0073 provider/model profile
+contract:
+
+- user config should use the current provider/model profile shape, not the old single
+  `[model]` shape;
+- Provider and Model settings must present the user workflow, not internal config ids
+  or generated defaults. Provider model cards are the place where users select a model
+  and correct provider-reported model metadata.
+
+The business outcome is that a user can configure real providers and choose models
+without needing to understand Scorel's internal TOML schema or default model parameters.
+
+## Scope
+
+### 1. Forward config only
+
+Scorel is still pre-release. Do not add compatibility recovery for deprecated
+development-stage model config:
+
+- `[model]`;
+- `[models.*]`.
+
+Those shapes should continue to fail through the schema path. Local user config should
+be rewritten to the current provider/model profile structure instead of adding runtime
+or GUI fallback logic.
+
+### 2. Provider settings simplification
+
+Provider settings should show only the user-facing provider fields:
+
+- provider name;
+- Base URL;
+- API Key, either direct or environment-variable based;
+- model list;
+- per-model selection and advanced model parameters.
+
+Internal fields such as provider id, provider type, provider protocol/API shape, and
+provider model keys should be generated or preserved by the application and not exposed
+as first-class controls. New Provider forms must not prefill development provider,
+endpoint, channel, API key, or model values.
+
+### 3. Provider-owned model selection and parameters
+
+Provider model cards own the model lifecycle:
+
+- a selected Provider model is the same thing as a Scorel available model;
+- selected models can be unselected;
+- configured models remain editable after selection;
+- model display name, model id, context window, max tokens, reasoning, developer-role
+  support, and image-input support can be corrected from the Provider model card;
+- model configuration opens in a modal instead of expanding inline in the model grid;
+- new Provider models get explicit editable defaults for context window, max tokens, and
+  reasoning instead of an empty advanced panel;
+- Provider/model ownership must be visible in the list without exposing generated ids.
+
+### 4. Model settings simplification
+
+Model settings should show model choices in user language:
+
+- model name;
+- model id;
+- provider ownership when displaying existing models.
+
+Do not show available-model ids or provider-model keys. Do not provide a second
+"add available model" form on the Model page; the Model page only consumes models
+selected from Provider settings and assigns work roles.
+
+## Not In Scope
+
+- Provider marketplace, pricing, ranking, routing policy, or fallback chains.
+- OAuth or OS keychain storage.
+- Changing runtime model selection semantics from S0073.
+- Automatic compatibility migration for old config shapes.
+- Deleting providers or models.
+- Full model-generation smoke tests from the GUI. Provider and model test controls may
+  use the existing real provider catalog path until a dedicated generation-test RPC is
+  added.
+- Exposing pi-ai compatibility switches that Scorel does not yet pass through
+  `resolvePiAiModel`.
+- Image generation output. pi-ai exposes image input in the current `Model.input`
+  contract, but Scorel's message protocol and runtime do not yet have an image-output
+  product path.
+
+## Acceptance Criteria
+
+- `~/.scorel/config.toml` uses the provider/model profile contract, not `[model]`.
+- `list_models` surfaces deprecated `[model]` / `[models.*]` config as schema errors
+  instead of compatibility recovery.
+- Provider settings do not render provider id, provider type, provider model key,
+  or default development provider/model values.
+- Provider model cards render user-facing configuration for model name, model id,
+  context window, max tokens, reasoning, developer-role support, and image-input
+  support.
+- Image-input support persists through config and maps to pi-ai `Model.input`.
+- Provider model configuration appears in a modal; opening one model does not change the
+  height of adjacent model cards.
+- Provider settings autosave on field blur. Model configuration autosaves on field blur
+  or checkbox changes. The main Provider page does not render a separate Save Provider
+  or Test Provider button.
+- Model test controls live next to each model's select/config controls. Passing tests
+  show a green check state; failing tests show a red cross state and a readable message
+  above the model list.
+- A selected Provider model can be unselected, and config rendering removes the
+  corresponding available model without leaving invalid role references.
+- Model settings uses Chinese labels for the visible workflow.
+- Existing provider/model ownership remains visible in a readable form.
+- GUI-created provider models do not write hidden context-window, max-token, or
+  reasoning defaults unless the user enters them in the model configuration.
+- The Model page does not render "模型来源" or "加入可用模型"; it only assigns roles
+  from already selected models.
+- The sidebar "New chat" action returns to the initial composer for the current or
+  fallback project and does not create a session until the user sends the first message.
+
+## Test Requirements
+
+- Core config test covers custom provider models without generated runtime metadata.
+- Daemon embedded test covers `list_models` surfacing old `[model]` as a schema error.
+- GUI renderer test covers simplified Provider and Model settings labels and hidden
+  internal fields.
+- Core config test covers Provider model metadata updates and available-model removal.
+- Run:
+  - `pnpm --filter @scorel/core test -- config.test.ts -t "without generated runtime metadata"`
+  - `pnpm --filter @scorel/daemon test -- embedded.test.ts -t "deprecated single model config"`
+  - `pnpm --filter @scorel/app-gui test -- gui-shell.test.tsx`
+  - `pnpm --filter @scorel/app-gui typecheck`
+  - `pnpm typecheck && pnpm test`
+
+## Impacted Files
+
+- `packages/core/src/config/index.ts`
+- `packages/daemon/src/index.ts`
+- `packages/daemon/src/embedded/embedded.test.ts`
+- `apps/gui/src/renderer/settings/sections/ModelSection.tsx`
+- `apps/gui/src/renderer/settings/sections/ProviderSection.tsx`
+- `apps/gui/src/renderer/gui-shell.test.tsx`
+- `docs/ROADMAP.md`
+- `~/.scorel/config.toml`
+
+## Risks And Boundaries
+
+- Hiding advanced runtime metadata means coding tool budgets fall back to existing
+  internal defaults when the provider model does not specify a context window. That is
+  acceptable for the main Settings flow; if those values need user control, add a later
+  advanced settings spec instead of leaking them into the basic provider form.
+- Do not add deprecated aliases, old-shape migration, or GUI fallback logic while Scorel
+  is still in forward-only pre-release development.

package/docs/spec/ship/S0079-gui-sidebar-layout-controls.md

@@ -0,0 +1,49 @@
+# S0079: GUI Sidebar Layout Controls
+
+## Goal
+
+Fix the GUI sidebar layout so long Project and Session titles stay inside the
+sidebar, and add basic desktop controls for resizing and collapsing the sidebar.
+
+## Scope
+
+- Clip sidebar Project and Session titles to a single line with ellipsis.
+- Prevent horizontal scrolling in the sidebar session list.
+- Add a sidebar resize handle with bounded width.
+- Add a macOS-style sidebar collapse button in the sidebar titlebar area.
+- Add a matching expand button in the topbar when the sidebar is collapsed.
+
+## Non-goals
+
+- Persist sidebar width across app launches.
+- Add keyboard shortcuts or menu commands.
+- Change Host, Relay, Session JSONL, provider, or model selection behavior.
+
+## Acceptance Criteria
+
+- Long sidebar titles do not create a horizontal scrollbar.
+- Session titles expose their full value through the native title tooltip.
+- Users can drag the sidebar edge between a safe minimum and maximum width.
+- Users can collapse and re-expand the sidebar from the window chrome area.
+
+## Tests
+
+- GUI rendering tests cover the sidebar collapse and resize affordances.
+- GUI CSS contract tests cover horizontal overflow prevention and text clipping.
+- `pnpm typecheck && pnpm test` passes.
+
+## Impacted Files
+
+- `apps/gui/src/renderer/App.tsx`
+- `apps/gui/src/renderer/shell/Sidebar.tsx`
+- `apps/gui/src/renderer/shell/ProjectTree.tsx`
+- `apps/gui/src/renderer/workspace/Topbar.tsx`
+- `apps/gui/src/renderer/workspace/Workspace.tsx`
+- `apps/gui/src/renderer/styles.css`
+- GUI renderer tests
+
+## Risks
+
+- Resize mouse listeners must be removed on mouseup to avoid stale global
+  handlers.
+- Collapsed sidebar must not hide the only way to expand the sidebar again.

package/docs/spec/ship/S0080-session-title-hook-and-gui-markdown-dark-code.md

@@ -0,0 +1,58 @@
+# S0080: Session Title Hook And GUI Markdown Dark Code
+
+## Goal
+
+Move automatic session title generation into a general session lifecycle hook and
+fix GUI Markdown code block colors in dark mode.
+
+## Scope
+
+- Schedule title generation from an `afterUserMessage` lifecycle hook after the
+  first `user_message` has been persisted.
+- Keep title generation on the configured `auxiliary` model.
+- Keep title generation off the main assistant response path: it starts after
+  the first user message persists and must not wait for the assistant answer.
+- Preserve the existing persistent `session_title_updated` event contract.
+- Use a dark Shiki theme for GUI fenced Markdown code blocks.
+
+## Non-goals
+
+- Add manual rename UI.
+- Add user-visible title regeneration controls.
+- Build a full public extension runtime.
+- Change WebUI Markdown rendering.
+
+## Acceptance Criteria
+
+- `#runUserTurn` does not directly call the title generator.
+- The lifecycle hook is scheduled after the first user message is appended and
+  before the assistant runtime turn starts.
+- The lifecycle hook can run concurrently with the assistant runtime, while
+  persistent JSONL appends remain serialized.
+- The title prompt uses a dedicated system prompt and a wrapped user request so
+  the auxiliary model summarizes the request instead of answering it.
+- The title hook still selects role `auxiliary`.
+- GUI Markdown fenced code blocks no longer use the light GitHub Shiki theme.
+
+## Tests
+
+- Daemon tests cover the session lifecycle hook structure.
+- Existing embedded daemon tests still cover auxiliary title generation.
+- GUI tests cover dark Shiki theme selection.
+- `pnpm typecheck && pnpm test` passes.
+
+## Impacted Files
+
+- `packages/daemon/src/index.ts`
+- `packages/daemon/src/session-hooks.test.ts`
+- `apps/gui/src/renderer/chatbox/ShikiCodeBlock.tsx`
+- `apps/gui/src/shiki-theme.test.ts`
+- `docs/ROADMAP.md`
+
+## Risks
+
+- The title generation hook must not block the assistant turn.
+- The title generation hook must not append events concurrently with the runtime
+  loop in a way that corrupts JSONL order or sequence numbers.
+- Dark Shiki tokens must not override the app's inline code styling outside
+  fenced code blocks.

package/docs/spec/ship/S0081-automatic-memory.md

@@ -0,0 +1,117 @@
+# S0081: Automatic Memory Context And Dreaming
+
+> Updated by [`S0082`](S0082-memory-journal-tool-and-idle-dream.md): daily is now written through the agent-owned `AppendDaily` tool, and dream consolidation runs after project idle time instead of immediately after every turn.
+
+## Goal
+
+Ship Scorel's first automatic memory loop:
+
+- inject memory context into the actual LLM `messages[]` via `harness_item kind="memory"`;
+- automatically write a short project daily entry after completed turns;
+- automatically consolidate durable project/root memory with the configured `auxiliary` model when available;
+- expose GUI Settings controls for memory;
+- support the macOS standard `Command+,` shortcut to open Settings.
+
+The business value is continuity: a new or resumed session should know recent work, stable project decisions, and cross-project user preferences without the user manually asking the agent to read notes.
+
+## Scope
+
+### Memory Files
+
+Use filesystem-backed memory under the fixed user root:
+
+```text
+~/.scorel/memory/
+  MEMORY.md
+  projects/
+    <projectId>/
+      MEMORY.md
+      daily/
+        YYYY-MM-DD.md
+      dream-state.json
+```
+
+### Runtime Context
+
+Memory content must enter the model through `messages[]`, not through duplicated provider-level `systemPrompt` text.
+
+`instruction_snapshot.memory` remains a schema/diagnostic section, but S0081 does not use it to carry memory content or policy.
+
+### Automatic Daily
+
+After a completed turn, Scorel appends one short daily entry automatically. The entry is generated from the completed turn evidence and written by the runtime, not by relying on the main assistant to call a tool.
+
+### Automatic Dream
+
+When enabled, Scorel uses the `auxiliary` model after a completed turn to consolidate:
+
+- project `MEMORY.md` from recent turn evidence and current project memory;
+- root `MEMORY.md` only for clearly cross-project/stable preferences.
+
+If no auxiliary model is configured or model execution fails, the main turn still succeeds; Scorel writes diagnostics and keeps daily/context memory working.
+
+### GUI Settings
+
+GUI Settings must expose memory controls for the selected project:
+
+- enable memory;
+- enable automatic daily;
+- enable automatic project dream;
+- enable root memory promotion.
+
+The Settings view must be openable with `Command+,` on macOS and `Ctrl+,` elsewhere through the Electron application menu.
+
+## Not In Scope
+
+- Topic memory files.
+- Semantic recall selectors.
+- Full activity recorder.
+- Per-turn vector search.
+- Cloud sync.
+- Editing memory files in GUI.
+- Blocking the user turn on memory consolidation success.
+
+## Acceptance Criteria
+
+- New sessions append a hidden `harness_item kind="memory"` before the user message is assembled into context.
+- `buildContext()` surfaces that memory harness as a `<system-reminder>` in `messages[]`.
+- Provider `systemPrompt` does not contain root/project/daily memory contents.
+- Completed turns automatically append to project daily when memory daily is enabled.
+- Completed turns attempt auxiliary consolidation when automatic dream is enabled.
+- Project `MEMORY.md` can be updated automatically from completed turn evidence.
+- Root `MEMORY.md` can be updated only for stable global preferences, and can be disabled independently.
+- Missing config or missing auxiliary model does not fail the user turn.
+- GUI Settings renders a Memory section with real controls.
+- `Command+,` / `Ctrl+,` opens GUI Settings.
+
+## Testing Requirements
+
+- Unit tests for memory paths, rendering, daily append, and deterministic fallback extraction.
+- Config tests for `[memory]` parsing/rendering.
+- Daemon tests proving memory harness injection and daily append after a completed turn.
+- GUI render tests proving Memory Settings controls are visible.
+- Source-level or unit test proving the Electron menu binds `CommandOrControl+,` to Settings.
+
+## Impacted Files
+
+- `packages/core/src/config/index.ts`
+- `packages/core/src/memory/*`
+- `packages/core/src/index.ts`
+- `packages/daemon/src/index.ts`
+- `packages/protocol/src/events.ts`
+- `packages/protocol/src/wire.ts`
+- `packages/client/src/index.ts`
+- `apps/gui/src/main.ts`
+- `apps/gui/src/main/local-host.ts`
+- `apps/gui/src/shared/ipc.ts`
+- `apps/gui/src/preload.ts`
+- `apps/gui/src/renderer/App.tsx`
+- `apps/gui/src/renderer/settings/*`
+- tests near the changed modules
+
+## Risks And Boundaries
+
+- Memory can become stale. The harness reminder must tell the model to verify current code facts from the repo.
+- Automatic memory must be best-effort. It must not fail the main user turn.
+- Root promotion is high-risk. S0081 only promotes clearly global preferences and keeps project facts inside project memory.
+- Daily is recent context, not source of truth. Session JSONL remains the authoritative evidence chain.

package/docs/spec/ship/S0082-memory-journal-tool-and-idle-dream.md

@@ -0,0 +1,107 @@
+# S0082: Memory Journal Tool And Idle Dream
+
+## Goal
+
+Refine S0081 memory so daily is owned by the agent main loop and dream is delayed until project idle time.
+
+The business value is better memory quality: the agent records daily evidence while it still has full task context, and the auxiliary dreamer consolidates a continuous session/project slice instead of prematurely freezing every turn.
+
+## Scope
+
+### AppendDaily Tool
+
+Add a built-in `AppendDaily` tool when memory and daily are enabled.
+
+The tool is append-only and writes to:
+
+```text
+~/.scorel/memory/projects/<projectId>/daily/YYYY-MM-DD.md
+```
+
+The model passes structured journal data:
+
+- `summary`
+- `completed`
+- `decisions`
+- `followUps`
+- `memoryCandidates`
+
+The daemon/core owns the actual path, date, append format, and validation. The model does not edit daily files through generic file tools.
+
+### Prompt Contract
+
+The baseline prompt tells the agent to call `AppendDaily` once near the end of meaningful completed work when the tool is available.
+
+This prompt is a tool-use contract. It must not carry root/project/daily memory content. Memory content continues to enter `messages[]` through the existing hidden memory harness.
+
+### Idle Dream
+
+Remove per-turn dream consolidation.
+
+After `AppendDaily` succeeds, daemon marks the project dirty and schedules dream after `memory.dreamIdleMinutes`.
+
+Rules:
+
+- new daily append resets the timer;
+- `dreamIdleMinutes = 0` means run as soon as the event loop is idle, mainly for tests/debugging;
+- dream uses the auxiliary model;
+- dream updates project `MEMORY.md`;
+- dream may update root `MEMORY.md` only when `promoteRoot` is enabled;
+- dream failure never fails the user turn.
+
+### Settings
+
+Extend memory settings with:
+
+```toml
+[memory]
+dreamIdleMinutes = 60
+```
+
+GUI Settings must expose the idle delay.
+
+## Not In Scope
+
+- Full activity recorder.
+- Topic memory files.
+- Vector or semantic recall.
+- Manual dream trigger.
+- GUI memory file editor.
+- Persistent cross-process dream scheduler after host process exit.
+
+## Acceptance Criteria
+
+- `AppendDaily` is available to the main chat runtime only when memory and daily are enabled.
+- `AppendDaily` appends structured daily content to the fixed project daily path.
+- Completed turns no longer write daily from daemon-side `userText + assistantText` fallback.
+- Completed turns no longer run auxiliary dream immediately.
+- Successful `AppendDaily` schedules idle dream according to `dreamIdleMinutes`.
+- Idle dream reads current memory and recent daily evidence, then writes project/root memory from auxiliary model output.
+- `dreamIdleMinutes` is parsed/rendered in config and exposed in GUI Settings.
+- Memory content still enters the LLM through `messages[]` memory harness, not provider system prompt.
+
+## Testing Requirements
+
+- Core tests for `AppendDaily` formatting and append-only behavior.
+- Provider/tool schema test coverage through existing tool conversion path.
+- Daemon test proving daily is written by `AppendDaily`.
+- Daemon test proving idle dream updates project/root memory.
+- GUI test proving idle delay control renders.
+- Full `pnpm typecheck && pnpm test`.
+
+## Impacted Files
+
+- `packages/core/src/memory/*`
+- `packages/core/src/config/index.ts`
+- `packages/core/src/provider/pi-ai.ts`
+- `packages/core/src/instructions/index.ts`
+- `packages/daemon/src/index.ts`
+- `packages/protocol/src/events.ts`
+- `apps/gui/src/renderer/settings/*`
+- tests near the changed modules
+
+## Risks And Boundaries
+
+- The agent may forget to call `AppendDaily`. This is acceptable for V1; the tool contract and prompt make the desired behavior explicit without daemon fabricating journal content.
+- The idle timer is in-process. If the host exits before the timer fires, daily evidence remains durable and can be consolidated by a future manual or scheduled dream feature.
+- Root promotion remains high-risk and must stay constrained to stable cross-project preferences.