MetaList 0.3.11__tar.gz → 0.3.13__tar.gz

{metalist-0.3.11/metalist.egg-info → metalist-0.3.13}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: metalist
-Version: 0.3.11
+Version: 0.3.13
 Summary: A minimalist single-user note-taking app with SSR, fast in-memory tree operations, and efficient sync.
 Project-URL: Homepage, https://github.com/evolvingstuff/metalist
 Project-URL: Repository, https://github.com/evolvingstuff/metalist
@@ -10,18 +10,23 @@ Description-Content-Type: text/markdown
 Requires-Dist: argon2-cffi==25.1.0
 Requires-Dist: cryptography==50.0.0
 Requires-Dist: fastapi==0.141.1
+Requires-Dist: httpcore==1.0.9
 Requires-Dist: httpx==0.28.1
 Requires-Dist: latex2mathml==3.81.0
 Requires-Dist: loguru==0.7.3
 Requires-Dist: Mako==1.3.12
 Requires-Dist: mutagen==1.48.1
+Requires-Dist: nh3==0.3.6
+Requires-Dist: pillow==12.3.0
 Requires-Dist: pydantic==2.13.4
+Requires-Dist: python-dotenv==1.2.2
 Requires-Dist: python-multipart==0.0.32
 Requires-Dist: starlette==1.3.1
 Requires-Dist: tqdm==4.70.0
 Requires-Dist: tree-sitter==0.25.2
 Requires-Dist: tree-sitter-javascript==0.25.0
 Requires-Dist: uvicorn==0.52.0
+Requires-Dist: zxcvbn==4.5.0
 Provides-Extra: dev
 Requires-Dist: hypothesis==6.164.0; extra == "dev"
 Requires-Dist: pytest==9.1.1; extra == "dev"
@@ -80,7 +85,7 @@ After the first installation, update and restart MetaList with one cross-platfor
 ```bash
 metalist update
 ```
-The updater stops running namespaces, hands off to an external PowerShell process on Windows or `/bin/sh` on macOS/Linux so the installed environment can unlock, runs the forced cache-refreshed uv update, and launches MetaList again.
+The updater checks the installed version against the latest PyPI release first. If MetaList is already current, it reports the installed version and leaves all running namespaces untouched. When an update is available, it stops running namespaces, hands off to an external PowerShell process on Windows or `/bin/sh` on macOS/Linux so the installed environment can unlock, installs the exact version reported by PyPI with a forced cache refresh, launches MetaList again, and reports the installed version (for example, `MetaList updated to v0.3.13.`).
 
 For pip, users can run `pip install metalist`. For a non-editable local install from this checkout, use `uv pip install .` or `pip install .` instead of the editable command below.
 
