✨ feat(core): Add notification/share APIs & simplify orchestration planning schema

.env.example

@@ -7,7 +7,7 @@
 # * Meeseeks Settings
 # - VERSION: Version of your application (There is no need to change these value)
 # - ENVMODE: Environment mode of your application (valid options: dev, prod)
-VERSION=2.1.0-alpha
+VERSION=0.0.7
 ENVMODE=dev
 LOG_LEVEL=DEBUG
 CACHE_DIR='/path/to/cache/directory'

.github/workflows/uv-lock-refresh.yml

@@ -0,0 +1,35 @@
+name: Refresh uv.lock
+
+on:
+  schedule:
+    - cron: "0 4 * * 1"
+  workflow_dispatch:
+  push:
+    paths:
+      - "pyproject.toml"
+      - "**/pyproject.toml"
+      - "uv.lock"
+
+jobs:
+  refresh-lock:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+      - name: Install uv
+        uses: astral-sh/setup-uv@v7
+      - name: Update lockfile
+        run: uv lock
+      - name: Create pull request
+        uses: peter-evans/create-pull-request@v8
+        with:
+          branch: chore/uv-lock-refresh
+          delete-branch: true
+          title: "chore(uv): refresh lockfile"
+          commit-message: "chore(uv): refresh lockfile"
+          body: |
+            - Automated uv.lock refresh.
+            - Runs `uv lock` at repo root.

README.md

@@ -19,7 +19,7 @@ https://github.com/user-attachments/assets/78754e8f-828a-4c54-9e97-29cbeacbc3bc
 
 # Intro
 
-Meeseeks is an AI task agent assistant built on a plan-act-observe orchestration loop. It breaks a request into steps, runs tools, and synthesizes a final reply. It keeps a session transcript, compacts long histories, and stores summaries for continuity across longer conversations.
+Meeseeks is an AI task agent assistant built on a plan → tool selection → step execution loop. It breaks a request into steps, chooses tools per step, runs them, and synthesizes a final reply. It keeps a session transcript, compacts long histories, and stores summaries for continuity across longer conversations.
 
 <details>
 <summary><i>Legends (Expand to View) </i></summary>
@@ -61,8 +61,9 @@ We are upgrading the API backend to better support a task-orchestration frontend
 </table>
 
 ## Core workflow
-- (✅) **Plan → act → observe loop:** Builds a short action plan, executes tools, and replans when needed.
-- (✅) **Step-level reflection:** Validates tool outcomes and adjusts step arguments when required.
+- (✅) **Plan → select tools → execute:** Builds a short plan, chooses the right tools per step, and executes them.
+- (✅) **Step-level reflection:** Validates tool outcomes and adjusts tool inputs when required.
+- (✅) **Plan updates:** Emits updated action plans after each step so UIs can refresh the to‑do list.
 - (✅) **Synthesized replies:** Produces a final answer after tool results are collected and summarized.
 
 ## Memory and context management
@@ -101,6 +102,7 @@ Optional features that can be installed when needed.
 - **Inline approvals.** Rich-based approval prompts render with padded, dotted borders and clear after input.
 - **Unified experience.** Web, API, Home Assistant, and CLI interfaces share the same core engine to reduce duplicated maintenance.
 - **Shared session runtime.** The API exposes polling endpoints; the CLI runs the same runtime in-process for sync execution, cancellation, and summaries.
+- **Event payloads.** `action_plan` steps are `{title, description}`; `tool_result`/`permission` use `tool_id`, `operation`, and `tool_input`.
 
 ## Monorepo layout
 
@@ -134,6 +136,10 @@ flowchart LR
   subgraph Core["Core Orchestration\n(packages/meeseeks_core)"]
     TaskMaster["orchestrate_session\n(task_master.py)"]
     Orchestrator["Orchestrator\n(orchestrator.py)"]
+    Planner["Planner\n(planning.py)"]
+    ToolSelector["ToolSelector\n(planning.py)"]
+    StepExecutor["StepExecutor\n(planning.py)"]
+    PlanUpdater["PlanUpdater\n(planning.py)"]
     ActionPlanRunner["ActionPlanRunner\n(action_runner.py)"]
     ContextBuilder["ContextBuilder\n(context.py)"]
     ActionStep["ActionStep\n(classes.py)"]
@@ -176,6 +182,10 @@ flowchart LR
   SessionRuntime --> RunRegistry
 
   TaskMaster --> Orchestrator
+  Orchestrator --> Planner
+  Orchestrator --> ToolSelector
+  Orchestrator --> StepExecutor
+  Orchestrator --> PlanUpdater
   Orchestrator --> ActionPlanRunner
   Orchestrator --> ContextBuilder
   Orchestrator --> ToolRegistry

agents.md

@@ -5,7 +5,8 @@ Meeseeks is a multi-agent LLM personal assistant that decomposes user requests i
 
 ## Core entry points
 - `packages/meeseeks_core/src/meeseeks_core/task_master.py`: action planning + task execution loop
-- `packages/meeseeks_core/src/meeseeks_core/classes.py`: `ActionStep`, `TaskQueue`, `AbstractTool` contracts
+- `packages/meeseeks_core/src/meeseeks_core/classes.py`: `ActionStep` (tool_id/operation/tool_input), `TaskQueue`, `AbstractTool` contracts
+- `packages/meeseeks_core/src/meeseeks_core/planning.py`: `Planner`, `ToolSelector`, `StepExecutor`, `PlanUpdater`
 - `packages/meeseeks_core/src/meeseeks_core/session_runtime.py`: session lifecycle, listing, archiving, and async runs
 - `packages/meeseeks_core/src/meeseeks_core/session_store.py`: transcript storage, tags, and archive state
 - `packages/meeseeks_tools/src/meeseeks_tools/`: tool implementations and integration glue
@@ -32,7 +33,7 @@ When you need external context (other repos, CI failures, specs, APIs), prefer M
 ## Engineering principles (project-specific)
 - KISS and DRY: prefer small, obvious changes; remove redundancy instead of adding layers.
 - KRY: keep requirements and acceptance criteria in view; do not drift.
-- Keep tool contracts stable (`AbstractTool`, `ActionStep`, `TaskQueue`).
+- Keep tool contracts stable (`AbstractTool`, `ActionStep`, `TaskQueue`) and the tool field names (`tool_id`, `operation`, `tool_input`).
 - Favor composition and reuse across interfaces; avoid duplicating core logic.
 - Add or improve tests for non-trivial behavior; expand coverage when touching core logic or tools.
 - Use Gitmoji + Conventional Commit format (e.g., `✨ feat: add session summary pass-through`).
@@ -44,7 +45,7 @@ When you need external context (other repos, CI failures, specs, APIs), prefer M
 ## Orchestration insights (transferable)
 - Separate tool execution from user-facing response: synthesize after tool results, don't dump raw tool output.
 - Keep the loop explicit: plan -> act -> observe -> decide; re-plan only when needed.
-- Make tool inputs schema-aware; prefer structured arguments for MCP tools.
+- Make tool inputs schema-aware; prefer structured `tool_input` for MCP tools.
 - Surface tool activity clearly (permissions, tool IDs, arguments) to reduce user confusion.
 
 ## Testing patterns (what worked)
@@ -64,7 +65,7 @@ When you need external context (other repos, CI failures, specs, APIs), prefer M
 ## Linting & formatting
 - Primary linting uses `ruff` (root + subpackages). Auto-fix with `.venv/bin/ruff check --fix .`.
 - Type checking uses `mypy`. Run from repo root after installing with `uv`.
-- `flake8`, `pylint`, and `autopep8` are still available as dev tools (legacy or ad‑hoc use).
+- `flake8`, `pylint`, and `autopep8` are still available as dev tools (optional/ad‑hoc use).
 - Helper targets: `make lint`, `make lint-fix`, and `make typecheck`.
 - Pre-commit hooks are defined in `.pre-commit-config.yaml` (install with `make precommit-install`).
 

apps/meeseeks_api/AGENTS.md

