Skip to content

History

Revisions

  • docs: refresh integration, operations, ONNX, hooks and graph wiki guides

    Heinrich Krupp committed Nov 6, 2026
    f0fce60
  • docs: rewrite quality guide against current scoring and API behavior

    Heinrich Krupp committed Nov 6, 2026
    447469b
  • docs: restructure roadmap around current work and verified milestones

    Heinrich Krupp committed Nov 6, 2026
    1f23c72
  • docs: remove obsolete ChromaDB FAQ guidance

    Heinrich Krupp committed Nov 5, 2026
    0ed07cd
  • docs: refresh wiki for v12.6.0 and GitHub hosting

    Heinrich Krupp committed Nov 5, 2026
    365c006
  • Diagram in Mermaid

    @doobidoo doobidoo committed Oct 16, 2026
    b9f878b
  • Backend Synchronization Guide: document delta-sync / self-hosted sync hub

    @doobidoo doobidoo committed Oct 16, 2026
    0a03ec2
  • Add v11.15 to the development roadmap

    @doobidoo doobidoo committed Oct 4, 2026
    d5577f0
  • Seed Memory-Portability-Map: 5 layers x daily-run harnesses (Kiro/OpenClaw/Hermes/OpenCode)

    @filhocf filhocf committed Sep 30, 2026
    55b5797
  • Mark the triage digest as running on GitHub again The workflow from #1358 posts to the pinned issue #1359 since 2026-09-28.

    @doobidoo doobidoo committed Sep 28, 2026
    a7033e9
  • Correct the maintainer operations lines The triage digest still reads the frozen Codeberg archive and its GitHub issue #805 is closed, the quarterly CODEOWNERS routine no longer exists, and the owner list changed in #1329. Say so instead of describing the May setup as current.

    @doobidoo doobidoo committed Sep 28, 2026
    f7dbaab
  • Replace the stale Q2 focus and Q3 plan with the Q4 2026 roadmap Current Focus now lists what closed in Q3, the open bugs, and the active RFCs and discussions. The Q3 plan referenced issues that had closed months ago; it is replaced by a Q4 roadmap that names the self-hosted sync hub (#1304) as the v12.0 milestone.

    @doobidoo doobidoo committed Sep 28, 2026
    eb81414
  • Fill in v10.48 through v10.74 on the roadmap The page jumped from v10.47 straight to v11.0. Add the two May-June 2026 blocks to Phase 2 and extend its range to v10.74.

    @doobidoo doobidoo committed Sep 28, 2026
    0567150
  • Bring the roadmap up to v11.14.0 Add a Phase 3 block covering v11.0 through v11.14 (June to September 2026), set the current version to v11.14.0 and refresh the test count, repository numbers and review schedule.

    @doobidoo doobidoo committed Sep 28, 2026
    3706903
  • Clear the two remaining dead links and refresh the stale numbers on Home Both dead links predate the diagram work and were found by walking every internal link in the wiki: - Screenshot-Automation-Guide pointed at SCREENSHOT_UPLOAD_INSTRUCTIONS.md, which exists nowhere in the wiki or its archive. Dropped the entry. - 11-Agent-Integrations-Guide rendered a broken "[CHANGELOG](link)" inside an example of a bot comment. It was placeholder prose, so it is plain text now. Home also still advertised v11.7.0 and ~2,780 tests. Now v11.10.0 and ~3,000, counted rather than guessed: pytest --collect-only reports 3007. The ASCII architecture box keeps its column width. The 28 MCP tools figure was checked against the registry and still holds. Every internal wiki link now resolves.

    @doobidoo doobidoo committed Aug 28, 2026
    e1ee07b
  • Give both diagram pages English names and content, and clear the number collisions The wiki numbering had two pages on 14 and two on 15. Both collisions are gone: the page with fewer inbound links moved in each pair, so the heavily linked Quality System and ONNX guides keep their URLs. - 15-Archify-Diagramm -> 22-Architecture-Diagram (translated) - 21-Deployment-Landschaft -> 21-Deployment-Landscape (translated, number kept) - 14-Contributor-Promotion -> 23-Contributor-Promotion (rename only) The architecture page now says what the diagram actually shows: the service as embedded in a local Hermes agent, one example rather than a canonical deployment. Seven inbound links updated across Home.md and the roadmap. Also fixes a dead nav link in Home.md that pointed at Windows-Hybrid-Backend-Setup instead of Windows-Hybrid-Setup.

    @doobidoo doobidoo committed Aug 28, 2026
    a8c3736
  • Point the diagram pages at mcpmemory.services and add the deployment landscape The iframe on the Archify page never rendered: the wiki serves neither iframes nor raw HTML. Both diagrams now live on Cloudflare Pages, deployed with the rest of site/, so the wiki pages link out instead of embedding. Adds the deployment landscape page: which forge builds, which mirrors pull, and which registries get published to — including the fact that the Forgejo runner and the Gitea mirror share one Hetzner VM. Numbered 21 rather than 16, because 14, 15 and 16 already carry two pages each.

    @doobidoo doobidoo committed Aug 27, 2026
    0aa8b5b
  • Update: Add <iframe> embed for Archify diagram in Wiki page - Replace raw download link with inline iframe - Restructure page with features list and alternative live link - Note: GitHub Wikis block <iframe> - only for reference

    @doobidoo doobidoo committed Aug 26, 2026
    deb15bd
  • Add: Archify architecture diagram for MCP Memory Service (#15) - Interactive HTML diagram generated with Archify v2.16 - Documentation page with overview, component table, and guided views - Self-contained 706 KB HTML asset for offline viewing

    @doobidoo doobidoo committed Aug 26, 2026
    3614ce3
  • Drop a personal store size from the scan-limit note The page illustrated MCP_MAINTAIN_SCAN_LIMIT with "on a 17,000-memory store, a default run covers roughly the first eighth". That number described one particular store, not anything about the software, so it read like a benchmark it never was — and it was wrong twice over: it came from _count_existing_memory_rows(), a hash-embedding guard heuristic that sums the memories and memory_embeddings tables, so it double-counted. What matters is the rule, which holds at any size: the limit takes the first N in storage order, so repeated runs re-scan the same N and never reach the rest.

    Henry Krupp committed Aug 9, 2026
    0ffc57e
  • docs(troubleshooting): add stale-Cloudflare stdio timeout case stdio memory server (hybrid backend) hangs every tools/call after days uptime due to a stale Cloudflare HTTPS socket; list_tools stays responsive. Distinct from the missing-sync-owner case — fix is a gateway restart, not a config change. Adds diagnosis (ps/lsof/etime) and launchctl kickstart fix, plus ToC entry. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    @doobidoo doobidoo committed Aug 8, 2026
    9acdcc8
  • docs(wiki): migrate retrieve_memory automation examples to memory_search (pre-V11) The three "action": "retrieve_memory" entries name the MCP tool directly, which is removed in V11. memory_search is the current registry name and resolves today, so this is correct now and future-proof. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    @doobidoo doobidoo committed Aug 8, 2026
    e7761ab
  • docs(home): add Heavybit interview + Michał Zubkowicz testimonial Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    @doobidoo doobidoo committed Aug 8, 2026
    4731534
  • Add token-efficient retrieval guide; correct stale facts on Home memory_explore and memory_detail shipped in v11.1.0 with no user-facing documentation anywhere, which is how a user with 11k memories came to file a feature request for most of what they already do (#215). New page walks from the symptom — search responses eating 10k tokens — through limit and max_response_chars, then the two-phase map for people who want an overview before pulling content. It leads with the prerequisite, because memory_explore returns count=0 for every query until the entity graph is populated and nothing populates it by default. Also documents the two traps that cost real time: maintain's dry_run defaults to true and stores nothing, and MCP_MAINTAIN_SCAN_LIMIT defaults to 2000 taking the first N in storage order, so repeated runs never reach the tail of a larger store. Home had drifted badly: it advertised v10.65.1 and ~1,828 tests, claimed MIT when the project is Apache-2.0, said 12 MCP tools where the registry now has 28, and every repository link pointed at github.com — which sends readers to the suspended mirror rather than Codeberg. Codeberg has no Discussions feature, so the "Question?" link now points at issues instead of a page that does not exist. The What's New section still stops at v10.65.1 and is left for the release workflow to bring forward.

    Henry Krupp committed Aug 8, 2026
    d265451
  • docs(troubleshooting): add port-conflict causes wrong backend incident (v11)

    @hekr4jivs hekr4jivs committed Jun 14, 2026
    43b24c5
  • docs(wiki): overhaul Home.md — v10.65.1, remove stale v7.x content, modern structure

    Heinrich Krupp committed May 24, 2026
    1681ee2
  • merge(wiki): consolidate Cloudflare cluster (#833 draft) Three-way Cloudflare/Hybrid guide cluster identified by housekeeping audit 2026-05-02 (F-033). Resolution favors lightweight reframing over heavy content merge — the three guides cover distinct topologies but the deprecated multi-machine framing is now redundant since hybrid mode handles multi-machine sync natively. ### Removed - Cloudflare-Based-Multi-Machine-Sync.md (507 lines) - Pre-hybrid (v6.13.7) framing of multi-machine sync as a separate architecture is now obsolete — hybrid backend IS the multi-machine sync solution - Architecture diagram useful but redundant with Hybrid_Setup_Configuration - Migration script superseded by built-in memory_ingest tooling ### Updated - Cloudflare-Backup-Sync-Setup.md - Added a top-of-page guidance block: "Most users want Hybrid_Setup_Configuration, not this guide" - Lists the legitimate remaining use cases (DR-only export, custom one-way sync, resource-provisioning reference) - Steps 1–2 (Cloudflare resource creation + token) remain canonical even when configuring hybrid - Hybrid_Setup_Configuration.md - Removed stale "Version 8.9.0" header (current is v10.48.0; version callouts inline still note v8.9.0+ for specific features) - Added explicit "Multi-Machine: ✅ canonical solution" callout in the metadata block - Cross-link to Cloudflare-Backup-Sync-Setup steps 1–2 for resource provisioning instead of duplicating those steps - Home.md - Dropped the Multi-Machine-Sync link from the Setup & Configuration section ### Net change ~520 lines removed, 2 cross-links added, 1 deprecation guidance block added. No content lost — anything load-bearing in Multi-Machine-Sync was already covered in Hybrid_Setup_Configuration. This commit is on branch merge/cloudflare-cluster-833 — review before merging to master.

    Heinrich Krupp committed May 2, 2026
    3c1f6e3
  • merge(wiki): consolidate Windows guides into Windows-Hybrid-Setup (#834 draft) Replaces two outdated, near-duplicate personal status logs with a single generic, version-agnostic Windows hybrid setup guide. Removed: - Windows-Setup-Summary-Example.md (211 lines) — Oct 2025, v8.3.0, hardcoded username 'heinrich.krupp' and personal paths - Windows-Hybrid-Backend-Setup-Example.md (209 lines) — same date, same version, same personal data, same general scope, slightly different emphasis (config-focused vs status-focused) Added: - Windows-Hybrid-Setup.md — generic guide with <USERNAME>/<REPO_PATH> placeholders, recommended MCP_HYBRID_SYNC_OWNER=http separation (sqlite_vec for MCP server, hybrid for HTTP server), WAL pragma guidance for concurrent access, current troubleshooting (Cloudflare 401, port conflicts), and explicit cross-links to: - Hybrid_Setup_Configuration (architecture) - Cloudflare-Backup-Sync-Setup (provisioning) - 02-Platform-Setup-Guide (broader Windows notes) Both removed files were flagged in housekeeping audit 2026-05-02 (F-034, issue #834) as a near-duplicate cluster of personal logs that should be generalized for the wiki audience. This commit is on branch merge/windows-cluster-834 — review before merging to master.

    Heinrich Krupp committed May 2, 2026
    2857e04
  • fix(wiki): redirect macOS Intel link to existing Platform Setup section (F-025, closes #825) F-025: link './macOS-Intel-Legacy-Guide' pointed to non-existent page. Redirected to '02-Platform-Setup-Guide#intel-macs-2015-2020---legacy-hardware-setup' which contains the actual Intel Mac legacy hardware guidance. F-026 (Tag-System-Migration-and-Management) was already redirected to 04-Advanced-Configuration in the prior housekeeping pass — no change needed, 04-Advanced-Configuration has Tagging Strategy coverage.

    Heinrich Krupp committed May 2, 2026
    80bdc17
  • fix(wiki): repair broken TOC anchors (F-028, F-029, closes #824) F-028 (06-Development-Reference.md:10): TOC link #debugging--testing pointed to a heading renamed to 'Debugging & Troubleshooting'. F-029 (05-Performance-Optimization.md:8): TOC link contained U+FE0F variation selector after '#'. GitHub Wiki strips variation selectors when generating anchors, so the link did not resolve.

    Heinrich Krupp committed May 2, 2026
    387db7f