Skip to content

Mr Folio's /roadmap shows the releases still being built - #250

Merged
McCal-Codes merged 1 commit into
mainfrom
bot-roadmap-after-rewrite
Oct 2, 2026
Merged

McCal-Codes merged 1 commit into
mainfrom
bot-roadmap-after-rewrite

Conversation

@McCal-Codes

Copy link
Copy Markdown
Owner

What this changes

Mr Folio's /roadmap is wrong on Discord right now, and it is my doing. The command treated every roadmap section with a version as "shipped" and left it out. The roadmap rewrite (#240, merged earlier today) moved "Next" into release sections (0.6.8, 0.6.9, 0.7.0, 0.7.1), so since then:

  • /roadmap lists only Later and Exploring, and
  • /roadmap next answers "Nothing under next."

Now:

  • A release section counts as shipped only when every item in it is done, so the release in progress and the ones after it are shown.
  • /roadmap next means those releases, named with their theme: "Folio 0.6.9 (Foundation)". Later and Exploring work as before.
  • sources.mjs passes release along, and reads the optional subtitle the new roadmap page uses.

How I checked it

  • node --test in tools/folio-bot: 28 pass (one test changed to the new shape, one added for next).
  • Ran the real handler against the real roadmap.json on main: /roadmap and /roadmap next show Folio 0.6.8 and Folio 0.6.9 (Foundation) with their items, and /roadmap later shows Later.
  • Not deployed. The bot is a Cloudflare Worker, and deploying it is yours: from tools/folio-bot, ~/dev/folio-site/node_modules/.bin/wrangler deploy (npx wrangler@4 hangs, per the notes). Until then /roadmap stays wrong.

Cheap way out: revert; no other command reads these fields.

  • No app change, so no CHANGELOG line (REL-7 skipped)

@McCal-Codes
McCal-Codes merged commit 2cb6c28 into main Oct 2, 2026
3 checks passed
@McCal-Codes
McCal-Codes deleted the bot-roadmap-after-rewrite branch October 2, 2026 21:13

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cc956476bd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

return {
name: section.release ? `Folio ${section.release}${section.subtitle ? ` (${section.subtitle})` : ''}` : section.title,
release: Boolean(section.release),
shipped: Boolean(section.release) && items.length > 0 && items.every((item) => item.status === 'done'),

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Reserve space for every requested roadmap section

With the reviewed app/src/main/assets/roadmap.json, this retains four unfinished release sections in addition to Later and Exploring. The unchanged handler emits up to six items per section and only trims the fully assembled message afterward, so /roadmap reaches 1,999 characters partway through Folio 0.7.1, omits Later and Exploring entirely, cuts a sentence mid-word, and drops the whole-roadmap link; /roadmap next is truncated similarly. Budget or summarize each block before assembling the response so every requested section and the link remain visible.

Useful? React with 👍 / 👎.

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