Question
How does optional Attach use standard OAuth against one Organization's canonical MCP resource, establish an organization-scoped Client Principal, discover and validate a Project Configuration, upload its bounded configuration bundle into the authoritative state model, obtain, renew, switch, and release a Project Context ID, add that context to stateless remote MCP requests, proxy the resulting surface over local stdio, retain local OAuth state, authorize project-defined sources and Secret Grants, and report reload, expiry, rejection, and transport failures without restoring legacy Remote Profiles, Project Binding, or arbitrary file synchronization?
Question
How does optional Attach use standard OAuth against one Organization's canonical MCP resource, establish an organization-scoped Client Principal, discover and validate a Project Configuration, upload its bounded configuration bundle into the authoritative state model, obtain, renew, switch, and release a Project Context ID, add that context to stateless remote MCP requests, proxy the resulting surface over local stdio, retain local OAuth state, authorize project-defined sources and Secret Grants, and report reload, expiry, rejection, and transport failures without restoring legacy Remote Profiles, Project Binding, or arbitrary file synchronization?