docs(fork): carried files for the line's first CI wiring

[teemow]

Replaces #329, rebuilt once off the current giantswarm (the ruleset's strict base; the line is rebase-merged, so a fresh branch instead of a merged base). Its sibling #330 landed as #342; #329 stayed mergeable after it, as after #333.

Problem

Three ci(fork) commits on top of the pin — the consumed branch is giantswarm, a tag is a release of the line, vX.Y.Z-gs.N, the e2e cluster runs the Substrate the charts depend on — have no row in the carried ledger (#326 lists them as unrecorded).

Proposed solution

One file each under fork/carried/, from the commits' own messages; scripts/fork/carried.sh --check keys them to the commits.

Acceptance criteria

• fork-ledger green.
• The proof for Carried pull requests conflict on FORK.md's last table rows #324: this pull request and docs(fork): carried files for the sync's App push and Renovate off #330 each add files to fork/carried/; after one merges, the other still shows mergeable on GitHub.

[teemow]

Replaced by #347: this branch fell behind giantswarm when #345 merged (the ruleset's strict base), and the line takes a fresh branch, not a merged base. Closed by the agent working #324.