luigidemasi opened a new pull request, #121: URL: https://github.com/apache/camel-kit/pull/121
Third step of the documentation migration to camel.apache.org (follows #116 and #120): the nine **Pipeline** pages of the Antora component are written. | Page | Content | |------|---------| | `pipeline.adoc` | The four stages, the single approval gate, pipeline files and standalone stages, the six Iron Laws, the internal skills | | `camel-start.adoc` | Routing order, skill tiers, when not to use each skill | | `camel-brainstorm.adoc` | Chained, standalone and amend modes, the adaptive interview, catalog verification, the design specification sections, common patterns | | `camel-plan.adoc` | Input and scope boundaries, how the plan is built, the plan format with the `yaml plan-metadata` block, waves, the two-stage review specification, handoff and reuse | | `camel-execute.adoc` | Wave analysis, plan ingress validation, environment probe, catalog research, the per-task loop (adversarial, spec and quality reviews), cross-cutting review, verification and report, generated artifacts per runtime, execution model per agent | | `camel-validate.adoc` | Chained, pipeline-scoped and project-scoped modes, the checks, the strictness invariant, the report | | `verification.adoc` | The internal `camel-verify` loop: environment check, build or startup smoke, tests, fix routing and promotion, report, verify log | | `camel-debug.adoc` | The five steps, what authorizes a repair, the summary | | `ship.adoc` | Requirements, command and options, oversight, stages and the Stamp, run state and publication, the shared native-subagent contract with a per-host table (merges `docs/ship-native.md`, `ship-claude.md`, `ship-copilot.md`, `ship-codex.md`), entry points per agent, examples, comparison with the manual pipeline | The text is rewritten from the standalone website and the repository documentation into the Camel documentation register. Every claim was checked against the skill manifests and guides, `shared/iron-laws.md`, the workflow manifest, `docs/commands.md`, the Ship documents and the 0.4.1 release tag. As in #120, the pages follow the development branch and mark features added after the 0.4.1 release as development snapshot only (here: Codex native Ship and the direct migration mode). ### Local build Antora 3.2 with the Camel website UI bundle at `failure_level: warn`, with stub `manual` and `components` sources for the external xrefs: 27 pages, no warnings, no absolute `camel.apache.org` links in the generated HTML. Desktop and mobile renders checked in headless Chrome. `docs/antora.yml` gains `pi-version`, `pi-previous-version` and `node-version` attributes (kept in step with `distribution.properties`) so the Ship page carries no hardcoded worker versions. No other change outside `docs/modules/`; the existing `docs/*.md` files are untouched. Next: the Architecture group. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