@@ -9,11 +9,20 @@ Scope: this file applies to the `apps/meeseeks_api/` package. It captures runtim
   - `GET /api/sessions` list sessions
   - `POST /api/sessions/{session_id}/query` enqueue run or core command
   - `GET /api/sessions/{session_id}/events?after=...` poll events
-  - `POST /api/query` legacy synchronous endpoint
+  - `POST /api/query` synchronous endpoint (simple/CLI-compatible)
+  - `GET /api/tools` list tool registry entries
+  - `GET /api/notifications` list notifications
+  - `POST /api/notifications/dismiss` dismiss notifications
+  - `POST /api/notifications/clear` clear notifications
+  - `POST /api/sessions/{session_id}/attachments` upload attachments
+  - `POST /api/sessions/{session_id}/share` create share link
+  - `POST /api/sessions/{session_id}/export` export session payload
+  - `GET /api/share/{token}` fetch shared session data
 - Auth: requires `X-API-KEY` header. Token defaults to `api.master_token` from `configs/app.json` (default: `msk-strong-password`).
 - Orchestration: uses `meeseeks_core.session_runtime.SessionRuntime` to run sync/async sessions.
 - Core commands: `/compact`, `/status`, `/terminate` (shared runtime).
 - Sessions: supports `session_id`, `session_tag`, and `fork_from` (tag or id). Tags are resolved via `SessionStore`.
+- Event payloads: `action_plan` steps are `{title, description}`; tool events use `tool_id`, `operation`, `tool_input`.
 
 ## Hidden dependencies / assumptions
 - Uses core logging (`meeseeks_core.common.get_logger`); log level controlled by `runtime.log_level`.

apps/meeseeks_api/README.md

@@ -4,9 +4,9 @@
     <a href="https://github.com/bearlike/Assistant/releases"><img src="https://img.shields.io/github/v/release/bearlike/Assistant?style=for-the-badge&" alt="GitHub Release"></a>
 </p>
 
-- REST API Engine wrapped around the meeseeks-core.
-- No components are explicitly tested for safety or security. Use with caution in a production environment.
-- For full setup and configuration, see `docs/getting-started.md`.
+- REST API engine wrapped around meeseeks-core.
+- No components are explicitly tested for safety or security. Use with caution in production.
+- For setup and configuration, see `docs/getting-started.md`.
 
 ## Run
 ```bash
@@ -21,6 +21,14 @@ uv run meeseeks-api
 - `GET /api/sessions/{session_id}/events?after=...` poll events
 - `POST /api/sessions/{session_id}/archive` archive a session
 - `DELETE /api/sessions/{session_id}/archive` unarchive a session
-- `POST /api/query` legacy synchronous endpoint
+- `POST /api/query` synchronous endpoint (simple/CLI-compatible)
+- `GET /api/tools` list tool registry entries
+- `GET /api/notifications` list notifications
+- `POST /api/notifications/dismiss` dismiss notifications
+- `POST /api/notifications/clear` clear notifications
+- `POST /api/sessions/{session_id}/attachments` upload attachments
+- `POST /api/sessions/{session_id}/share` create share link
+- `POST /api/sessions/{session_id}/export` export session payload
+- `GET /api/share/{token}` fetch shared session data
 
 [Link to GitHub Repository](https://github.com/bearlike/Assistant)

apps/meeseeks_api/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "meeseeks-api"
-version = "2.1.0-alpha"
+version = "0.0.7"
 description = "REST API Engine wrapped around the Meeseeks core."
 readme = "../../README.md"
 requires-python = ">=3.10,<4.0"
@@ -10,8 +10,8 @@ authors = [
 license = { text = "MIT" }
 
 dependencies = [
-  "meeseeks-core>=2.1.0-alpha",
-  "meeseeks-tools>=2.1.0-alpha",
+  "meeseeks-core>=0.0.7",
+  "meeseeks-tools>=0.0.7",
   "flask>=3.0.3,<4.0.0",
   "flask-restx>=1.3.0,<2.0.0",
 ]