From 2ece5bc9c22795fe64946081344d6acca8699f45 Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Wed, 21 Oct 2026 10:27:38 +0200 Subject: [PATCH] Post a release's announcements once npm holds it, and draft them from the finished release --- AGENTS.md | 1 + docs/decisions.md | 7 +++++++ todo.md | 7 ++++--- 3 files changed, 12 insertions(+), 3 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index b6578b2..3ce855b 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -54,6 +54,7 @@ In `docs/decisions.md`: - Publish on a version bump - Docs describe the release being built - Plan items rank by `rank_todo.py`'s goal weights, code health first +- Posts announcing a release wait for its publish, and their drafts wait for the finished release - No schema validation - The gate runs on Deno and Bun - The gate installs the tarball diff --git a/docs/decisions.md b/docs/decisions.md index 1c128a5..2cc4ad4 100644 --- a/docs/decisions.md +++ b/docs/decisions.md @@ -601,6 +601,13 @@ weighs 4 times its position weight. README goal 10 restates code health until it `todo.md`'s `## Scoring` keeps the formula and the bar, the lowest Score a non-exempt item may have. Both are the project's to tune: the maintainer confirmed the bar at 0.1 on 2026-10-21. +## Posts announcing a release wait for its publish, and their drafts wait for the finished release + +2026-10-21, the agent, choosing at the maintainer's request what best serves the goals. Serves Goal 3: +its counter-signal is issues saying a call did something else, and a post that runs ahead of npm sends +readers to a version without what the post describes. Drafts describe the finished release, so they +wait for every item in it. Valid while a version bump on `main` publishes (§Publish on a version bump). + ## No schema validation 2026-08-23, the mark refusal 2026-08-25, the maintainer. Goal 1. Valid while the site a document diff --git a/todo.md b/todo.md index f875db9..8821702 100644 --- a/todo.md +++ b/todo.md @@ -178,12 +178,13 @@ three directories. ### 73. Announce the package where someone needing an ADF converter already reads: JRACLOUD-77436, the Atlassian developer community and Stack Overflow's ADF-to-markdown questions. -Blocked by every other `0.3.0` item (the maintainer, 2026-10-14): the posts announce the finished +Blocked by every other `0.3.0` item (the maintainer, 2026-10-14): the drafts describe the finished release. Each post links the GitHub repository, the README's comparison table and a README that opens with what the package is. Before posting, set `converter-comparison/run.sh`'s pins to each package's latest version, `@larvit/adf-codec@0.3.0` included, and `--before` to today. Run it, then bring the README table, -its versions and its date in step with the output. We draft each post for the place it goes; the -maintainer posts them once `0.3.0` is published. Found while planning discoverability, 2026-10-04. +its versions and its date in step with the output. We draft each post for the place it goes. The +maintainer posts them once `0.3.0` is published (`docs/decisions.md` §Posts announcing a release +wait for its publish). Found while planning discoverability, 2026-10-04. ### 45. Replace `isAdfDocument` with a reader returning `Result`.