v0.6.0

Config-declared pipelines

New capstead.pipelines property lets applications describe a multi-step workflow purely in configuration — no client code changes, no schema changes. Runs are assembled at read time from already-recorded root executions (ordered step matching with a bounded max-gap).

• New /actuator/capabilitypipelines endpoint: pipeline scorecards + per-run drill-down (wall time, tokens, cost, per-step breakdown)
• Dashboard now shows a Pipelines section with run detail view
• PipelineDefinition / PipelineRun / PipelineScorecard / PipelineAssembler in capstead-core

Fixes

• Registry and metadata-resolver beans are now static ROLE_INFRASTRUCTURE beans, silencing the 'not eligible for getting processed by all BeanPostProcessors' startup warning in client apps.

Example:

capstead:
  pipelines:
    - name: Generate Lesson Pipeline
      domain: EngineerPrep
      owner: Content Team
      max-gap: 5m
      steps:
        - Author Lesson
        - Write Episode
        - Synthesize Episode Audio
        - Generate Assessments
        - Generate GitHub Repo