HTTP app contract¶
A Forge app is a process that starts from the command in its manifest and serves the routes its capabilities declare.
Runtime requirements¶
| Requirement | Contract |
|---|---|
| Startup | capabilities[].startup.command must start the server without an interactive prompt. |
| Route | http and scheduler capabilities require capabilities[].route. |
| Runtime | capabilities[].runtime names the runtime Forge uses, such as static. |
| Port | The public v1 manifest has no port field. The process must listen where its startup command and runtime expect; the starter binds port 8000 with python3 -m http.server 8000. |
| Readiness | The public v1 manifest has no readiness-probe field. Do not assume an injected port variable or a specific probe path. |
| Errors | Return an HTTP error with a useful body when a request cannot succeed. |
The port and readiness details are not part of the documented 0.9.4 public contract; treat them as unknown rather than guessing a value.
Local proof¶
Start the app with the manifest's command, request its declared route, and record the command, exit status and HTTP responses with the manifest and commit used for the run.
A local response proves the app behaves on that machine. It does not prove hosted availability or Forge repository access.
Source boundary¶
Forge deploys committed source. The default request uses the repository
origin and committed HEAD; automation may select only repository, ref or
commit. Uncommitted files are never uploaded.