fix(export): allow static elements beyond the bleed boundary

[patriksimms]

Problem

Images and other static layout elements beyond the bleed boundary currently block the organizer from exporting, even though the exported page can safely clip them.

Solution

Report those placements as warnings while preserving blocking validation for question-bound text and all unrelated export problems.

Validation

• All static and image element types warn beyond bleed
• Question-bound text remains blocking
• Automated preflight passes with the new warning
• Full repository verification suite passes
• Matched book-review and export evidence is attached to issue Images and other static elements when they go over the bleed radius should only create a warning, not an error preventing the export #56

Closes #56

Built with Codex in T3 Code using gpt-5.6-sol.

[patriksimms]

Delivery status

The change passes the complete repository gate locally:

• format, lint, and typecheck
• 223 unit tests
• 20 end-to-end tests (2 intentional skips)
• production build
• Compose and production-compose validation

Both required GitHub checks fail before compiling this branch because bun run setup:icc cannot create .local/icc after Docker creates .local as root (EACCES). The current main run fails at the same step: https://github.com/patriksimms/sakekeep/actions/runs/31974752917

This is a baseline CI ownership failure introduced by the latest main commit, not a failure caused by this change. The PR remains draft until the required check can run successfully.

[patriksimms]

The baseline CI fix is ready and green in #61. It upgrades actions/checkout to v7 and runs ICC setup before Docker creates .local bind-mount directories. Once #61 is merged, this PR can be updated and rerun.