[DOCS-02] Publish 30-minute authentication, tenant, device, and command quickstart

[jaavid]

Background

CoreLink is managed as one product across multiple implementation repositories. This work is the executable feature owned by developer-docs under EPIC-05.

Problem

The current repository state does not yet provide verified, release-ready evidence to publish a 30-minute authentication, tenant, device, and command quickstart.

Goal

Publish a 30-minute authentication, tenant, device, and command quickstart with observable acceptance evidence and no divergence from the product-level contract.

Parent

• Primary Product Epic: EPIC-05
• Backlog ID: DOCS-02

Scope

• Deliver the outcome stated in the title within the developer-docs implementation boundary.
• Reconcile the quickstart with the accepted authentication, tenant, device and command contract slice.
• Retain runnable evidence suitable for the Developer Platform product gate.

Out of Scope

• Creating a separate repository roadmap.
• Expanding into adjacent product domains without an accepted Product Epic or decision record.
• Treating documentation CI or a merged draft alone as Developer Platform acceptance.

Acceptance Criteria

• A new developer can complete the supported authentication, tenant, device and command journey from the documented quickstart in 30 minutes or less.
• Examples are versioned, runnable and aligned with supported contract versions.
• Expected, failure and recovery paths are documented where they materially affect the journey.
• Tenant isolation, authorization and sensitive-data handling are accurate.
• Links, examples and version claims pass documentation validation.
• Retained evidence is linked and EPIC-05 exit criteria are measurably advanced.

Technical Notes

Preserve canonical identifiers and provider-neutral public behavior. Do not advertise draft/scaffold capability as a supported stable release.

Dependencies and acceptance state

• Prerequisite completed: DOCS-01 is closed/completed and established the versioned documentation information architecture.
• Active product-gate prerequisite: an accepted contract slice for authentication, tenant, device and command behavior must be available and version-identifiable.
• Implementation evidence: PR Publish the CoreLink v1 30-minute quickstart #8 materially advances the quickstart and its Documentation CI has passed, but that does not by itself satisfy end-to-end Developer Platform acceptance.
• Blocks: EPIC-05 developer onboarding acceptance and downstream quickstart-derived examples.
• Current dependency state: See the CoreLink Product organization Project.

Planning Metadata

• Type: Feature
• Priority snapshot: P0
• Product milestone snapshot: Developer Platform
• Domain snapshots: docs, devex
• Area snapshot: documentation
• Complexity: L
• Created in status: Triage
• Current status and DRI: See the CoreLink Product organization Project.
• Intended repository labels: type:feature

Definition of Done

• Acceptance criteria demonstrated.
• Runnable quickstart evidence is retained and linked.
• Contract/version claims are reconciled.
• Security and tenant boundaries are reviewed.
• Documentation validation passes on the accepted revision.
• Related examples and release/maturity notes are updated.
• Pull request(s) are merged and linked.