You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
WEB-SUGGESTIONS-001A: add a static Suggestions page - #620
Adds a source-only public Suggestions information page at /suggestions. The page provides one internal path to the existing Contact page and does not add a suggestion form, public idea list, external intake provider, suggestion record, or suggestion-specific service or analytics call.
The footer exposes the route as a secondary utility link. The primary navigation is unchanged.
Safety boundary
No Firebase, Functions, Firestore Rules, package, provider, or production configuration change.
No fields, upload, voting, submit control, external resource, or direct email link on the Suggestions page.
The copy states that Contact email is a separate existing channel and may retain the sender address and message.
The copy makes no anonymity, confidentiality, reply, or implementation promise.
The reviewed change is exactly 16 paths: the new page and CSS; route/footer/SEO-shell/sitemap integration; focused route, no-intake, sitemap, lint, and repository-safety tests; exact lint/current-truth metadata; and the affected content/map/preview officer documentation.
Real-browser checks: exact-one Suggestions SEO tags, 320px reflow and keyboard focus, 1440px 52rem content cap, footer routing, and Contact transition passed.
Three independent final reviews: GO.
Officer handoff
Officer impact: Visitors gain a clear, secondary path for short ideas through the existing Contact channel. This change assigns no mailbox owner, response deadline, moderation duty, or new provider workflow.
Officer documentation: docs/CONTENT_GUIDE.md, docs/officers/SYSTEM_MAPS.md, and docs/officers/UPDATE_PUBLIC_CONTENT.md.
Deployment evidence: Source and local tests/browser checks only at publication. The website has not been published or verified from this PR. No Firebase deployment, outside-provider configuration, production-data action, or live behavior check occurred.
READY-TO-MERGE marker for exact reviewed head da87c253951d953693d3712d224f2d103482a1c3 (tree a746c0e50c7f43db93b95e249f4fc77ad5e7bab3, 16-path patch SHA-256 af4d18827b32a9477f04004a93130620463dd39d1a929fd2a86c692c17871ac7). Three independent exact-diff reviews returned GO: documentation/scope/backup-officer; privacy/UX/browser; tests/lint/mutation. CI run 31673796755 passed all five required jobs. Exact-head Netlify preview deploy 6a7d636d30804600088f9784 is ready, preview-only (published_at null), and bound to this exact commit. Readback: /suggestions, /contact, and /robots.txt are HTTP 200/no redirects; exact-one Suggestions title/canonical/description/H1; zero forms/intake controls/provider resources in main; sole main link routes to /contact; HSTS/noindex present; no console errors beyond the existing app_check_disabled warning. Source changed/tests passed/preview verified; website production, Firebase, outside provider, data, and live runmprc.com remain unchanged. GitHub's required-review gate cannot represent these independent Codex reviews, so the controlled admin-squash path is required after one final base-freshness check.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #618
Outcome
Adds a source-only public Suggestions information page at /suggestions. The page provides one internal path to the existing Contact page and does not add a suggestion form, public idea list, external intake provider, suggestion record, or suggestion-specific service or analytics call.
The footer exposes the route as a secondary utility link. The primary navigation is unchanged.
Safety boundary
Scope
The reviewed change is exactly 16 paths: the new page and CSS; route/footer/SEO-shell/sitemap integration; focused route, no-intake, sitemap, lint, and repository-safety tests; exact lint/current-truth metadata; and the affected content/map/preview officer documentation.
Exact reviewed head: da87c25
Exact tree: a746c0e50c7f43db93b95e249f4fc77ad5e7bab3
Exact binary patch SHA-256: af4d18827b32a9477f04004a93130620463dd39d1a929fd2a86c692c17871ac7
Verification
Officer handoff
Officer impact: Visitors gain a clear, secondary path for short ideas through the existing Contact channel. This change assigns no mailbox owner, response deadline, moderation duty, or new provider workflow.
Officer documentation: docs/CONTENT_GUIDE.md, docs/officers/SYSTEM_MAPS.md, and docs/officers/UPDATE_PUBLIC_CONTENT.md.
Deployment evidence: Source and local tests/browser checks only at publication. The website has not been published or verified from this PR. No Firebase deployment, outside-provider configuration, production-data action, or live behavior check occurred.