Skip to content

Add nested note paths, study-note prompt, and drain subcommand - #6

Open
lorenzoliuzzo wants to merge 3 commits into
mainfrom
feat/note-drafting-drain
Open

Add nested note paths, study-note prompt, and drain subcommand#6
lorenzoliuzzo wants to merge 3 commits into
mainfrom
feat/note-drafting-drain

Conversation

@lorenzoliuzzo

Copy link
Copy Markdown
Contributor

Summary

  • Notes can now pin an exact write path with a Path: <relative>.md line in the issue body, so drafts land under the site's existing tag-nested _notes/<topic>/<subtopic>/ convention instead of a flat slug-of-the-title.
  • kind == "note" gets a stricter system prompt (LaTeX conventions, no fabricated figures/tables, flag genuinely uncertain claims instead of stating them flatly) — these are exam study notes, not general content pages.
  • New mysite drain subcommand: drafts every open my-site issue in one pass, built on the existing per-issue draft() with no new drafting logic. This is the loop a daily/timer-driven unattended run needs.

Test plan

  • pytest — 19 passed (11 new/extended cases covering path-directive parsing, nested-path dedup, note vs. non-note system prompt selection, and the drain subcommand)
  • ruff check / ruff format --check clean
  • pre-commit run (ruff + pytest-fast) green

🤖 Generated with Claude Code

lorenzoliuzzo added 3 commits August 3, 2026 12:25
Notes need a tag-nested write path (_notes/<topic>/<subtopic>/...) instead
of the flat slug-of-the-title my-site otherwise falls back to, and a
higher quality bar than the generic project/page prompt: LaTeX
conventions, no fabricated figures, and a duty to flag uncertain claims
rather than assert them.

Also adds `mysite drain`, which drafts every open my-site issue in one
pass instead of one at a time -- the loop a daily/timer-driven run needs,
built on the existing per-issue draft() with no new drafting logic.
Bulk intake for an exam syllabus, via my-server's POST /tools/my-site/issues
(the actual enqueue-API hop in the pipeline) -- everything downstream (draft,
drain) only ever sees issues, so this is the one place syllabi are a concept
at all.
Modeled on my-fleet's fleet-bookkeeping.{service,timer}: OnCalendar every
2 hours rather than daily, since this is meant to clear an exam-syllabus
backlog inside a few days rather than tick over indefinitely in the
background.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant