Skip to content

docs: clarify follow-up timing and use production API docs - #11

Merged
a7vinx merged 2 commits into
mainfrom
codex/pine-followup-guidance
Nov 6, 2026
Merged

a7vinx merged 2 commits into
mainfrom
codex/pine-followup-guidance

Conversation

@a7vinx

@a7vinx a7vinx commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Clarify when agents using REST should check Pine task progress. Use about 30 seconds when timing is unclear, reassess after each read, and schedule a single check near an explicit future continuation time when supported. Pause for user input and stop when the task finishes.

Point the OpenAPI and AsyncAPI documentation links to production and remove the temporary staging instructions. Business endpoints and Socket.IO live-update behavior remain unchanged.

Validation

  • Skill structure validation, local Markdown links, and diff whitespace checks passed.
  • Both production documentation URLs returned valid JSON with the expected OpenAPI and AsyncAPI versions.
  • Documentation only; no runtime changes or live task execution. Follow-up behavior has not been tested in Instinct.

@a7vinx
a7vinx merged commit 5c2c93a into main Nov 6, 2026
5 checks passed
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