@@ -99,8 +104,22 @@ metalist
 ```
 For source-checkout compatibility, `python main.py` performs the same orchestration. Use `metalist work`, `python main.py --namespace work`, or `python main.py work` when you want one foreground namespace process.
 
-`metalist` and explicit single-namespace source runs bind HTTP on `0.0.0.0:8000` by default, matching the old MetaList LAN-friendly behavior.
-On first startup, MetaList also auto-generates a self-signed TLS pair at `~/MetaList/certs/metalist-cert.pem` and `~/MetaList/certs/metalist-key.pem`, then enables HTTPS on `0.0.0.0:8443`. If you already have real PEM files, point `METALIST_TLS_CERT` and `METALIST_TLS_KEY` at them instead. Set `METALIST_AUTO_GENERATE_TLS=0` only if you explicitly want HTTP-only startup.
+Shell execution is disabled by default. To enable `@shell` for every namespace
+started by the top-level orchestrator, use either:
+
+```bash
+metalist --enable-shell
+python main.py --enable-shell
+```
+
+This flag is propagated to every namespace child process. The top-level process
+prints a conspicuous shell-enabled banner before its namespace launch results.
+Use `python main.py work --enable-shell` for one foreground namespace. Shell
+routes remain restricted to loopback clients using a loopback request host,
+even when the rest of MetaList is intentionally exposed to a LAN.
+
+`metalist` and explicit single-namespace source runs bind to loopback at `127.0.0.1:8000` by default. This keeps a normal laptop launch off LAN and public interfaces unless remote access is explicitly configured.
+On first startup, MetaList also auto-generates a self-signed TLS pair at `~/MetaList/certs/metalist-cert.pem` and `~/MetaList/certs/metalist-key.pem`, then enables HTTPS on the same bind host at port `8443`. If you already have real PEM files, point `METALIST_TLS_CERT` and `METALIST_TLS_KEY` at them instead. Set `METALIST_AUTO_GENERATE_TLS=0` only if you explicitly want HTTP-only startup.
 
 Database selection:
 - No explicit namespace on a single-namespace launch: `~/MetaList/namespaces/default/default.metalist.db`
@@ -116,20 +135,36 @@ Useful env flags:
 - `CRASH_SERVER_ON_FAIL=1` (default): fail-fast on validation errors
 - `API_PREFIX=/api2`: override API prefix (client assumes `/api2` by default)
 - `METALIST_NAMESPACE=work`: select `~/MetaList/namespaces/work/work.metalist.db`
-- `METALIST_HOST=0.0.0.0` (default): bind the main app to a different interface such as `127.0.0.1`
+- `METALIST_HOST=127.0.0.1` (default): bind the main app to a specific interface; use a LAN IP or `0.0.0.0` only for intentional remote access
+- `METALIST_ALLOWED_HOSTS=notes.example.com,192.168.1.20`: comma-separated public/LAN hostnames accepted in HTTP `Host` headers; loopback aliases and a specific non-wildcard `METALIST_HOST` are accepted automatically
 - `METALIST_PORT=8000` (default): bind the main app to a different port
 - `METALIST_HTTPS_PORT=8443`: override the HTTPS port when TLS is enabled
 - `METALIST_TLS_CERT=/path/to/fullchain.pem` + `METALIST_TLS_KEY=/path/to/privkey.pem`: override TLS paths
 - `METALIST_AUTO_GENERATE_TLS=0`: disable automatic creation of the default self-signed TLS pair
 - default TLS paths: `~/MetaList/certs/metalist-cert.pem` and `~/MetaList/certs/metalist-key.pem`
 - `METALIST_FORWARDED_ALLOW_IPS=127.0.0.1,::1` (default): trust proxy headers only from those reverse-proxy IPs
+- `--enable-shell`: opt in to local `@shell` execution for this launch; shell routes require a loopback client and loopback request host, and the capability is never persisted in namespace data
 
 ### Remote Access / HTTPS
-Plain LAN or VPN HTTP works with a normal PyCharm run:
+LAN or VPN access must be enabled explicitly. Prefer binding the machine's specific LAN address, which also adds that address to the accepted-host set:
 ```bash
-metalist
+METALIST_HOST=192.168.1.20 metalist
 ```
-On a fresh machine, that first launch also creates the default TLS cert pair automatically. Then open either `http://<laptop-ip>:8000` or `https://<laptop-ip>:8443` from the other machine.
+On a fresh machine, that first launch also creates the default TLS cert pair automatically. Then open either `http://192.168.1.20:8000` or `https://192.168.1.20:8443` from the other machine.
+
+To keep `@shell` available on the host laptop while allowing another laptop to
+use normal MetaList features, bind both interfaces and explicitly allow the LAN
+address:
+
+```bash
+METALIST_HOST=0.0.0.0 \
+METALIST_ALLOWED_HOSTS=10.0.0.31 \
+metalist --enable-shell
+```
+
+Use `http://127.0.0.1:<namespace-http-port>` on the host laptop when running
+`@shell`. Other devices may use `https://10.0.0.31:<namespace-https-port>`, but
+their shell start/status requests receive `403`.
 
 Namespaced launch example:
 ```bash
@@ -147,6 +182,7 @@ and MetaList will reuse the saved HTTP / HTTPS ports for `work`. The same applie
 Equivalent explicit launch, if you want it:
 ```bash
 METALIST_HOST=0.0.0.0 \
