Troubleshooting

Start with the repository origin, committed source, manifest, local HTTP result, and deployment result. Keep the investigation on the supported surface.

Local setup fails

Use the approved Aegis distribution and repeat local setup. This portal does not provide a second login, endpoint, or token path.

Repository access fails

Wait for deployment to request repository access, then inspect the Forge App authorization outcome. Keep ordinary source control under the operator's GitHub authority.

Source or configuration fails

Inspect the origin, selected commit, manifest, and source diff. Commit the reviewed files before requesting deployment.

Build or runtime fails

Read the build output, startup command, port binding, and readiness route. Reproduce the HTTP contract locally before requesting another deployment.

Derived context looks wrong

Do not add a selector. Environment, tenant, account, installation, and app identity come from authorization and repository context.

Deployment result is unclear

Keep the result with the repository and commit. Classify the failure stage and preserve the non-secret proof packet.

Scope

Do not invent hosted behavior. Read Deploy and Support for the supported boundaries.