Framework hardening follow-ups after PR #121

[Yehonal]

This issue tracks the main non-blocking framework follow-ups intentionally left outside PR #121.

Reference:

• PR: feat: add task system app scaffold and plan #121
• Repo doc: docs/framework-hardening-followups.md

Why

PR #121 fixes real problems and is merge-ready, but a few follow-ups should remain visible instead of being forgotten after merge.

Tracked follow-ups

• Simplify legacy repository capability fallback now that crud-gen has explicit repository capabilities
• Clean up deprecated/permissive GraphQL input paths after restoring stronger generated field-id typing
• Decide whether invalid-path GraphQL errors in examples should stay tolerant (400 vs 200 + errors[]) or be normalized more strictly
• Harden event-manager
• Harden api-strategy

Notes

These items are tracked as follow-ups because they are:

• real improvements
• not hidden blockers for PR feat: add task system app scaffold and plan #121
• better handled as focused hardening tasks than as scope creep inside the scaffold PR