+METALIST_ALLOWED_HOSTS=192.168.1.20 \
 METALIST_PORT=8000 \
 METALIST_HTTPS_PORT=8443 \
 metalist
@@ -156,6 +192,7 @@ From the other machine, open `https://<laptop-ip>:8443`.
 If you already have a real certificate and key, use the same dual-listener flow:
 ```bash
 METALIST_HOST=0.0.0.0 \
+METALIST_ALLOWED_HOSTS=192.168.1.20 \
 METALIST_PORT=8000 \
 METALIST_HTTPS_PORT=8443 \
 METALIST_TLS_CERT=/path/to/fullchain.pem \
@@ -175,11 +212,17 @@ When HTTPS is enabled:
 If TLS is terminated by a reverse proxy on the same machine instead, keep MetaList on loopback and let the proxy forward to it:
 ```bash
 METALIST_HOST=127.0.0.1 \
+METALIST_ALLOWED_HOSTS=notes.example.com \
 METALIST_PORT=8000 \
 METALIST_FORWARDED_ALLOW_IPS=127.0.0.1,::1 \
 metalist
 ```
 
+The reverse proxy must preserve the browser-facing `Host` header and set
+`X-Forwarded-Proto`. MetaList never trusts `X-Forwarded-Host`; forwarded
+scheme/client metadata is accepted only from `METALIST_FORWARDED_ALLOW_IPS`.
+Do not widen that list beyond the actual proxy addresses.
+
 ### Legacy Import
 `convert-from-legacy.py` replaces the SQLite database referenced by `app.config.DATABASE_URL`, clears its files/sounds sidecar, and imports notes from a legacy JSON export.
 
@@ -226,6 +269,18 @@ node --test tests/unit/*.mjs
 .venv/bin/python -c "from pathlib import Path; import main; main._run_startup_sanity_gates(repo_root=Path.cwd())"
 ```
 
+Source-checkout development launches can enable the mandatory Python and
+JavaScript sanity gates with an ignored repository-root `.env` file:
+
+```dotenv
+METALIST_ENVIRONMENT=development
+```
+
+`main.py` prints the resolved environment at startup. An explicit process
+environment value takes precedence over `.env`; only `development` and
+`production` are accepted. When the variable and `.env` file are absent,
+MetaList runs in production mode and skips the source sanity gates.
+
 `TEST_MODE=1` and `POST /api2/test/reset` still exist for deterministic browser automation if we decide to add a new harness later, but Cypress is not part of the current workflow.
 
 ### Diagrams

{metalist-0.3.11 → metalist-0.3.13}/README.md

@@ -51,7 +51,7 @@ After the first installation, update and restart MetaList with one cross-platfor
 ```bash
 metalist update
 ```
-The updater stops running namespaces, hands off to an external PowerShell process on Windows or `/bin/sh` on macOS/Linux so the installed environment can unlock, runs the forced cache-refreshed uv update, and launches MetaList again.
+The updater checks the installed version against the latest PyPI release first. If MetaList is already current, it reports the installed version and leaves all running namespaces untouched. When an update is available, it stops running namespaces, hands off to an external PowerShell process on Windows or `/bin/sh` on macOS/Linux so the installed environment can unlock, installs the exact version reported by PyPI with a forced cache refresh, launches MetaList again, and reports the installed version (for example, `MetaList updated to v0.3.13.`).
 
 For pip, users can run `pip install metalist`. For a non-editable local install from this checkout, use `uv pip install .` or `pip install .` instead of the editable command below.
 
