Lyellr88/marm-memory

Problem Once marm-init is installed, the Connections card hides Install skill and only shows an installed pill. Users cannot refresh the bundled skill after an upgrade or remove it from the card, even though the installer already supports refreshing an existing installation. Requested behavior Replace Install skill with Manage skill when installed. Open a small dialog offering: Update: reinstall the current bundled skill using the existing installer. Delete: remove only this agent's installed marm-init folder. Close: make no change. Delete requires a second confirmation showing the exact folder. Use the same client-specific directory resolution as install, including supported overrides such as HERMES_HOME. Do not remove sibling skills or other agent files, and refuse symlinked paths that could redirect deletion outside the intended folder. Add the deletion route beside the existing skill-install route in console/endpoints/agents.py, with the same loopback-only mutation guard. Fronten

Context: PR #203 proposed an engine_binary object in marm_graph_index's auto_status response. PR #204 is the stronger implementation for closed GH #201 because it validates the selected launcher as an executable regular file and shares that check with the graph backend. The structured status idea should not be lost, but it must be built on #204's resolver rather than PR #203's Path.exists() check. Potential fields: availability, launcher source (CBM_BINARY_PATH, CBM_COMMAND, or pip-managed), configured or resolved path, and an actionable unavailable reason such as missing, invalid, or non-executable. Why it helps: The Console System/Health surface could explain why graph auto-indexing is dormant without asking users to inspect server logs. It is observability only, not required to activate Docker auto-indexing. Status: Open follow-up; PR #204 has landed. Current auto-status reports engine_binary_present, and PR #255 adds outcome/hint logging, but neither delivers the proposed structure

Problem Code Explorer cannot expand valid filenames containing apostrophes, ampersands, commas, or non-ASCII characters. These files can be indexed, but the Console and graph adapter reject their paths when requesting details. Affected boundaries: marm_mcp_server/console/endpoints/projects.py: file-path request validation. marm_graph/core/code_graph_view.py: _FILE_PATH_RE validation and fixed query templates. Prerequisite Before changing the allowlist, verify how the pinned codebase-memory-mcp engine supports query parameters or escaped string literals. MARM currently pins version 0.10.5. The planned upgrade evaluation is documented in docs/current/current-issues/codebase-memory-mcp-v0.11-upgrade.md, but safe filename handling still needs explicit investigation. Please comment before starting. Contract investigation is welcome; do not widen the regex without proving the resulting queries remain safe. Acceptance criteria Verify and document the engine's parameter-binding or literal-

Goal Finish the remaining Docker runtime coverage from #170. The PR CI gap is fixed, and several container regressions now have real tests. This issue tracks what is left, not new runtime features. Completed Docker images build and container tests run in PR CI: #183. Healthchecks can report unhealthy: #185. Exposed-network mode enforces authentication: #192. A mounted Git repository is indexed and refreshed by the code worker: #204. Foreign-owned mounts refuse unsafe key persistence while supplied keys remain usable: #206. This is credential protection, not full UID-mapping coverage. Code indexes persist across recreated registry-launched containers: #257. Remaining coverage Start with the background and shared-storage paths: Concept-worker processing in a real container, including both HTTP and STDIO startup paths. Queued memory writes persist correctly and drain during shutdown. A host process and a container sharing the same database contend safely on the concept-build and cod

Summary We are looking for a contributor to record and edit a short, professional MARM Console demo video. The contributor should capture the footage from the supplied demo environment, then deliver the completed edit and editable project files. MARM Console is the local web interface for memory retrieval, knowledge-graph exploration, repository indexing, code-graph workflows, and local runtime controls. Demo pack The repository will include a self-contained demo pack at marm-console/assets/demo-pack/. It avoids personal data and private source code while giving the Console meaningful content to show. It includes: Eight fictional release-readiness memories in the console-demo session A small fictional signalboard-demo Python project with an intentional import graph A local-only seed script that imports the memories into the running MARM runtime A timed recording plan, asset manifest, and source-safe recording guidance Quick start: pip install marm-mcp-server marm-memory fast-start-ht