DEV Community

Meronq
Meronq

Posted on • Originally published at meronq.pages.dev

Sprint 2 closed: Local Project Intelligence

#devtools #ai #opensource #engineering

Sprint 2 is closed.

The goal was to build the first local prototype that can read a project and produce structured project understanding. The scanner package, CLI commands, and an upgraded handshake now turn repository layout into a ProjectIndex and a CEM snapshot — not just directory names.

What Sprint 2 delivered

Every item on the roadmap is checked off:

  • Project indexing model — ProjectIndex in packages/scanner
  • CLI prototype — meronq scan and meronq info (apps/cli)
  • Repository scanning — apps, packages, docs flags, ADRs, blog posts
  • Package manager detection — pnpm, npm, yarn
  • Structure summary — human-readable one-liner per project
  • Local notes — scan output saved to .meronq/local/project-index.json

Local MCP is now v1.11.0 with project_scan and project_index in handshake.

New package: @meronq/scanner

Module Role
scanProject() Walk repo → ProjectIndex
indexToCemSnapshot() ProjectIndex + git log → CEM
saveProjectIndex() / loadProjectIndex() Persist under .meronq/local/

Example summary:

meronq: pnpm monorepo=true · 4 app(s), 2 package(s) · 8 ADR(s), 3 blog post(s)
Enter fullscreen mode Exit fullscreen mode

CLI 

meronq scan    # write .meronq/local/project-index.json
meronq info    # print summary (--json for full index)
Enter fullscreen mode Exit fullscreen mode

Handshake pipeline 

scanProject(root) → ProjectIndex → indexToCemSnapshot() → handshake.cem
Enter fullscreen mode Exit fullscreen mode

Still read-only from disk — Sprint 3 adds SQLite persistence.

Sprint 3 — Memory Engine v0

Persist entities, relations, evidence, and events locally. Handshake reads from memory with optional refresh.

Follow along

Read the full post on meronq.pages.dev · Source on GitHub

Top comments (0)