@@ -70,8 +70,22 @@ metalist
 ```
 For source-checkout compatibility, `python main.py` performs the same orchestration. Use `metalist work`, `python main.py --namespace work`, or `python main.py work` when you want one foreground namespace process.
 
-`metalist` and explicit single-namespace source runs bind HTTP on `0.0.0.0:8000` by default, matching the old MetaList LAN-friendly behavior.
-On first startup, MetaList also auto-generates a self-signed TLS pair at `~/MetaList/certs/metalist-cert.pem` and `~/MetaList/certs/metalist-key.pem`, then enables HTTPS on `0.0.0.0:8443`. If you already have real PEM files, point `METALIST_TLS_CERT` and `METALIST_TLS_KEY` at them instead. Set `METALIST_AUTO_GENERATE_TLS=0` only if you explicitly want HTTP-only startup.
+Shell execution is disabled by default. To enable `@shell` for every namespace
+started by the top-level orchestrator, use either:
+
+```bash
+metalist --enable-shell
+python main.py --enable-shell
+```
+
+This flag is propagated to every namespace child process. The top-level process
+prints a conspicuous shell-enabled banner before its namespace launch results.
+Use `python main.py work --enable-shell` for one foreground namespace. Shell
+routes remain restricted to loopback clients using a loopback request host,
+even when the rest of MetaList is intentionally exposed to a LAN.
+
+`metalist` and explicit single-namespace source runs bind to loopback at `127.0.0.1:8000` by default. This keeps a normal laptop launch off LAN and public interfaces unless remote access is explicitly configured.
+On first startup, MetaList also auto-generates a self-signed TLS pair at `~/MetaList/certs/metalist-cert.pem` and `~/MetaList/certs/metalist-key.pem`, then enables HTTPS on the same bind host at port `8443`. If you already have real PEM files, point `METALIST_TLS_CERT` and `METALIST_TLS_KEY` at them instead. Set `METALIST_AUTO_GENERATE_TLS=0` only if you explicitly want HTTP-only startup.
 
 Database selection:
 - No explicit namespace on a single-namespace launch: `~/MetaList/namespaces/default/default.metalist.db`
@@ -87,20 +101,36 @@ Useful env flags:
 - `CRASH_SERVER_ON_FAIL=1` (default): fail-fast on validation errors
 - `API_PREFIX=/api2`: override API prefix (client assumes `/api2` by default)
 - `METALIST_NAMESPACE=work`: select `~/MetaList/namespaces/work/work.metalist.db`
-- `METALIST_HOST=0.0.0.0` (default): bind the main app to a different interface such as `127.0.0.1`
+- `METALIST_HOST=127.0.0.1` (default): bind the main app to a specific interface; use a LAN IP or `0.0.0.0` only for intentional remote access
+- `METALIST_ALLOWED_HOSTS=notes.example.com,192.168.1.20`: comma-separated public/LAN hostnames accepted in HTTP `Host` headers; loopback aliases and a specific non-wildcard `METALIST_HOST` are accepted automatically
 - `METALIST_PORT=8000` (default): bind the main app to a different port
 - `METALIST_HTTPS_PORT=8443`: override the HTTPS port when TLS is enabled
 - `METALIST_TLS_CERT=/path/to/fullchain.pem` + `METALIST_TLS_KEY=/path/to/privkey.pem`: override TLS paths
 - `METALIST_AUTO_GENERATE_TLS=0`: disable automatic creation of the default self-signed TLS pair
 - default TLS paths: `~/MetaList/certs/metalist-cert.pem` and `~/MetaList/certs/metalist-key.pem`
 - `METALIST_FORWARDED_ALLOW_IPS=127.0.0.1,::1` (default): trust proxy headers only from those reverse-proxy IPs
+- `--enable-shell`: opt in to local `@shell` execution for this launch; shell routes require a loopback client and loopback request host, and the capability is never persisted in namespace data
 
 ### Remote Access / HTTPS
-Plain LAN or VPN HTTP works with a normal PyCharm run:
+LAN or VPN access must be enabled explicitly. Prefer binding the machine's specific LAN address, which also adds that address to the accepted-host set:
 ```bash
