overengineeringstudio / overengineeringstudio/effect-utils

notion-md: add managed workspace watch mode

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

Nobody has claimed this yet.

area:notion origin:agent type:feature
Dominant language
TypeScript
Stars
82
Forks
2
Avg merge
1d 8h
Merged PRs (30d)
121

Description

Context\n\nPR #679 establishes managed workspaces via notion-md sync <page> <dir> and refreshes them with one-shot notion-md sync <dir>. The CLI intentionally rejects notion-md sync <managed-workspace> --watch for now because the existing watch loop only watches an already-resolved local file set.\n\n## Desired behavior\n\nA managed workspace watcher should periodically run workspace sync so newly discovered remote child pages are materialized, while preserving the existing guarded one-page sync behavior for files already present.\n\n## Acceptance criteria\n\n- notion-md sync <managed-workspace> --watch uses workspace metadata rather than recursive unmanaged file discovery.\n- Remote child pages created after watcher startup are materialized on a poll pass.\n- Local file events still coalesce into bounded sync passes.\n- Fake E2E coverage proves new remote child materialization during watch.

Posted on behalf of @schickling
field value
agent_name 🐫 co2-arroyo
agent_session_id 1541aa19-13f8-4fa9-b520-ff423b266cea
agent_tool Codex CLI
agent_tool_version 0.130.0
agent_runtime Codex CLI 0.130.0
agent_model unknown
worktree effect-utils/schickling/2026-05-24-notion-md
machine dev3
tooling_profile dotfiles@unknown-dirty

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 with PR #679 and the CLI paths for notion-md sync <page> <dir>, one-shot managed-workspace sync, and the existing --watch loop. Trace how workspace metadata and local file events are handled, then use the fake E2E coverage to verify that a remote child created after startup is materialized and local events still coalesce into bounded sync passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.