Fix feature catalogue template resolution

[adulau]

Motivation

• The features page was falling back to the generic page template so the feature "card" catalogue from data/feature_catalog.yaml was not being rendered.
• Hugo resolves page templates by content type and lookup path, so the content frontmatter and template location needed to match the Hugo lookup conventions.

Description

• Change content/features.md frontmatter from layout: features to type: features to expose the page as the features content kind used by Hugo.
• Move the bespoke template from layouts/page/features.html into the canonical lookup path layouts/features/single.html so Hugo will resolve the specialized template for the features content type.
• Remove the stale override at layouts/page/features.html and ensure the new template contains the feature-card markup that iterates Site.Data.feature_catalog.

Testing

• Asserted the content frontmatter matches with test "$(sed -n 's/^type: //p' content/features.md)" = "features" and the test passed.
• Verified layouts/features/single.html exists and contains <article class="feature-card"> and the check succeeded.
• Verified data/feature_catalog.yaml contains feature entries and that layouts/page/features.html no longer exists.
• Ran git diff --check / git diff --cached --check and git status validations which all succeeded; a full hugo render could not be produced because the theme submodule could not be fetched (HTTP 403), so end-to-end site rendering was not possible in this environment.

---

Codex Task

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-29T08:11:51.873011Z	56ef98b	PR opened
🔒 Security Review	✅ Completed 2026-09-29T08:12:41.356380Z	56ef98b	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.