feat: the reusable workflow composes the delivery step it promises (#3)

kapi-action reports; the PR (or branch push) is authored here, with an
optional deliver-token secret for consumers whose CI must react.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

feat: the reusable workflow composes the delivery step it promises (#3)

kapi-action reports; the PR (or branch push) is authored here, with an
optional deliver-token secret for consumers whose CI must react.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

docs: "convergence" becomes "the kapi loop" — catch-up framing (#1)

Align with neokapi/neokapi#1275: re-headline the concept as the kapi loop
(kapi up catches translations up and parks what needs a person); visible
report headings become "kapi up report". Machine contract unchanged:
outcome values (converged/parked), KAPI_* outputs, exit codes, and sticky
comment markers are untouched.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Reusable workflows: up (converge → PR + report) and gate (PR → ship g…

…ate)

The continuous-localization happy path as one uses: line each, composing
setup-kapi + kapi-action v1.3.0. up.yml converges and delivers a PR with
the convergence report; gate.yml fails PRs on unmet content quality gates
(exit 3) with a sticky report comment. kapi-version pins the 1.2.0
release candidate until stable ships.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NBoxTTZe69Nyssa6QSMxFK