Automate repository delivery and maintenance

[KickNext]

What changed

• deploy the Flutter demo to GitHub Pages from main
• validate, publish to pub.dev through OIDC, then create a GitHub Release for version tags
• enable weekly Dependabot updates for Dart packages and GitHub Actions
• pin all Actions to immutable commit SHAs
• add CODEOWNERS, a compact PR template, and live README badges

Verification

• actionlint
• flutter analyze --fatal-infos --fatal-warnings
• flutter test --coverage (114 tests)
• example flutter test (24 tests)
• example web release build with /morphnext/ base path

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 159b83b15d

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Grant Pages access to the build job

The build job inherits only contents: read, but actions/configure-pages queries the repository's Pages configuration using github.token, which requires Pages repository access. The pages: write permission declared under deploy applies only to that job, so every main-branch run will fail at Configure Pages before an artifact can reach the deploy job. Grant the build job at least pages: read (or apply the standard Pages permissions at workflow level).

Useful? React with 👍 / 👎.