overengineeringstudio / overengineeringstudio/effect-utils
notion-md: add live Notion E2E coverage for managed workspace materialization
Open
Nobody has claimed this yet.
area:notion
origin:agent
type:chore
- Dominant language
- TypeScript
- Stars
- 82
- Forks
- 2
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 121
Description
Context\n\nPR #679 covers managed workspace materialization with the fake gateway. Live Notion coverage should be added separately because the fixture must safely create, discover, and clean up child pages.\n\n## Acceptance criteria\n\n- The live fixture creates a parent page with at least one child page.\n- notion-md sync <page> <dir> materializes root and child files.\n- A later remote child page is discovered by notion-md sync <dir>.\n- Cleanup is allowlisted and cannot archive unrelated pages.\n- The run ledger records the fixture and cleanup behavior.
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing PR #679 and the existing fake-gateway coverage for managed workspace materialization. Add live Notion E2E coverage around notion-md sync <page> <dir> and notion-md sync <dir>, with an allowlisted fixture and cleanup; done means root and child files materialize, later children are discovered, and the run ledger records setup and cleanup.
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
- 52/100