Fix the two cross-PC risks identified in the site audit.\n\nChanges:\n- Set an explicit default content color on the shared main container with a dark-mode counterpart, preventing generic page content from relying on inherited browser/theme colors.\n- Add an explicit wedding.event_end RFC3339 configuration value and expose it through /api/config. The details calendar download now uses that exact local end time instead of adding a fixed 7.5-hour duration in the browser.\n\nVerification:\n- cd ui && pnpm run check\n- cd ui && pnpm run build\n- cd server && go test ./...\n- git diff --check\n\nDeployment note: the runtime config.yaml must include wedding.event_end, as documented in README.md and config.example.yaml.
Fix the two cross-PC risks identified in the site audit.\n\nChanges:\n- Set an explicit default content color on the shared main container with a dark-mode counterpart, preventing generic page content from relying on inherited browser/theme colors.\n- Add an explicit wedding.event_end RFC3339 configuration value and expose it through /api/config. The details calendar download now uses that exact local end time instead of adding a fixed 7.5-hour duration in the browser.\n\nVerification:\n- cd ui && pnpm run check\n- cd ui && pnpm run build\n- cd server && go test ./...\n- git diff --check\n\nDeployment note: the runtime config.yaml must include wedding.event_end, as documented in README.md and config.example.yaml.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fix the two cross-PC risks identified in the site audit.\n\nChanges:\n- Set an explicit default content color on the shared main container with a dark-mode counterpart, preventing generic page content from relying on inherited browser/theme colors.\n- Add an explicit wedding.event_end RFC3339 configuration value and expose it through /api/config. The details calendar download now uses that exact local end time instead of adding a fixed 7.5-hour duration in the browser.\n\nVerification:\n- cd ui && pnpm run check\n- cd ui && pnpm run build\n- cd server && go test ./...\n- git diff --check\n\nDeployment note: the runtime config.yaml must include wedding.event_end, as documented in README.md and config.example.yaml.