-metalist
+METALIST_HOST=192.168.1.20 metalist
 ```
-On a fresh machine, that first launch also creates the default TLS cert pair automatically. Then open either `http://<laptop-ip>:8000` or `https://<laptop-ip>:8443` from the other machine.
+On a fresh machine, that first launch also creates the default TLS cert pair automatically. Then open either `http://192.168.1.20:8000` or `https://192.168.1.20:8443` from the other machine.
+
+To keep `@shell` available on the host laptop while allowing another laptop to
+use normal MetaList features, bind both interfaces and explicitly allow the LAN
+address:
+
+```bash
+METALIST_HOST=0.0.0.0 \
+METALIST_ALLOWED_HOSTS=10.0.0.31 \
+metalist --enable-shell
+```
+
+Use `http://127.0.0.1:<namespace-http-port>` on the host laptop when running
+`@shell`. Other devices may use `https://10.0.0.31:<namespace-https-port>`, but
+their shell start/status requests receive `403`.
 
 Namespaced launch example:
 ```bash
@@ -118,6 +148,7 @@ and MetaList will reuse the saved HTTP / HTTPS ports for `work`. The same applie
 Equivalent explicit launch, if you want it:
 ```bash
 METALIST_HOST=0.0.0.0 \
+METALIST_ALLOWED_HOSTS=192.168.1.20 \
 METALIST_PORT=8000 \
 METALIST_HTTPS_PORT=8443 \
 metalist
@@ -127,6 +158,7 @@ From the other machine, open `https://<laptop-ip>:8443`.
 If you already have a real certificate and key, use the same dual-listener flow:
 ```bash
 METALIST_HOST=0.0.0.0 \
+METALIST_ALLOWED_HOSTS=192.168.1.20 \
 METALIST_PORT=8000 \
 METALIST_HTTPS_PORT=8443 \
 METALIST_TLS_CERT=/path/to/fullchain.pem \
@@ -146,11 +178,17 @@ When HTTPS is enabled:
 If TLS is terminated by a reverse proxy on the same machine instead, keep MetaList on loopback and let the proxy forward to it:
 ```bash
 METALIST_HOST=127.0.0.1 \
+METALIST_ALLOWED_HOSTS=notes.example.com \
 METALIST_PORT=8000 \
 METALIST_FORWARDED_ALLOW_IPS=127.0.0.1,::1 \
 metalist
 ```
 
+The reverse proxy must preserve the browser-facing `Host` header and set
+`X-Forwarded-Proto`. MetaList never trusts `X-Forwarded-Host`; forwarded
+scheme/client metadata is accepted only from `METALIST_FORWARDED_ALLOW_IPS`.
+Do not widen that list beyond the actual proxy addresses.
+
 ### Legacy Import
 `convert-from-legacy.py` replaces the SQLite database referenced by `app.config.DATABASE_URL`, clears its files/sounds sidecar, and imports notes from a legacy JSON export.
 
@@ -197,6 +235,18 @@ node --test tests/unit/*.mjs
 .venv/bin/python -c "from pathlib import Path; import main; main._run_startup_sanity_gates(repo_root=Path.cwd())"
 ```
 
+Source-checkout development launches can enable the mandatory Python and
+JavaScript sanity gates with an ignored repository-root `.env` file:
+
+```dotenv
+METALIST_ENVIRONMENT=development
+```
+
+`main.py` prints the resolved environment at startup. An explicit process
+environment value takes precedence over `.env`; only `development` and
+`production` are accepted. When the variable and `.env` file are absent,
+MetaList runs in production mode and skips the source sanity gates.
+
 `TEST_MODE=1` and `POST /api2/test/reset` still exist for deterministic browser automation if we decide to add a new harness later, but Cypress is not part of the current workflow.
 
 ### Diagrams

{metalist-0.3.11 → metalist-0.3.13}/app/api/middleware/auth.py

@@ -7,30 +7,34 @@ from app.api.request_auth import read_request_auth_token
 from app.services.tokens import token_service
 from app.services.auth_service import AuthService
 from app.services.maintenance_mode import maintenance_service
-from app.services.runtime_lock import purge_decrypted_runtime_state
 from app.models.database import SafeSession
 from app.config import API_PREFIX, TEST_MODE
 
 
 class AuthMiddleware(BaseHTTPMiddleware):
     """Middleware to check authentication on protected routes."""
