docs(post-scripts): use post-script as the one term for hooks

Add the post-script row to the ste-writing terminology contract and
replace hook/postscript/post-download script across docs and docstrings.
This commit is contained in:
imSp4rky
2026-08-25 19:57:41 -06:00
parent a13081b14f
commit b94f338619
11 changed files with 57 additions and 57 deletions
+2 -2
View File
@@ -425,9 +425,9 @@ Make a download job. It requires `service` and `title_id`. Every other field is
!!! danger "Rejected parameters"
`postscript`, `post_script` and `post_scripts` are never accepted. A body containing any
of them gets `400 INVALID_PARAMETERS`, because a command string that arrives from
an HTTP caller would be remote code execution. You configure post-download hooks only in
an HTTP caller would be remote code execution. You configure post-scripts only in
`unshackle.yaml`, where they still operate for API jobs. See
[Post-download scripts](../../reference/configuration/post-scripts.md).
[Post-scripts](../../reference/configuration/post-scripts.md).
!!! warning "Gated parameters (developer)"
The server accepts a few keys, but permits them only when the server config opts in. Otherwise the server rejects the request with `403 FORBIDDEN`: