Treating Backstage as the platform interfaceInterface versus mechanismWhat a developer should seeWhat the platform team should ownWhy Backstage arrives lastThe pre-built imageBackstage data in the corrected workshop buildHands-on exercise: review the portal contractExpected resultTroubleshooting the interface boundaryConnecting the catalog, TechDocs, and live Argo CD stateRegistering a componentTechDocs as docs-as-codeThe Argo CD integrationQuerying the catalog APIExpected outputQuerying the Argo CD proxyCredential boundariesCatalog eventual consistencyHands-on lab: verify catalog and live delivery statePrerequisitesFiles usedRun the Phase 3 integration testsTroubleshooting tipsAdding workflows, events, progressive delivery, and autoscalingArgo WorkflowsArgo EventsArgo RolloutsKEDAHands-on lab: verify extension APIs1.Check the CRDs2.Run the full phase gateTroubleshooting tipsDiagnosing portal image, configuration, and credential failuresThe diagnostic layersFailure 1: doubled registry pathFailure 2: the file exists but the process cannot reach itFailure 3: production configuration never loadedFailure 4: secret and credential driftFailure 5: database secret and storage assumptionsFailure 6: eventually consistent catalog stateHands-on lab: diagnose a failed Backstage deployment1.Inspect Argo CD and the rendered workload2.Inspect events and logsExpected evidence3.Test the outcome after the repairTroubleshooting checklistProduction reality checkSummary