FE-1456: Add a usage manual for the Python bindings - #9266
Open
kube wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
kube
marked this pull request as ready for review
August 21, 2026 00:14
PR SummaryLow Risk Overview The CLI manual’s “Driving the CLI from Python” section no longer shows a raw Reviewed by Cursor Bugbot for commit 1d6951e. Bugbot is set up for automated code reviews on this repo. Configure here. |
kube
force-pushed
the
cf/fe-1456-arch-docs-usage-manual-for-the-python-bindings
branch
from
August 21, 2026 08:27
7dc0fdf to
09bbe8e
Compare
kube
force-pushed
the
cf/fe-1456-arch-docs-usage-manual-for-the-python-bindings
branch
from
August 21, 2026 09:30
09bbe8e to
2c2733c
Compare
This was referenced Aug 21, 2026
kube
force-pushed
the
cf/fe-1456-arch-docs-usage-manual-for-the-python-bindings
branch
from
August 21, 2026 09:57
2c2733c to
09ffabe
Compare
kube
force-pushed
the
cf/fe-1456-arch-docs-usage-manual-for-the-python-bindings
branch
from
August 21, 2026 12:07
09ffabe to
6980ae2
Compare
kube
force-pushed
the
cf/fe-1456-arch-docs-usage-manual-for-the-python-bindings
branch
from
August 21, 2026 14:52
6980ae2 to
079023d
Compare
kube
force-pushed
the
cf/fe-1456-arch-docs-usage-manual-for-the-python-bindings
branch
from
August 21, 2026 15:09
079023d to
a63f786
Compare
3 tasks
kube
force-pushed
the
cf/fe-1456-arch-docs-usage-manual-for-the-python-bindings
branch
from
August 21, 2026 15:20
a63f786 to
1aff1f6
Compare
kube
force-pushed
the
cf/fe-1456-arch-docs-usage-manual-for-the-python-bindings
branch
from
August 22, 2026 02:53
1aff1f6 to
1d6951e
Compare
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
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.
🌟 What is the purpose of this PR?
The CLI has a usage manual attached to its layer; the Python bindings had only a package README and docstrings. A caller who wants to drive Petrinaut from Python now has the same kind of guide in the docs site, attached to the
python-bindingslayer.In stack #9280, FE-1415 (#9265) sits below and FE-1457 (#9267) above.
🔗 Related links
🔍 What does this change?
One new authored page,
content/python-bindings/usage-manual.mdx, covers depending on the package, opening a session, run requests, optimization studies, errors, timeouts and shutdown, and an end-to-end example. It documents the Python layer and links to the CLI manual for the protocol detail rather than repeating it. In the other direction, the CLI manual's "Driving the CLI from Python" section replaces its hand-written subprocess wrapper with a short example that uses the bindings and links to the new page.Every symbol, default, and limit was checked against the source. Claims the package README implies that the manual corrects:
PetrinautRunErrorextendsRuntimeErrordirectly; onlyPetrinautProtocolErrorextendsPetrinautClientErrorseedsPerTrialPETRINAUT_CHILD_NODE_OPTIONSis forwarded, as the child'sNODE_OPTIONSReview fixes
PetrinautRunErrorand leaves the session usable, while a non-numeric one fails schema validation and raisesPetrinautProtocolError. It also states that requestparamsthat fail JSON serialization raisePetrinautClientErrorbefore anything is written, leaving the session running.close()may be called from another thread is restored.Pre-Merge Checklist 🚀
🚢 Has this modified a publishable library?
This PR:
📜 Does this require a change to the docs?
The changes in this PR:
🕸️ Does this require a change to the Turbo Graph?
The changes in this PR:
🛡 What tests cover this?
lint:arch-docsvalidatesattachToand everydoc:/layer:target, so a stale link fails the build.❓ How to test this?
turbo run dev --filter @apps/petrinaut-docs/architecture/python-bindings/usage-manual: it appears under thepython-bindingslayer beside its Overview, and its links to the CLI manual resolve.🐾 Next steps
The CLI manual keeps its em dashes, so the two pages differ in punctuation style. Bringing the older page in line with the prose rules is a separate cleanup.
🤖 Generated with Claude Code