Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Contributor
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (92)
📝 WalkthroughWalkthroughAdds a full 0.13.x documentation set (concepts, how-tos, tutorials), multi-language SDK references, 0.11.0 migration guides, a 0.16.0 changelog entry, and updates docs.json to wire new versioned navigation. Changes0.13.x docs set, SDK refs, migrations, and navigation
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Suggested reviewers
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
|
3 tasks
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
skill-check — docs49 verified, 300 skipped. 6 errors, 7 warnings across the verified workers.
Caution Rendered artifacts were out of date — sources had changed without re-rendering. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 8
♻️ Duplicate comments (5)
docs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdx (1)
1-6:⚠️ Potential issue | 🟡 MinorIncomplete tutorial content.
This page also contains only placeholder frontmatter without implementation content.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdx` around lines 1 - 6, The file docs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdx currently contains only placeholder frontmatter (title: "Orchestration loop") and no tutorial content; replace the placeholder with a complete tutorial: add an intro explaining the orchestration loop concept, a step‑by‑step walkthrough of the loop lifecycle, concrete code examples/snippets showing the orchestration loop implementation (referencing functions/classes used in the repo for agent orchestration), expected inputs/outputs and error handling, and helpful links/resources; ensure the frontmatter remains valid and include section headers (e.g., Overview, Implementation, Examples, Troubleshooting) so the page is a usable tutorial rather than just a stub.docs/0-13-0/tutorials/build-an-agent/memory-and-state.mdx (1)
1-6:⚠️ Potential issue | 🟡 MinorIncomplete tutorial content.
Like define-tools.mdx, this page contains only placeholder frontmatter without implementation content.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/0-13-0/tutorials/build-an-agent/memory-and-state.mdx` around lines 1 - 6, The file currently only has frontmatter for the "Memory and state" tutorial; replace the placeholder with a full MDX tutorial modeled after define-tools.mdx: keep the existing frontmatter (title/description/owner/type) and add an introduction, clear sections describing memory vs. state, supported memory stores and lifetimes, code examples showing how to instantiate and use the Memory API (e.g., examples that call createMemory/useMemory or whichever functions your codebase provides), a step‑by‑step agent example demonstrating persistence across calls, and links to relevant reference docs; use the same headings, formatting, and example style as define-tools.mdx so reviewers can compare structure and ensure completeness.docs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdx (1)
1-6:⚠️ Potential issue | 🟡 Minor | 🏗️ Heavy liftIncomplete tutorial stub referenced from overview.
This tutorial file contains only frontmatter with a "Placeholder." description but no actual content. The overview page references this as step 1 of the incremental adoption flow.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdx` around lines 1 - 6, The tutorial file with title "Wrap an existing API" currently only contains frontmatter with a "Placeholder." description; replace the placeholder by writing the full tutorial content: update the frontmatter description to a concise summary and add sections (Introduction, Prerequisites, Step-by-step instructions to wrap an existing API, code examples/snippets, expected outcomes, and links to related docs), ensure the tutorial covers the incremental-adoption flow referenced by the overview (describe inputs/outputs and any config or commands), and validate the MDX compiles and links correctly so the overview’s step 1 points to a complete, runnable tutorial for users.docs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdx (1)
1-6:⚠️ Potential issue | 🟡 Minor | 🏗️ Heavy liftIncomplete tutorial stub referenced from overview.
This tutorial file contains only frontmatter with a "Placeholder." description but no actual content. The overview page references this as step 2 of the incremental adoption flow. Users following the tutorial sequence will encounter an empty page.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdx` around lines 1 - 6, The "Offload work to a queue" tutorial contains only frontmatter with a placeholder description; replace the placeholder by adding the actual tutorial content for step 2 of the incremental adoption flow: update the frontmatter description and add sections that include a short overview, prerequisites, step-by-step instructions for offloading tasks to a queue (concepts, recommended queue technology, enqueuing/dequeuing patterns), at least one minimal code example and configuration snippet, troubleshooting notes, and a "Next steps" link back to the incremental adoption overview; ensure the content is authored under the existing title "Offload work to a queue" so the overview page’s reference resolves correctly.docs/0-13-0/tutorials/incremental-adoption/overview.mdx (1)
25-32:⚠️ Potential issue | 🟡 Minor | 🏗️ Heavy liftTutorial references point to incomplete placeholder pages.
The three sub-tutorial links reference files that currently contain only frontmatter stubs with "Placeholder." descriptions and no content. Users following this tutorial flow will encounter empty pages at each step.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/0-13-0/tutorials/incremental-adoption/overview.mdx` around lines 25 - 32, The three tutorial links ("Wrap an existing API" -> ./wrap-existing-api, "Offload work to a queue" -> ./offload-to-queue, and "Migrate persistence" -> ./migrate-persistence) point to placeholder pages; update each referenced MDX file to include real tutorial content or meaningful redirects: replace the frontmatter-only "Placeholder." with a short, actionable step-by-step tutorial (objectives, prerequisites, code/examples, and next steps) or add a redirect/notice that links back to the overview until full content is available so readers following the incremental-adoption flow don't hit empty pages.
🧹 Nitpick comments (1)
docs/0-13-0/understanding-iii/functions.mdx (1)
30-30: ⚡ Quick winTODO comment in archived documentation.
This file is being archived as part of the 0.13.0 snapshot. The TODO comment about restricted string prefixes should ideally be resolved before archiving to ensure the documentation is complete.
Do you want me to help search the codebase to confirm whether restricted string prefixes still exist in 0.13.0?
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/0-13-0/understanding-iii/functions.mdx` at line 30, The archived docs file contains a lingering TODO about "restricted string prefixes"; search the codebase for the exact phrase "restricted string prefixes" and related symbols (config keys, constants, or feature flags) to confirm whether the feature exists in 0.13.0, then update docs/0-13-0/understanding-iii/functions.mdx by replacing the TODO with a short factual statement (either confirming the prefixes remain and linking to the relevant constant/flag, or stating they were removed in 0.13.0 and referencing the commit or changelog entry); if you find nothing, remove the TODO and add a one-line note that the feature is not present in 0.13.0.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/0-11-0/api-reference/sdk-node.mdx`:
- Line 190: The example in the sdk-node docs uses a 5-field cron expression in
the config object (config: { expression: '*/5 * * * *' }) but elsewhere the
project expects 6- or 7-field cron syntax; update the example by replacing the
expression value with a 6-field example such as "0 */5 * * * *" (or
alternatively add a short clarifying note next to the config.expression example
stating that '*/5 * * * *' is the legacy 5-field Motia format) so the sdk-node
example matches the documented 6/7-field expectation.
In `@docs/0-13-0/install.mdx`:
- Line 15: In docs/0-13-0/install.mdx the installer curl uses the generic URL
"https://install.iii.dev/iii/main/install.sh" which may mislead readers of
archived docs into thinking it installs v0.13.x; either update the curl command
to point to a version-pinned installer (e.g., replace "/iii/main/install.sh"
with a "/iii/0-13-0/install.sh" route) or add a one-line clarifying note above
the command that the "main" installer tracks the latest release and does not
necessarily install 0.13.x (same change should be applied to other archived
pages that use "/iii/main/").
- Around line 40-43: The Card in docs/0-13-0/install.mdx uses href="/using-iii"
which points to a non-existent landing page; either update that Card's href (the
Card element with title="Use iii") to a valid existing route such as
"/using-iii/workers" or create a new index page at
docs/0-13-0/using-iii/index.mdx and add the corresponding nav entry so
href="/using-iii" resolves; modify the Card href or add the index.mdx and nav
route accordingly.
In `@docs/0-13-0/sdk-reference/engine-sdk.mdx`:
- Around line 12-14: The SDK links in the text ([Node](/sdk-reference/node-sdk),
[Python](/sdk-reference/python-sdk), [Rust](/sdk-reference/rust-sdk),
[Browser](/sdk-reference/browser-sdk)) point to the root docs instead of the
0.13 archive; update those hrefs to the 0.13 archive paths (e.g.
/0-13-0/sdk-reference/node-sdk, /0-13-0/sdk-reference/python-sdk,
/0-13-0/sdk-reference/rust-sdk, /0-13-0/sdk-reference/browser-sdk) or convert
them to correct relative links so they resolve within the
docs/0-13-0/sdk-reference/ archive.
In `@docs/0-13-0/tutorials/build-an-agent/define-tools.mdx`:
- Around line 1-6: The page "Define tools" currently contains only frontmatter
(title/description/owner/type) and a placeholder description; replace the
placeholder by adding real tutorial content under the same file (the "Define
tools" page) that matches the "build an agent" tutorial flow: add a brief
overview, step-by-step instructions for defining tools, concrete
examples/snippets showing tool interfaces and registration, expected
inputs/outputs, and links/backrefs to overview.mdx; ensure the new content uses
the existing frontmatter fields (title: "Define tools") and fits the 0.13
archive tone so the overview.mdx step resolves to a complete implementation
guide.
In `@docs/0-13-0/using-iii/cli.mdx.skill.md`:
- Line 53: The generator (iii-skill-render) is exposing internal "llm-only"
directives by stripping JSX comment delimiters and leaving their content in
output; update the renderer to detect the `{/* llm-only:` pattern and either
preserve the original JSX comment delimiters in the generated .skill.md output
or strip the entire line when producing skill markdown, and add a
unit/integration test that feeds a source containing `{/* llm-only:` to ensure
the output neither reveals nor mangles the directive.
In `@docs/0-13-0/using-iii/deployment.mdx`:
- Around line 60-75: The Caddy configuration code block is missing a language
identifier which prevents syntax highlighting; update the fenced code block in
the documentation by adding "caddyfile" immediately after the opening triple
backticks (so the block starts with ```caddyfile) to enable proper highlighting
for the shown Caddy directives (e.g., the your-domain.com block and
handle/reverse_proxy entries).
In `@docs/0-13-0/using-iii/deployment.mdx.skill.md`:
- Line 16: The generated skill docs are leaking internal "llm-only:" blocks into
user-facing .skill.md output; update the documentation generation logic (e.g.,
the function(s) responsible for producing skill markdown such as generateSkillMd
/ skillDocRenderer) to detect and strip or hide any {/* llm-only: ... */} blocks
(and equivalent inline markers) before rendering/writing .skill.md, ensure the
parser handles both single-line and multiline variants, and add a
unit/integration check that asserts no "llm-only" content appears in the
produced .skill.md files.
---
Duplicate comments:
In `@docs/0-13-0/tutorials/build-an-agent/memory-and-state.mdx`:
- Around line 1-6: The file currently only has frontmatter for the "Memory and
state" tutorial; replace the placeholder with a full MDX tutorial modeled after
define-tools.mdx: keep the existing frontmatter (title/description/owner/type)
and add an introduction, clear sections describing memory vs. state, supported
memory stores and lifetimes, code examples showing how to instantiate and use
the Memory API (e.g., examples that call createMemory/useMemory or whichever
functions your codebase provides), a step‑by‑step agent example demonstrating
persistence across calls, and links to relevant reference docs; use the same
headings, formatting, and example style as define-tools.mdx so reviewers can
compare structure and ensure completeness.
In `@docs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdx`:
- Around line 1-6: The file
docs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdx currently contains
only placeholder frontmatter (title: "Orchestration loop") and no tutorial
content; replace the placeholder with a complete tutorial: add an intro
explaining the orchestration loop concept, a step‑by‑step walkthrough of the
loop lifecycle, concrete code examples/snippets showing the orchestration loop
implementation (referencing functions/classes used in the repo for agent
orchestration), expected inputs/outputs and error handling, and helpful
links/resources; ensure the frontmatter remains valid and include section
headers (e.g., Overview, Implementation, Examples, Troubleshooting) so the page
is a usable tutorial rather than just a stub.
In `@docs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdx`:
- Around line 1-6: The "Offload work to a queue" tutorial contains only
frontmatter with a placeholder description; replace the placeholder by adding
the actual tutorial content for step 2 of the incremental adoption flow: update
the frontmatter description and add sections that include a short overview,
prerequisites, step-by-step instructions for offloading tasks to a queue
(concepts, recommended queue technology, enqueuing/dequeuing patterns), at least
one minimal code example and configuration snippet, troubleshooting notes, and a
"Next steps" link back to the incremental adoption overview; ensure the content
is authored under the existing title "Offload work to a queue" so the overview
page’s reference resolves correctly.
In `@docs/0-13-0/tutorials/incremental-adoption/overview.mdx`:
- Around line 25-32: The three tutorial links ("Wrap an existing API" ->
./wrap-existing-api, "Offload work to a queue" -> ./offload-to-queue, and
"Migrate persistence" -> ./migrate-persistence) point to placeholder pages;
update each referenced MDX file to include real tutorial content or meaningful
redirects: replace the frontmatter-only "Placeholder." with a short, actionable
step-by-step tutorial (objectives, prerequisites, code/examples, and next steps)
or add a redirect/notice that links back to the overview until full content is
available so readers following the incremental-adoption flow don't hit empty
pages.
In `@docs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdx`:
- Around line 1-6: The tutorial file with title "Wrap an existing API" currently
only contains frontmatter with a "Placeholder." description; replace the
placeholder by writing the full tutorial content: update the frontmatter
description to a concise summary and add sections (Introduction, Prerequisites,
Step-by-step instructions to wrap an existing API, code examples/snippets,
expected outcomes, and links to related docs), ensure the tutorial covers the
incremental-adoption flow referenced by the overview (describe inputs/outputs
and any config or commands), and validate the MDX compiles and links correctly
so the overview’s step 1 points to a complete, runnable tutorial for users.
---
Nitpick comments:
In `@docs/0-13-0/understanding-iii/functions.mdx`:
- Line 30: The archived docs file contains a lingering TODO about "restricted
string prefixes"; search the codebase for the exact phrase "restricted string
prefixes" and related symbols (config keys, constants, or feature flags) to
confirm whether the feature exists in 0.13.0, then update
docs/0-13-0/understanding-iii/functions.mdx by replacing the TODO with a short
factual statement (either confirming the prefixes remain and linking to the
relevant constant/flag, or stating they were removed in 0.13.0 and referencing
the commit or changelog entry); if you find nothing, remove the TODO and add a
one-line note that the feature is not present in 0.13.0.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 2709e2be-3ebd-404a-96d9-01bb0dc72841
⛔ Files ignored due to path filters (3)
docs/0-13-0/assets/favicon.svgis excluded by!**/*.svgdocs/0-13-0/assets/iii-black.svgis excluded by!**/*.svgdocs/0-13-0/assets/iii-white.svgis excluded by!**/*.svg
📒 Files selected for processing (97)
docs/0-11-0/api-reference/sdk-node.mdxdocs/0-11-0/api-reference/sdk-python.mdxdocs/0-11-0/api-reference/sdk-rust.mdxdocs/0-11-0/scripts/generate-api-docs.mtsdocs/0-11-0/scripts/parsers/parse-rustdoc.mtsdocs/0-13-0/changelog/0-11-0/everything-is-a-worker.mdxdocs/0-13-0/changelog/0-11-0/migrated-examples.mdxdocs/0-13-0/changelog/0-11-0/migrating-from-motia-js.mdxdocs/0-13-0/changelog/0-11-0/migrating-from-motia-py.mdxdocs/0-13-0/changelog/index.mdxdocs/0-13-0/creating-workers/functions.mdxdocs/0-13-0/creating-workers/functions.mdx.skill.mddocs/0-13-0/creating-workers/triggers.mdxdocs/0-13-0/creating-workers/triggers.mdx.skill.mddocs/0-13-0/creating-workers/workers-registry.mdxdocs/0-13-0/creating-workers/workers-registry.mdx.skill.mddocs/0-13-0/creating-workers/workers.mdxdocs/0-13-0/creating-workers/workers.mdx.skill.mddocs/0-13-0/how-to/build-a-realtime-todo-app.mdxdocs/0-13-0/how-to/build-a-realtime-todo-app.mdx.skill.mddocs/0-13-0/index.mdxdocs/0-13-0/index.mdx.skill.mddocs/0-13-0/install.mdxdocs/0-13-0/install.mdx.skill.mddocs/0-13-0/patterns/adapter-pattern.mdxdocs/0-13-0/patterns/adapter-pattern.mdx.skill.mddocs/0-13-0/patterns/reactive-state-pattern.mdxdocs/0-13-0/patterns/reactive-state-pattern.mdx.skill.mddocs/0-13-0/quickstart.mdxdocs/0-13-0/quickstart.mdx.skill.mddocs/0-13-0/sdk-reference/browser-sdk.mdxdocs/0-13-0/sdk-reference/browser-sdk.mdx.skill.mddocs/0-13-0/sdk-reference/engine-sdk.mdxdocs/0-13-0/sdk-reference/engine-sdk.mdx.skill.mddocs/0-13-0/sdk-reference/node-sdk.mdxdocs/0-13-0/sdk-reference/node-sdk.mdx.skill.mddocs/0-13-0/sdk-reference/python-sdk.mdxdocs/0-13-0/sdk-reference/python-sdk.mdx.skill.mddocs/0-13-0/sdk-reference/rust-sdk.mdxdocs/0-13-0/sdk-reference/rust-sdk.mdx.skill.mddocs/0-13-0/tutorials/build-an-agent/define-tools.mdxdocs/0-13-0/tutorials/build-an-agent/define-tools.mdx.skill.mddocs/0-13-0/tutorials/build-an-agent/memory-and-state.mdxdocs/0-13-0/tutorials/build-an-agent/memory-and-state.mdx.skill.mddocs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdxdocs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdx.skill.mddocs/0-13-0/tutorials/build-an-agent/overview.mdxdocs/0-13-0/tutorials/build-an-agent/overview.mdx.skill.mddocs/0-13-0/tutorials/incremental-adoption/migrate-persistence.mdxdocs/0-13-0/tutorials/incremental-adoption/migrate-persistence.mdx.skill.mddocs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdxdocs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdx.skill.mddocs/0-13-0/tutorials/incremental-adoption/overview.mdxdocs/0-13-0/tutorials/incremental-adoption/overview.mdx.skill.mddocs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdxdocs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdx.skill.mddocs/0-13-0/tutorials/reactive-crud/crud-endpoints.mdxdocs/0-13-0/tutorials/reactive-crud/crud-endpoints.mdx.skill.mddocs/0-13-0/tutorials/reactive-crud/model-and-store.mdxdocs/0-13-0/tutorials/reactive-crud/model-and-store.mdx.skill.mddocs/0-13-0/tutorials/reactive-crud/overview.mdxdocs/0-13-0/tutorials/reactive-crud/overview.mdx.skill.mddocs/0-13-0/tutorials/reactive-crud/realtime-subscriptions.mdxdocs/0-13-0/tutorials/reactive-crud/realtime-subscriptions.mdx.skill.mddocs/0-13-0/understanding-iii/channels.mdxdocs/0-13-0/understanding-iii/channels.mdx.skill.mddocs/0-13-0/understanding-iii/engine.mdxdocs/0-13-0/understanding-iii/engine.mdx.skill.mddocs/0-13-0/understanding-iii/functions.mdxdocs/0-13-0/understanding-iii/functions.mdx.skill.mddocs/0-13-0/understanding-iii/index.mdxdocs/0-13-0/understanding-iii/index.mdx.skill.mddocs/0-13-0/understanding-iii/triggers.mdxdocs/0-13-0/understanding-iii/triggers.mdx.skill.mddocs/0-13-0/understanding-iii/workers.mdxdocs/0-13-0/understanding-iii/workers.mdx.skill.mddocs/0-13-0/using-iii/channels.mdxdocs/0-13-0/using-iii/channels.mdx.skill.mddocs/0-13-0/using-iii/cli.mdxdocs/0-13-0/using-iii/cli.mdx.skill.mddocs/0-13-0/using-iii/console.mdxdocs/0-13-0/using-iii/console.mdx.skill.mddocs/0-13-0/using-iii/deployment.mdxdocs/0-13-0/using-iii/deployment.mdx.skill.mddocs/0-13-0/using-iii/engine.mdxdocs/0-13-0/using-iii/engine.mdx.skill.mddocs/0-13-0/using-iii/functions.mdxdocs/0-13-0/using-iii/functions.mdx.skill.mddocs/0-13-0/using-iii/triggers.mdxdocs/0-13-0/using-iii/triggers.mdx.skill.mddocs/0-13-0/using-iii/workers-registry.mdxdocs/0-13-0/using-iii/workers-registry.mdx.skill.mddocs/0-13-0/using-iii/workers.mdxdocs/0-13-0/using-iii/workers.mdx.skill.mddocs/changelog/0-16-0/align-rust-register-function-with-signature.mdxdocs/changelog/index.mdxdocs/docs.json
Contributor
Author
|
Approved |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 7
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/0-13-0/sdk-reference/node-sdk.mdx.skill.md`:
- Around line 124-126: Update the documentation line that maps common engine
`code` values so that `invocation_stopped` is described as a worker
disconnect/cancel mid-flight (not an engine timeout), and explicitly state that
`TIMEOUT` is the timeout case; keep the other values (`invocation_failed`,
`function_not_found`, `function_not_invokable`, `FORBIDDEN`) unchanged. Locate
the sentence containing the list of codes (the string "Common `code` values come
from the engine: `invocation_failed` ...") and rewrite the description for
`invocation_stopped` and `TIMEOUT` to match the engine protocol wording.
In `@docs/0-13-0/understanding-iii/functions.mdx`:
- Line 30: Resolve the in-page TODO comment "/* TODO: Confirm if we still have
restricted string prefixes */" in functions.mdx: either remove the TODO and its
comment if there is no restriction, or replace it with a short definitive
statement documenting the restriction (what the restricted string prefixes are,
when they apply, and a short example or link to the authoritative policy), and
ensure the updated text follows the docs style and consistency guidelines before
merging.
In `@docs/0-13-0/using-iii/cli.mdx.skill.md`:
- Line 10: Fix the typo in the help example string: change the incorrect word
"sucommand" to "subcommand" in the example line that reads "iii subcommand
--help `#lists` the specific actions each sucommand accepts" so the example
correctly shows "iii subcommand --help `#lists` the specific actions each
subcommand accepts".
- Line 41: The table links `#updating-iii-itself` to the update section but the
actual heading is `## Updating iii` (slug `#updating-iii`), so update the anchor
in the table entries that reference `#updating-iii-itself` (the two occurrences
shown around the `| `iii update` |` row) to use `#updating-iii`, or
alternatively rename the section heading to `## Updating iii itself` so the slug
matches; change the link target or heading consistently for both occurrences.
In `@docs/0-13-0/using-iii/deployment.mdx.skill.md`:
- Line 58: The Caddy code fence is missing a language tag which affects syntax
highlighting and linting; update the opening backtick fence that precedes the
snippet containing "your-domain.com {" and "handle /api/* {" to use a language
tag (e.g., change the opening "```" to "```caddyfile" or "```text") so the
Caddyfile block is properly recognized and rendered.
In `@docs/0-13-0/using-iii/workers-registry.mdx`:
- Line 45: Replace the phrase "Docker / OCI compatible image" with the
hyphenated compound "Docker/OCI-compatible image" to normalize wording; search
for the exact string "Docker / OCI compatible image" in the document (look for
the sentence containing that phrase) and update it to "Docker/OCI-compatible
image" so the compound adjective is consistently hyphenated.
In `@docs/0-13-0/using-iii/workers.mdx`:
- Around line 17-18: The sentence contains a duplicated word sequence "adding
functionality that functionality"; update the sentence in
docs/0-13-0/using-iii/workers.mdx to remove the redundancy (e.g., change "adding
functionality that functionality will come in the form of a worker" to "adding
functionality will come in the form of a worker" or "adding new functionality
will come in the form of a worker") so the overview reads clearly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: a1c6f37d-b1fc-4240-a6bb-b34404d23346
⛔ Files ignored due to path filters (3)
docs/0-13-0/assets/favicon.svgis excluded by!**/*.svgdocs/0-13-0/assets/iii-black.svgis excluded by!**/*.svgdocs/0-13-0/assets/iii-white.svgis excluded by!**/*.svg
📒 Files selected for processing (92)
docs/0-13-0/changelog/0-11-0/everything-is-a-worker.mdxdocs/0-13-0/changelog/0-11-0/migrated-examples.mdxdocs/0-13-0/changelog/0-11-0/migrating-from-motia-js.mdxdocs/0-13-0/changelog/0-11-0/migrating-from-motia-py.mdxdocs/0-13-0/changelog/index.mdxdocs/0-13-0/creating-workers/functions.mdxdocs/0-13-0/creating-workers/functions.mdx.skill.mddocs/0-13-0/creating-workers/triggers.mdxdocs/0-13-0/creating-workers/triggers.mdx.skill.mddocs/0-13-0/creating-workers/workers-registry.mdxdocs/0-13-0/creating-workers/workers-registry.mdx.skill.mddocs/0-13-0/creating-workers/workers.mdxdocs/0-13-0/creating-workers/workers.mdx.skill.mddocs/0-13-0/how-to/build-a-realtime-todo-app.mdxdocs/0-13-0/how-to/build-a-realtime-todo-app.mdx.skill.mddocs/0-13-0/index.mdxdocs/0-13-0/index.mdx.skill.mddocs/0-13-0/install.mdxdocs/0-13-0/install.mdx.skill.mddocs/0-13-0/patterns/adapter-pattern.mdxdocs/0-13-0/patterns/adapter-pattern.mdx.skill.mddocs/0-13-0/patterns/reactive-state-pattern.mdxdocs/0-13-0/patterns/reactive-state-pattern.mdx.skill.mddocs/0-13-0/quickstart.mdxdocs/0-13-0/quickstart.mdx.skill.mddocs/0-13-0/sdk-reference/browser-sdk.mdxdocs/0-13-0/sdk-reference/browser-sdk.mdx.skill.mddocs/0-13-0/sdk-reference/engine-sdk.mdxdocs/0-13-0/sdk-reference/engine-sdk.mdx.skill.mddocs/0-13-0/sdk-reference/node-sdk.mdxdocs/0-13-0/sdk-reference/node-sdk.mdx.skill.mddocs/0-13-0/sdk-reference/python-sdk.mdxdocs/0-13-0/sdk-reference/python-sdk.mdx.skill.mddocs/0-13-0/sdk-reference/rust-sdk.mdxdocs/0-13-0/sdk-reference/rust-sdk.mdx.skill.mddocs/0-13-0/tutorials/build-an-agent/define-tools.mdxdocs/0-13-0/tutorials/build-an-agent/define-tools.mdx.skill.mddocs/0-13-0/tutorials/build-an-agent/memory-and-state.mdxdocs/0-13-0/tutorials/build-an-agent/memory-and-state.mdx.skill.mddocs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdxdocs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdx.skill.mddocs/0-13-0/tutorials/build-an-agent/overview.mdxdocs/0-13-0/tutorials/build-an-agent/overview.mdx.skill.mddocs/0-13-0/tutorials/incremental-adoption/migrate-persistence.mdxdocs/0-13-0/tutorials/incremental-adoption/migrate-persistence.mdx.skill.mddocs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdxdocs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdx.skill.mddocs/0-13-0/tutorials/incremental-adoption/overview.mdxdocs/0-13-0/tutorials/incremental-adoption/overview.mdx.skill.mddocs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdxdocs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdx.skill.mddocs/0-13-0/tutorials/reactive-crud/crud-endpoints.mdxdocs/0-13-0/tutorials/reactive-crud/crud-endpoints.mdx.skill.mddocs/0-13-0/tutorials/reactive-crud/model-and-store.mdxdocs/0-13-0/tutorials/reactive-crud/model-and-store.mdx.skill.mddocs/0-13-0/tutorials/reactive-crud/overview.mdxdocs/0-13-0/tutorials/reactive-crud/overview.mdx.skill.mddocs/0-13-0/tutorials/reactive-crud/realtime-subscriptions.mdxdocs/0-13-0/tutorials/reactive-crud/realtime-subscriptions.mdx.skill.mddocs/0-13-0/understanding-iii/channels.mdxdocs/0-13-0/understanding-iii/channels.mdx.skill.mddocs/0-13-0/understanding-iii/engine.mdxdocs/0-13-0/understanding-iii/engine.mdx.skill.mddocs/0-13-0/understanding-iii/functions.mdxdocs/0-13-0/understanding-iii/functions.mdx.skill.mddocs/0-13-0/understanding-iii/index.mdxdocs/0-13-0/understanding-iii/index.mdx.skill.mddocs/0-13-0/understanding-iii/triggers.mdxdocs/0-13-0/understanding-iii/triggers.mdx.skill.mddocs/0-13-0/understanding-iii/workers.mdxdocs/0-13-0/understanding-iii/workers.mdx.skill.mddocs/0-13-0/using-iii/channels.mdxdocs/0-13-0/using-iii/channels.mdx.skill.mddocs/0-13-0/using-iii/cli.mdxdocs/0-13-0/using-iii/cli.mdx.skill.mddocs/0-13-0/using-iii/console.mdxdocs/0-13-0/using-iii/console.mdx.skill.mddocs/0-13-0/using-iii/deployment.mdxdocs/0-13-0/using-iii/deployment.mdx.skill.mddocs/0-13-0/using-iii/engine.mdxdocs/0-13-0/using-iii/engine.mdx.skill.mddocs/0-13-0/using-iii/functions.mdxdocs/0-13-0/using-iii/functions.mdx.skill.mddocs/0-13-0/using-iii/triggers.mdxdocs/0-13-0/using-iii/triggers.mdx.skill.mddocs/0-13-0/using-iii/workers-registry.mdxdocs/0-13-0/using-iii/workers-registry.mdx.skill.mddocs/0-13-0/using-iii/workers.mdxdocs/0-13-0/using-iii/workers.mdx.skill.mddocs/changelog/0-16-0/align-rust-register-function-with-signature.mdxdocs/changelog/index.mdxdocs/docs.json
✅ Files skipped from review due to trivial changes (51)
- docs/0-13-0/tutorials/reactive-crud/realtime-subscriptions.mdx.skill.md
- docs/0-13-0/tutorials/reactive-crud/model-and-store.mdx
- docs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdx
- docs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdx.skill.md
- docs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdx.skill.md
- docs/0-13-0/tutorials/reactive-crud/crud-endpoints.mdx.skill.md
- docs/0-13-0/understanding-iii/channels.mdx.skill.md
- docs/0-13-0/tutorials/reactive-crud/crud-endpoints.mdx
- docs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdx
- docs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdx.skill.md
- docs/0-13-0/tutorials/reactive-crud/model-and-store.mdx.skill.md
- docs/0-13-0/tutorials/build-an-agent/define-tools.mdx.skill.md
- docs/0-13-0/tutorials/incremental-adoption/migrate-persistence.mdx
- docs/0-13-0/tutorials/reactive-crud/overview.mdx.skill.md
- docs/0-13-0/tutorials/incremental-adoption/migrate-persistence.mdx.skill.md
- docs/0-13-0/tutorials/incremental-adoption/overview.mdx.skill.md
- docs/0-13-0/how-to/build-a-realtime-todo-app.mdx.skill.md
- docs/0-13-0/tutorials/build-an-agent/overview.mdx
- docs/0-13-0/tutorials/build-an-agent/overview.mdx.skill.md
- docs/0-13-0/sdk-reference/node-sdk.mdx
- docs/0-13-0/tutorials/incremental-adoption/overview.mdx
- docs/0-13-0/index.mdx
- docs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdx
- docs/0-13-0/changelog/0-11-0/migrated-examples.mdx
- docs/0-13-0/install.mdx
- docs/0-13-0/sdk-reference/rust-sdk.mdx
- docs/0-13-0/tutorials/build-an-agent/memory-and-state.mdx
- docs/0-13-0/using-iii/functions.mdx
- docs/0-13-0/patterns/reactive-state-pattern.mdx
- docs/0-13-0/tutorials/reactive-crud/realtime-subscriptions.mdx
- docs/0-13-0/understanding-iii/channels.mdx
- docs/0-13-0/tutorials/build-an-agent/define-tools.mdx
- docs/0-13-0/creating-workers/workers.mdx
- docs/0-13-0/using-iii/channels.mdx.skill.md
- docs/0-13-0/how-to/build-a-realtime-todo-app.mdx
- docs/0-13-0/creating-workers/functions.mdx
- docs/0-13-0/using-iii/triggers.mdx
- docs/0-13-0/tutorials/build-an-agent/memory-and-state.mdx.skill.md
- docs/changelog/0-16-0/align-rust-register-function-with-signature.mdx
- docs/0-13-0/creating-workers/triggers.mdx
- docs/0-13-0/sdk-reference/engine-sdk.mdx
- docs/0-13-0/creating-workers/functions.mdx.skill.md
- docs/0-13-0/using-iii/cli.mdx
- docs/0-13-0/using-iii/deployment.mdx
- docs/0-13-0/understanding-iii/workers.mdx
- docs/0-13-0/changelog/0-11-0/migrating-from-motia-js.mdx
- docs/0-13-0/creating-workers/triggers.mdx.skill.md
- docs/0-13-0/using-iii/engine.mdx
- docs/0-13-0/changelog/0-11-0/migrating-from-motia-py.mdx
- docs/0-13-0/changelog/index.mdx
- docs/0-13-0/using-iii/console.mdx
🚧 Files skipped from review as they are similar to previous changes (5)
- docs/0-13-0/using-iii/channels.mdx
- docs/0-13-0/sdk-reference/python-sdk.mdx
- docs/0-13-0/sdk-reference/browser-sdk.mdx
- docs/docs.json
- docs/0-13-0/creating-workers/workers-registry.mdx
| level, but the `service::name` form makes the Function's intent obvious to readers and avoids | ||
| collisions between unrelated Functions registered by different Workers. | ||
|
|
||
| {/* TODO: Confirm if we still have restricted string prefixes */} |
Contributor
There was a problem hiding this comment.
Remove or resolve the in-page TODO before publishing.
This unresolved TODO leaves the guidance in an incomplete state for the archived docs snapshot. Please either confirm and document the restriction, or remove this note before merge.
As per coding guidelines: docs/** should follow the documentation workflow and consistency standards for published docs.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/0-13-0/understanding-iii/functions.mdx` at line 30, Resolve the in-page
TODO comment "/* TODO: Confirm if we still have restricted string prefixes */"
in functions.mdx: either remove the TODO and its comment if there is no
restriction, or replace it with a short definitive statement documenting the
restriction (what the restricted string prefixes are, when they apply, and a
short example or link to the authoritative policy), and ensure the updated text
follows the docs style and consistency guidelines before merging.
Contributor
Author
There was a problem hiding this comment.
The 0.13 docs should not reflect the docs from 0.16
Contributor
There was a problem hiding this comment.
Understood, @guibeira — the docs/0-13-0/ tree is an immutable archive snapshot of the 0.13.x state, and unresolved TODOs or in-progress notes there are acceptable as they reflect the docs at that point in time. My comment was misguided. The 0.16 active docs are the right target for keeping things clean and resolved.
(ᴗ˳ᴗ)
✏️ Learnings added
Learnt from: guibeira
Repo: iii-hq/iii PR: 1711
File: docs/0-13-0/understanding-iii/functions.mdx:30-30
Timestamp: 2026-05-29T18:27:44.486Z
Learning: In the iii-hq/iii repository, `docs/0-13-0/` (and any similar version-prefixed snapshot directories, e.g., `docs/0-11-0/`) are immutable archived snapshots of the documentation at the time of that release. Do not flag unresolved TODOs, incomplete content, or style issues in these archived snapshot directories during PR review — they intentionally preserve the state of the docs as they existed at that version and should not be updated to reflect later versions (e.g., 0.16).
Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.
🧠 Learnings used
Learnt from: guibeira
Repo: iii-hq/iii PR: 1313
File: docs/content/how-to/create-ephemeral-worker.mdx:172-172
Timestamp: 2026-03-16T11:41:40.222Z
Learning: Guideline: In Rust SDK documentation, replace shutdown() with shutdown_async().await to ensure telemetry is flushed before process exit. Update all relevant Rust examples and prose in docs/content/how-to/create-ephemeral-worker.mdx and other Rust SDK docs to use shutdown_async().await. Actions: search for shutdown() usages in Markdown docs under docs/ and update to shutdown_async().await, verify the async call is awaited, adjust any surrounding async context, and run any available automated checks (lint/CI/docs build) to ensure consistency and correctness.
Learnt from: guibeira
Repo: iii-hq/iii PR: 1313
File: docs/content/modules/module-stream.mdx:349-351
Timestamp: 2026-03-16T11:50:21.574Z
Learning: In docs under the iii-hq/iii repository, ensure that any example constructing RegisterTriggerInput uses exactly three required fields: trigger_type: String, function_id: String, config: Value; do not use Default::default(). Update all Rust doc examples to use: RegisterTriggerInput { trigger_type: "...".into(), function_id: "...".into(), config: json!({ ... }) } and avoid any 'type_:' typos. Specifically fix occurrences of type_ instead of trigger_type in the following MDX docs: module-stream.mdx, architecture/trigger-types.mdx, advanced/sdk-implementation.mdx, examples/conditions.mdx, examples/cron.mdx, examples/hello-world.mdx, and examples/observability.mdx.
Learnt from: guibeira
Repo: iii-hq/iii PR: 1313
File: docs/content/modules/module-stream.mdx:349-351
Timestamp: 2026-03-16T11:50:21.574Z
Learning: In the iii-hq/iii repository Rust SDK docs, when documenting RegisterFunctionMessage and only the id is needed, instantiate via RegisterFunctionMessage::new("id"). Do not rely on Default. If you need to set optional fields, use the full struct literal with explicit None values (e.g., request_format: None, response_format: None, metadata: None, invocation: None). Apply this pattern in all relevant doc examples; avoid using ..Default::default().
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (2)
docs/0-13-0/sdk-reference/node-sdk.mdx.skill.md (1)
124-126:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix
invocation_stoppedmeaning to match the engine protocol docs.This mapping is still inconsistent:
invocation_stoppedshould describe worker disconnect/cancel mid-flight, while timeout isTIMEOUT.As per coding guidelines, "**/*.md*: Ensure all references to primitives reflect those defined in docs/**."Suggested wording
-Common `code` values come from the engine: `invocation_failed` (handler threw), `invocation_stopped` -(engine timeout), `function_not_found`, `function_not_invokable`, `TIMEOUT` (client-side timeout), -`FORBIDDEN` (RBAC denial). +Common `code` values come from the engine: `invocation_failed` (handler threw), `invocation_stopped` +(owning worker disconnected mid-flight), `function_not_found`, `function_not_invokable`, +`TIMEOUT` (client-side timeout), `FORBIDDEN` (RBAC denial).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/0-13-0/sdk-reference/node-sdk.mdx.skill.md` around lines 124 - 126, Update the description for the `invocation_stopped` code to match engine protocol docs: change its meaning to indicate a worker disconnect or cancellation mid-flight (worker-initiated stop), and ensure `TIMEOUT` remains the code used for timeouts; edit the sentence listing common `code` values (the line containing `invocation_failed`, `invocation_stopped`, `function_not_found`, `function_not_invokable`, `TIMEOUT`, `FORBIDDEN`) so `invocation_stopped` explicitly states "worker disconnect/cancel mid-flight" and `TIMEOUT` is described as the client-side or execution timeout.docs/0-13-0/using-iii/cli.mdx.skill.md (1)
41-41:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFix the in-page anchor target for the update section.
The link at Line 41 points to
#updating-iii-itself, but the section heading at Line 55 resolves to#updating-iii, so this fragment is broken in the current page.Suggested patch
-| `iii update` | Update iii and its managed binaries. See [Updating iii itself](`#updating-iii-itself`). | +| `iii update` | Update iii and its managed binaries. See [Updating iii](`#updating-iii`). |Also applies to: 55-55
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/0-13-0/using-iii/cli.mdx.skill.md` at line 41, The in-page anchor target for the "update" row is incorrect: the table link uses the fragment `#updating-iii-itself` while the actual section heading is `#updating-iii`; update the fragment in the table (the `iii update` row) to `#updating-iii` (or alternatively rename the heading to `Updating iii itself` matching `#updating-iii-itself`) so the anchor resolves correctly; look for the `iii update` table entry and the `Updating iii` heading to apply the fix.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/0-13-0/quickstart.mdx`:
- Around line 28-34: The three unlabeled fenced code blocks in quickstart.mdx
(the directory tree and two console output blocks) trigger MD040; update each
triple-backtick fence to include a language tag (e.g., change ``` to ```text for
the tree and console outputs, or ```bash if preferred) so the blocks are
explicitly marked; locate the blocks in docs/0-13-0/quickstart.mdx (around the
blocks shown and the other occurrences referenced) and replace the opening
fences accordingly while leaving the inner content unchanged.
In `@docs/0-13-0/understanding-iii/index.mdx`:
- Around line 115-120: The HTTP trigger flow text is using the wrong Function
ID: update the sentence that says the HTTP trigger targets `math::add` so it
instead references the correct Function ID `math::add_two_numbers` to match the
`POST /math/add-two-numbers` endpoint and the routing to `caller-worker`
(symbols: `iii-http`, `POST /math/add-two-numbers`, Trigger, Engine,
`caller-worker`, `math::add` -> change to `math::add_two_numbers`).
---
Duplicate comments:
In `@docs/0-13-0/sdk-reference/node-sdk.mdx.skill.md`:
- Around line 124-126: Update the description for the `invocation_stopped` code
to match engine protocol docs: change its meaning to indicate a worker
disconnect or cancellation mid-flight (worker-initiated stop), and ensure
`TIMEOUT` remains the code used for timeouts; edit the sentence listing common
`code` values (the line containing `invocation_failed`, `invocation_stopped`,
`function_not_found`, `function_not_invokable`, `TIMEOUT`, `FORBIDDEN`) so
`invocation_stopped` explicitly states "worker disconnect/cancel mid-flight" and
`TIMEOUT` is described as the client-side or execution timeout.
In `@docs/0-13-0/using-iii/cli.mdx.skill.md`:
- Line 41: The in-page anchor target for the "update" row is incorrect: the
table link uses the fragment `#updating-iii-itself` while the actual section
heading is `#updating-iii`; update the fragment in the table (the `iii update`
row) to `#updating-iii` (or alternatively rename the heading to `Updating iii
itself` matching `#updating-iii-itself`) so the anchor resolves correctly; look
for the `iii update` table entry and the `Updating iii` heading to apply the
fix.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 833142fb-edda-49dd-9e98-bf3f9a946516
⛔ Files ignored due to path filters (3)
docs/0-13-0/assets/favicon.svgis excluded by!**/*.svgdocs/0-13-0/assets/iii-black.svgis excluded by!**/*.svgdocs/0-13-0/assets/iii-white.svgis excluded by!**/*.svg
📒 Files selected for processing (92)
docs/0-13-0/changelog/0-11-0/everything-is-a-worker.mdxdocs/0-13-0/changelog/0-11-0/migrated-examples.mdxdocs/0-13-0/changelog/0-11-0/migrating-from-motia-js.mdxdocs/0-13-0/changelog/0-11-0/migrating-from-motia-py.mdxdocs/0-13-0/changelog/index.mdxdocs/0-13-0/creating-workers/functions.mdxdocs/0-13-0/creating-workers/functions.mdx.skill.mddocs/0-13-0/creating-workers/triggers.mdxdocs/0-13-0/creating-workers/triggers.mdx.skill.mddocs/0-13-0/creating-workers/workers-registry.mdxdocs/0-13-0/creating-workers/workers-registry.mdx.skill.mddocs/0-13-0/creating-workers/workers.mdxdocs/0-13-0/creating-workers/workers.mdx.skill.mddocs/0-13-0/how-to/build-a-realtime-todo-app.mdxdocs/0-13-0/how-to/build-a-realtime-todo-app.mdx.skill.mddocs/0-13-0/index.mdxdocs/0-13-0/index.mdx.skill.mddocs/0-13-0/install.mdxdocs/0-13-0/install.mdx.skill.mddocs/0-13-0/patterns/adapter-pattern.mdxdocs/0-13-0/patterns/adapter-pattern.mdx.skill.mddocs/0-13-0/patterns/reactive-state-pattern.mdxdocs/0-13-0/patterns/reactive-state-pattern.mdx.skill.mddocs/0-13-0/quickstart.mdxdocs/0-13-0/quickstart.mdx.skill.mddocs/0-13-0/sdk-reference/browser-sdk.mdxdocs/0-13-0/sdk-reference/browser-sdk.mdx.skill.mddocs/0-13-0/sdk-reference/engine-sdk.mdxdocs/0-13-0/sdk-reference/engine-sdk.mdx.skill.mddocs/0-13-0/sdk-reference/node-sdk.mdxdocs/0-13-0/sdk-reference/node-sdk.mdx.skill.mddocs/0-13-0/sdk-reference/python-sdk.mdxdocs/0-13-0/sdk-reference/python-sdk.mdx.skill.mddocs/0-13-0/sdk-reference/rust-sdk.mdxdocs/0-13-0/sdk-reference/rust-sdk.mdx.skill.mddocs/0-13-0/tutorials/build-an-agent/define-tools.mdxdocs/0-13-0/tutorials/build-an-agent/define-tools.mdx.skill.mddocs/0-13-0/tutorials/build-an-agent/memory-and-state.mdxdocs/0-13-0/tutorials/build-an-agent/memory-and-state.mdx.skill.mddocs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdxdocs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdx.skill.mddocs/0-13-0/tutorials/build-an-agent/overview.mdxdocs/0-13-0/tutorials/build-an-agent/overview.mdx.skill.mddocs/0-13-0/tutorials/incremental-adoption/migrate-persistence.mdxdocs/0-13-0/tutorials/incremental-adoption/migrate-persistence.mdx.skill.mddocs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdxdocs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdx.skill.mddocs/0-13-0/tutorials/incremental-adoption/overview.mdxdocs/0-13-0/tutorials/incremental-adoption/overview.mdx.skill.mddocs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdxdocs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdx.skill.mddocs/0-13-0/tutorials/reactive-crud/crud-endpoints.mdxdocs/0-13-0/tutorials/reactive-crud/crud-endpoints.mdx.skill.mddocs/0-13-0/tutorials/reactive-crud/model-and-store.mdxdocs/0-13-0/tutorials/reactive-crud/model-and-store.mdx.skill.mddocs/0-13-0/tutorials/reactive-crud/overview.mdxdocs/0-13-0/tutorials/reactive-crud/overview.mdx.skill.mddocs/0-13-0/tutorials/reactive-crud/realtime-subscriptions.mdxdocs/0-13-0/tutorials/reactive-crud/realtime-subscriptions.mdx.skill.mddocs/0-13-0/understanding-iii/channels.mdxdocs/0-13-0/understanding-iii/channels.mdx.skill.mddocs/0-13-0/understanding-iii/engine.mdxdocs/0-13-0/understanding-iii/engine.mdx.skill.mddocs/0-13-0/understanding-iii/functions.mdxdocs/0-13-0/understanding-iii/functions.mdx.skill.mddocs/0-13-0/understanding-iii/index.mdxdocs/0-13-0/understanding-iii/index.mdx.skill.mddocs/0-13-0/understanding-iii/triggers.mdxdocs/0-13-0/understanding-iii/triggers.mdx.skill.mddocs/0-13-0/understanding-iii/workers.mdxdocs/0-13-0/understanding-iii/workers.mdx.skill.mddocs/0-13-0/using-iii/channels.mdxdocs/0-13-0/using-iii/channels.mdx.skill.mddocs/0-13-0/using-iii/cli.mdxdocs/0-13-0/using-iii/cli.mdx.skill.mddocs/0-13-0/using-iii/console.mdxdocs/0-13-0/using-iii/console.mdx.skill.mddocs/0-13-0/using-iii/deployment.mdxdocs/0-13-0/using-iii/deployment.mdx.skill.mddocs/0-13-0/using-iii/engine.mdxdocs/0-13-0/using-iii/engine.mdx.skill.mddocs/0-13-0/using-iii/functions.mdxdocs/0-13-0/using-iii/functions.mdx.skill.mddocs/0-13-0/using-iii/triggers.mdxdocs/0-13-0/using-iii/triggers.mdx.skill.mddocs/0-13-0/using-iii/workers-registry.mdxdocs/0-13-0/using-iii/workers-registry.mdx.skill.mddocs/0-13-0/using-iii/workers.mdxdocs/0-13-0/using-iii/workers.mdx.skill.mddocs/changelog/0-16-0/align-rust-register-function-with-signature.mdxdocs/changelog/index.mdxdocs/docs.json
✅ Files skipped from review due to trivial changes (48)
- docs/0-13-0/tutorials/build-an-agent/memory-and-state.mdx.skill.md
- docs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdx
- docs/0-13-0/tutorials/reactive-crud/realtime-subscriptions.mdx.skill.md
- docs/0-13-0/tutorials/build-an-agent/overview.mdx.skill.md
- docs/0-13-0/tutorials/reactive-crud/model-and-store.mdx
- docs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdx
- docs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdx
- docs/0-13-0/tutorials/build-an-agent/orchestration-loop.mdx.skill.md
- docs/0-13-0/tutorials/reactive-crud/crud-endpoints.mdx.skill.md
- docs/0-13-0/tutorials/incremental-adoption/migrate-persistence.mdx.skill.md
- docs/0-13-0/how-to/build-a-realtime-todo-app.mdx.skill.md
- docs/0-13-0/tutorials/build-an-agent/define-tools.mdx.skill.md
- docs/0-13-0/tutorials/build-an-agent/define-tools.mdx
- docs/0-13-0/changelog/0-11-0/migrated-examples.mdx
- docs/0-13-0/tutorials/build-an-agent/memory-and-state.mdx
- docs/0-13-0/tutorials/incremental-adoption/offload-to-queue.mdx.skill.md
- docs/0-13-0/using-iii/functions.mdx
- docs/0-13-0/using-iii/deployment.mdx
- docs/0-13-0/tutorials/reactive-crud/realtime-subscriptions.mdx
- docs/0-13-0/creating-workers/functions.mdx
- docs/changelog/0-16-0/align-rust-register-function-with-signature.mdx
- docs/0-13-0/tutorials/reactive-crud/overview.mdx
- docs/0-13-0/sdk-reference/node-sdk.mdx
- docs/0-13-0/tutorials/reactive-crud/crud-endpoints.mdx
- docs/0-13-0/tutorials/reactive-crud/model-and-store.mdx.skill.md
- docs/0-13-0/using-iii/cli.mdx
- docs/0-13-0/patterns/reactive-state-pattern.mdx
- docs/0-13-0/understanding-iii/channels.mdx.skill.md
- docs/0-13-0/tutorials/incremental-adoption/migrate-persistence.mdx
- docs/0-13-0/creating-workers/triggers.mdx.skill.md
- docs/0-13-0/tutorials/build-an-agent/overview.mdx
- docs/0-13-0/using-iii/triggers.mdx
- docs/0-13-0/how-to/build-a-realtime-todo-app.mdx
- docs/0-13-0/install.mdx
- docs/0-13-0/creating-workers/workers.mdx
- docs/0-13-0/changelog/0-11-0/migrating-from-motia-js.mdx
- docs/0-13-0/sdk-reference/engine-sdk.mdx
- docs/0-13-0/using-iii/channels.mdx.skill.md
- docs/0-13-0/using-iii/console.mdx
- docs/0-13-0/index.mdx
- docs/0-13-0/sdk-reference/python-sdk.mdx
- docs/0-13-0/creating-workers/functions.mdx.skill.md
- docs/0-13-0/creating-workers/workers-registry.mdx
- docs/0-13-0/changelog/0-11-0/migrating-from-motia-py.mdx
- docs/0-13-0/changelog/index.mdx
- docs/0-13-0/creating-workers/triggers.mdx
- docs/0-13-0/using-iii/channels.mdx
- docs/0-13-0/sdk-reference/browser-sdk.mdx
🚧 Files skipped from review as they are similar to previous changes (8)
- docs/0-13-0/tutorials/incremental-adoption/overview.mdx
- docs/0-13-0/tutorials/incremental-adoption/wrap-existing-api.mdx.skill.md
- docs/0-13-0/tutorials/reactive-crud/overview.mdx.skill.md
- docs/0-13-0/sdk-reference/rust-sdk.mdx
- docs/0-13-0/understanding-iii/channels.mdx
- docs/0-13-0/tutorials/incremental-adoption/overview.mdx.skill.md
- docs/0-13-0/using-iii/engine.mdx
- docs/docs.json
anthonyiscoding
approved these changes
May 29, 2026
Mirrors the 0.13 archive pattern: copy current docs to docs/0-13-0/, mark 0.14.x as the new "Next" version, register the 0.13.x archive in docs.json, and seed an empty 0.14.0 changelog entry.
Fills the empty 0.14.0 entry with the cross-language extraction: Logger, OtelConfig, ReconnectionConfig, and the full OTel surface move to the new iii-observability packages on npm, PyPI, and crates.io. Notes the two new symbols (flush_otel/flushOtel and execute_traced_request/executeTracedRequest) and includes per- language migration snippets.
…kills Move the doc/skill updates that were carried on align-rust-sdk into this branch so they ship alongside the observability work. - Regenerate sdk-node / sdk-python / sdk-rust API references for the new Rust register_function shape (`register_function(id, RegisterFunction::…)`, 3 constructors, IIIError handler errors). - Add the migration changelog entry under docs/changelog/0-11-0/. - Update docs/0-11-0/scripts/generate-api-docs.mts + parsers/parse-rustdoc.mts to scan FunctionDoc descriptions/examples and allowlist RegisterFunctionOptions in the rustdoc parser. - Refresh skills/iii-rust-sdk/SKILL.md and skills/references/http-invoked-functions.rs to reflect the new Rust call shape.
… to index - Move docs/changelog/0-11-0/align-rust-register-function-with-signature.mdx to docs/changelog/0-14-0/. The change ships in 0.14, not 0.11. - Add a 0.14.0 entry in docs/changelog/index.mdx linking to the migration page. - Register the new page under the "Changelog" tab in docs/docs.json.
- sdk-node.mdx: switch cron trigger examples from `schedule` to the engine-standard `expression` key. - sdk-rust.mdx: remove duplicate `RegisterFunction::new_async` from the constructor list; align the register_trigger example with the documented 3-field RegisterTriggerInput shape (drop metadata: None).
Reorder navigation versions newest-first (0.16.x → 0.10.x), retag 0.16.x as Latest, and relabel the 0.13.x changelog group to 0.11.0 to match the detail pages it points to.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Snapshot current docs to
docs/0-13-0/as the 0.13 archive.Promote the active version to
0.16.xindocs/docs.jsonand register the0.13.xarchive navigation.Seed the
0.16.0entry indocs/changelog/index.mdx.Changes from:
feat/iii-observability #1678
refactor(rust-sdk)!: simplify register_function — 3 constructors + IIIError handlers #1578
Supersedes #1686 (rebumped Next version 0.14 → 0.16).
Test plan
0.16.x(Next) renders root docs unchanged.0.13.xversion selector renders archived snapshot atdocs/0-13-0/*.Summary by CodeRabbit
Documentation
Migration & Examples
Breaking Changes