History

Ben 751a300fca docs(cron): scope in_channel to channels; document DM continuation knob Live DM testing showed a reply to a DM cron brief did NOT continue the job. Root cause: for a 1:1 DM the governing knob is dm_top_level_threads_as_sessions (default True), NOT reply_in_thread / cron_continuable_surface. Under the default, each top-level DM keys to a per-message session (…:dm:<chat>:<ts>), so a reply mints a new ts and can never converge with the flat …:dm:<chat> session the cron seed creates. A 1:1 DM has no thread-vs-timeline split, so "in_channel" has no coherent meaning for a DM — cron_continuable_surface is a channel concept and is a no-op for DMs. DM continuation is governed entirely by dm_top_level_threads_as_sessions: - false → all top-level DMs share …:dm:<chat> → seed + reply converge → works - true (default) → per-message sessions → no continuation (cron or interactive) Option A (chosen): document the requirement; no code change (the flat-DM seed from the prior commit already lands correctly when the knob is false). Adds a ":::note 1:1 DMs" admonition to cron.md + the zh-Hans mirror. Verification (real inbound handler, not a hard-coded assumption — the mistake that made the earlier DM E2E falsely pass): tests/manual/cron_inchannel_dm_e2e.py drives the REAL _handle_slack_message for a top-level DM under both knob values and asserts false→converges (…:dm:D_TESTDM == seed), true→diverges (…:dm:D_TESTDM:<ts>). See decisions.md D9.		2026-07-01 03:16:13 -07:00
..
docs	docs(cron): scope in_channel to channels; document DM continuation knob	2026-07-01 03:16:13 -07:00
i18n/zh-Hans/docusaurus-plugin-content-docs/current	docs(cron): scope in_channel to channels; document DM continuation knob	2026-07-01 03:16:13 -07:00
scripts	refactor(cron): rebrand Cron Recipes -> Automation Blueprints	2026-06-11 10:49:47 -07:00
src	refactor(cron): rebrand Cron Recipes -> Automation Blueprints	2026-06-11 10:49:47 -07:00
static	feat: add z-ai/glm-5.2 to OpenRouter and Nous model lists	2026-06-16 23:35:45 +05:30
.gitignore	feat(skills-hub): health checks, freshness badge, and a watchdog cron (#32345 )	2026-05-25 23:10:45 -07:00
docusaurus.config.ts	docs: point desktop download links to site root (deprecate /desktop) (#46795 )	2026-06-15 15:02:24 -04:00
package-lock.json	docs(website): redirect old automation-templates URL to automation-blueprints	2026-06-12 09:46:27 -07:00
package.json	docs(website): redirect old automation-templates URL to automation-blueprints	2026-06-12 09:46:27 -07:00
README.md	docs: replace ASCII diagrams with Mermaid/lists, add linting note	2026-03-21 17:58:30 -07:00
sidebars.ts	docs: reconcile docs with code across last 3 releases (#54254 )	2026-06-28 12:47:50 -07:00
tsconfig.json	change(tooling): typecheck in CI, update ts to 6	2026-06-10 11:59:34 -04:00

README.md

Website

This website is built using Docusaurus, a modern static website generator.

Installation

yarn

Local Development

yarn start

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

Build

yarn build

This command generates static content into the build directory and can be served using any static contents hosting service.

Deployment

Using SSH:

USE_SSH=true yarn deploy

Not using SSH:

GIT_USER=<Your GitHub username> yarn deploy

If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.

Diagram Linting

CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.