Clarify first-time Lumin connection and integration boundaries

[silverstein]

Outcome

Clarify first-time Lumin setup, signup and reconnect guidance in both plain text and structured output. Preserve separate document-send consent. Compare Lumin own local/hosted MCP offerings and document a provider-side attribution proposal without telemetry or duplicate cloud tools.

Changes

• Distinguish installation configuration from personal signup; keep account credentials out of chat.
• Close expired pending callbacks and guide canceled/expired/browser-failed connections without resending signing requests.
• Plain-text and structured guidance; exact source/share mirrors.
• Update discovery pin and regenerate the extraction fixture source binding for the shared output-schema bytes. Regeneration changes only3 metadata values, no extraction cases, truth or outputs.

Verification

Final exact SHA c220e2a. Independent source review GO including independent recomputation of fixture metadata. MSS MacBook Darwin arm64 Node22.23.2: 252/252 tests across11 focused/adjoining files with one worker, including Lumin tools/OAuth/mapper/transport/OpenAPI, schemas, source/share stdio discovery, packaging inventory, and affected extraction oracle/scorer/generation verification. Syntax, mirrors and diff checks pass.

Initial CI at88be08ad correctly rejected the stale shared-schema binding. Superseded7cf59001 CI was canceled to avoid repeating known failure. The generator was run onMac; all extraction results remained unchanged. No assertion was weakened or skipped.

Scope

Bead pjh8. Full first-time browser signup, shared production app/cross-workspace API allowance, hosted-MCP interoperability and per-app reporting remain provider-dependent in s002. No analytics, signup/account mutation, secrets, provider requests, signing invitations, host install or release. No sandbox/production default client ID added.