overengineeringstudio / overengineeringstudio/effect-utils

notion md sync: watch requires explicit files; shared file doesn't pull remote-ahead

Open
#897 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:notion system:notion-md type:bug
Dominant language
TypeScript
Stars
82
Forks
2
Avg merge
1d 8h
Merged PRs (30d)
121

Description

Two gaps in notion-md sync found while building a demo.

1. Watch requires explicit files; no directory/recursive watch

notion md sync --watch . (and --recursive --watch .) errors — a single directory/path arg is read as one .nmd file:

NmdFileSystemError: Failed to read .nmd file .

Batch watch currently needs explicit filenames; there's no directory / recursive watch mode.

Expected: a directory or --recursive argument to --watch watches all .nmd files under the path.

2. source: shared file doesn't pull remote-ahead changes

A single source: shared .nmd file returns noop / in-sync on a remote-only edit. decideShared treats local ≡ base ⇒ noop, so a remote-ahead change is never pulled. Possibly a bug.

Expected: when local ≡ base but remote has advanced, sync pulls the remote-ahead changes rather than reporting noop.

Package: packages/@overeng/notion-md.

Posted on behalf of @schickling
field value
agent_name 💜 cl1-violet
agent_session_id 5ce468e2-a077-44ee-a724-bca1fb992e1c
agent_tool Claude Code
agent_tool_version 2.1.202
agent_runtime Claude Code 2.1.202
agent_model claude-opus-4-8
runtime_profile /nix/store/34v4ljmkjh4sgzax68wwgggmzf69zmfk-coding-agent-runtime-profile/share/coding-agents/profile.json
skills_manifest /nix/store/92pwq9mx1byj8nl9an05dyh4baykvf1d-agent-skills-corpus/share/agent-skills/manifest.json
worktree effect-utils/schickling/2026-07-07-notion-demo
machine mbp2025
tooling_profile dotfiles@unknown

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in packages/@overeng/notion-md by tracing how notion md sync --watch handles a directory or --recursive path, then inspect decideShared for remote-ahead behavior. Done means directory and recursive watch discover all .nmd files, and a source: shared file pulls remote-only changes instead of reporting noop or in-sync; verify both scenarios with the package's available checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.