on: repository_dispatch: types: workflow_dispatch: permissions: contents: write pull-requests: write

The token pipeline and the asset pipeline together cover the two highest-value extraction use cases. Chapter 10 applies the same structural thinking to component documentation: reading component names, descriptions, and variant properties from the API and generating documentation artifacts that stay in sync with the file. The question it answers is the same one the close icon failure raised , not "can we get the data?" but "does everyone know where the data came from and when it was last verified?"

The token pipeline and the asset pipeline together cover the two highest-value extraction use cases. Chapter 10 applies the same structural thinking to component documentation: reading component names, descriptions, and variant properties from the API and generating documentation artifacts that stay in sync with the file. The question it answers is the same one the close icon failure raised , not "can we get the data?" but "does everyone know where the data came from and when it was last verified?"