overengineeringstudio / overengineeringstudio/effect-utils

notion-md production hardening follow-ups

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

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

Follow-up tracking for notion-md after PR #671.\n\nAcceptance criteria:\n\n- Add required or explicitly gated live Notion coverage for release/admission paths.\n- Add in-memory OTEL trace assertions for status, push, watch errors, gateway markdown updates, and object-store operations.\n- Define the stable CLI output contract for one-shot JSON and watch NDJSON modes.\n- Refactor watch internals toward an Effect-native event/clock core so coalescing, self-write suppression, and error behavior are deterministic in tests.\n- Extend storage transition coverage for object-store refresh/downgrade and comment/file inventory preservation.\n\nRefs #671.

Posted on behalf of @schickling
field value
agent_name 🚗 co1-ford
agent_session_id 0d338626-aaeb-473e-b1b4-5d3a9ed2231e
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-22-notion-md
machine dev3
tooling_profile dotfiles@4e6515b

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 #671 and trace the release/admission paths, status, push, watch, gateway markdown updates, and object-store operations named in the acceptance criteria. Done requires live coverage, in-memory OTEL assertions, stable JSON and NDJSON CLI contracts, deterministic watch behavior, and storage transition coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend, cli, observability, testing
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.