Public docs for the current Forge surface

Start with the current public workflow: sign in, generate, review validation notes, and download the package for build validation in your environment.

Concrete examples of the shipped `itk-batch` scope: realistic requests, selected patterns, output shape, and what still needs engineering review.

Current authenticated API routes for artifacts, generations, API keys, and billing actions. Covers the live web/API surface without implying a broader SDK platform.

Practical trust boundaries: what Forge receives, what it does not access, how prompts and output are handled, and where customer responsibility starts.

Short factual answers about shipped scope, authentication, validation, Teamcenter targeting, and current product boundaries.