Repository navigation
Document local-only API guardrails - #74
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 32a8c9a478
ℹ️ 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".
|
|
||
| ## Route-level implications | ||
|
|
||
| Read-only report and approval inspection routes can disclose project metadata. Mutating approval routes can apply approved patches, move approval artifacts, and create Git commits. Both categories require an authorization boundary before remote use. |
There was a problem hiding this comment.
The current create_app() surface has only POST /commands and read-only approval list/detail endpoints; it exposes no route that approves a request, applies a patch, moves approval artifacts, or creates a Git commit. In the current API context, this statement therefore misdocuments the available behavior and threat model; either describe the actual /commands mutations (approval/activity record creation) or defer these implications until approval mutation routes exist.
Useful? React with 👍 / 👎.
Summary
Documents the current local-only API trust boundary.
Changes
Closes #65.
Validation
Docs-only change; CI should run on this PR.