fix(editor): support template and field query params and prefill (#75)

[bhushan4work]

Closes #75

Description

• Fix template selection from URL query parameters.
• Prefill editor fields from supported query parameters, including title and description.
• Support Smart Autofill URL prefill via ?autofill=.
• Ignore unknown template IDs and unsupported query parameters safely.
• Prevent hydration mismatches by applying URL parameters after mount.
• Update README documentation to reflect the supported behavior.

How I Tested This

• npm run check
• npm run test
• Manually verify template selection, field prefill, Smart Autofill prefill, and unknown parameters on /create and /create/{category} using npm run dev.

AI Assistance

none

Type of Change

• Bug fix
• New template
• New feature
• Documentation
• Tests
• Refactoring
• Performance improvement
• Other (describe below)

Screenshots

Not applicable; no visual changes.

Checklist

• This PR targets dev
• I was assigned the linked issue
• npm run check passes
• npm run test passes
• For a bug fix: the new test fails without my change
• Tested locally with npm run dev
• Screenshots included for visual changes
• New templates follow the [Template Guidelines](https://github.com/codercops/ogcops/blob/dev/CONTRIBUTING.md#template-guidelines)

[anurag629]

Thanks @bhushan4work, the editor part works. I ran it on top of dev in headless Chrome: ?template=quote-centered-serif opens Centered Serif (also from /create/blog), ?title=Hello&description=World fills both fields, an unknown template id or key is ignored, ?autofill= opens Smart Autofill with the URL in it, edits stay after that, and the console has no hydration warnings. On dev the same links still open Minimal Dark. npm run check, all 483 tests and the build pass.

Three things before I merge:

• The README line still says you can "share or bookmark any configuration". Nothing writes the editor state back to the URL, so a bookmark taken after editing loses the edits. I left a suggestion for that line below.
• Please drop the "README.md:33 accuracy" test and the "gallery cards link to /create?template=id" test. The first one pins line 33 of the README word for word, so any edit above that line breaks it. The second builds the link inside the test, so it passes whatever templates.astro does.
• A value that isn't a number goes through as a string for number fields. /create?template=ecommerce-product-card&rating=abc puts "abc" in rating, the slider shows NaN and React logs "Received NaN" twice. Can you skip values where Number.isFinite is false, in both branches of parseEditorQueryParams, and add a test for it?

[anurag629]

Suggested change

	- **URL-based State**: Prefill editor state via URL params — share or bookmark any configuration
	- **Prefill from the URL**: Links like `/create?template=quote-centered-serif&quote=Hello` open the editor with that template and text filled in

[anurag629]

Thanks @bhushan4work, that's everything. /create?template=ecommerce-product-card&rating=abc now keeps the default rating and the console stays clean, the template links still open the right template, and the README line reads right. npm run check, all 482 tests and the build pass. Merging.