-    
-    # Paths that don't require authentication
-    PUBLIC_PATHS = [
+
+    PUBLIC_EXACT_PATHS = frozenset({
+        "/",
         f"{API_PREFIX}/auth/login",
+        f"{API_PREFIX}/auth/login-namespaces",
+        f"{API_PREFIX}/auth/login-namespaces/open",
         f"{API_PREFIX}/auth/status",
         f"{API_PREFIX}/auth/session",
-        f"{API_PREFIX}/auth/namespaces/delete-jobs/",
-        f"{API_PREFIX}/auth/namespaces/rename-jobs/",
-        "/namespace-deleted",
-        "/namespace-renamed",
-        "/static/",  # CSS/JS files needed for login page
         "/favicon.ico",
         "/locked",
-    ]
+        "/namespace-deleted",
+        "/namespace-deleted/open",
+        "/namespace-renamed",
+        "/namespace-renamed/open",
+    } | ({f"{API_PREFIX}/test/reset"} if TEST_MODE else set()))
 
-    if TEST_MODE:
-        PUBLIC_PATHS.append(f"{API_PREFIX}/test/reset")
+    PUBLIC_PREFIX_PATHS = (
+        f"{API_PREFIX}/auth/namespaces/delete-jobs/",
+        f"{API_PREFIX}/auth/namespaces/rename-jobs/",
+        "/static/",  # CSS/JS files needed for login page
+    )
+    assert all(path.endswith("/") for path in PUBLIC_PREFIX_PATHS)
     
     # Paths to suppress verbose logging for (frequent polling endpoints)
     QUIET_PATHS = [
@@ -44,14 +48,19 @@ class AuthMiddleware(BaseHTTPMiddleware):
     ]
     
     # Note: /api/notes/* paths are NOT in this list - they require auth when password is set
+
+    @classmethod
+    def is_public_path(cls, *, path: str) -> bool:
+        if not isinstance(path, str) or not path.startswith("/"):
+            raise TypeError("path must be an absolute URL path")
+        if path in cls.PUBLIC_EXACT_PATHS:
+            return True
+        return any(path.startswith(prefix) for prefix in cls.PUBLIC_PREFIX_PATHS)
     
     async def dispatch(self, request: Request, call_next):
         """Check authentication for protected routes."""
         path = request.url.path
 
-        if not token_service.has_active_tokens():
-            purge_decrypted_runtime_state()
-
         # Block any v1 API usage with an explicit 410 Gone (no DB access)
         if path.startswith('/api') and not (path.startswith(API_PREFIX) or path == API_PREFIX):
             ref = request.headers.get('referer', '-')
@@ -74,22 +83,9 @@ class AuthMiddleware(BaseHTTPMiddleware):
         if not is_quiet:
             print(f"Middleware checking path: {path}")
         
-        # Skip authentication for public paths
-        public_match = None
-        
-        # Handle exact root path match
-        if path == "/":
-            public_match = "/ (root)"
-        else:
-            # Check other public paths with startswith
-            for public in self.PUBLIC_PATHS:
-                if path.startswith(public):
-                    public_match = public
-                    break
-                
-        if public_match:
+        if self.is_public_path(path=path):
             if not is_quiet:
-                print(f"Path {path} is public (matched '{public_match}'), skipping auth")
+                print(f"Path {path} is explicitly public, skipping auth")
             return await call_next(request)
         
         if not is_quiet:

{metalist-0.3.11 → metalist-0.3.13}/app/api/request_auth.py

@@ -2,8 +2,19 @@ from __future__ import annotations
 
 from fastapi import HTTPException, Request, Response
 
+from app.config import ACTIVE_NAMESPACE
+from app.server_runtime import validate_namespace
 
-AUTH_COOKIE_NAME = "metalist_auth"
+
+AUTH_COOKIE_PREFIX = "metalist_auth"
+
+
+def auth_cookie_name_for_namespace(namespace: str) -> str:
+    normalized_namespace = validate_namespace(namespace=namespace)
+    return f"{AUTH_COOKIE_PREFIX}_{normalized_namespace}"
+
+
+AUTH_COOKIE_NAME = auth_cookie_name_for_namespace(ACTIVE_NAMESPACE)
 
 
 def read_request_auth_token(request: Request) -> tuple[str | None, str | None]: