Regenerate the overview apps after the merge instead of blocking the PR

[oblomov-dev]

Summary

The overview catalogs are generated from the folder tree and the class descriptions, so a stale catalog says nothing about the quality of a change — it only forced a mechanical follow-up commit before a branch could be merged. generate_overview_apps now runs after the merge instead of on the pull request, so a branch that adds or moves samples can be merged as is and standard heals itself.

This also fixes the current red standard: #701 was merged without the catalog update, so the workflow has been failing on standard since (runs for #701 and #703).

Changes

generate_overview_apps no longer runs on pull_request. It runs on push to standard, regenerates the catalogs there and pushes the result back with the default GITHUB_TOKEN. That push starts no workflow run, so this does not loop.

The cloud and 702 rebuilds are dispatched explicitly. A push made with GITHUB_TOKEN does not start further workflow runs — GitHub's guard against recursive workflows — so auto_cloud and auto_downport would not react to the bot commit and the cloud and 702 branches would keep the stale catalog until the next unrelated push. workflow_dispatch is exempt from that restriction, so the job triggers both after pushing; each gains a workflow_dispatch trigger for that.

Adds the missing tile for sample 443 so standard is green again immediately.

AGENTS.md §4 now states that a stale catalog never blocks a pull request, while still recommending that contributors regenerate — it keeps the diff reviewable and saves the extra bot commit.

Follow-up needed to activate

standard is protected, so the push only works once the GitHub Actions app is a bypass actor on the standard branch ruleset. That is the only manual step. Until it is configured the job fails on a diff with an actionable message, which is exactly the previous behaviour — nothing breaks on merge.

An earlier revision of this branch used a deploy key. It turned out to buy only the workflow re-triggering, which workflow_dispatch covers, so the secret, its rollover and the caveat that deploy keys cannot be bypass actors under classic branch protection are all gone.

Verification

• npx abaplint — 0 issues across 719 files
• node scripts/check-agents-structure.js — passes
• npm run launchpad produces no further diff
• All three workflow files parse; triggers and permissions are as intended
• The sync step was exercised against a scratch repository: no diff → exit 0, nothing dispatched; diff → commit pushed to standard and both rebuilds dispatched; diff with the push rejected (simulating the missing ruleset bypass) → exit 1 with the actionable message and no dispatch

🤖 Generated with Claude Code

https://claude.ai/code/session_01Cpu46KEg8yScnPEVUKS8fL