Add blocks project seed for seeding

[jamdelion]

What's changed?

PR description written by Claude, and reviewed by JH

Adds a Blocks (Scratch) starter project to the seed data, so developers working on integrated
Blocks editor projects in projects-ui have a real example locally instead of having to hand-craft
a scratch_component row.

• New lib/tasks/project_components/neil-the-seal-starter/ containing neil-the-seal-starter.sb3
  and a project_config.yml with TYPE: "code_editor_scratch". Picked up automatically by
  rails projects:create_all, which db/seeds.rb already invokes.
• The .sb3 is copied unmodified from
  raspberrypilearning/editor-neil-the-seal
  at en/code/neil-the-seal-starter/neil-the-seal-starter.sb3. The identifier
  neil-the-seal-starter matches production, so local and deployed data agree.
• Documents Scratch seeds in lib/tasks/README.md, which previously only covered Python and HTML.
  Most usefully it warns that content repositories use a lowercase-keyed project_config.yml
  read by the webhook/UploadJob path, whereas the seeding task reads uppercase keys — copying
  one across verbatim parses fine but silently produces a nameless Python project.
• Relaxes the README's claim that IDENTIFIER is "three words separated by dashes"; it isn't
  enforced and existing projects such as editor-scratch-testing-starter already use more.

Related

Reaching this project through projects-ui also needs the projects-admin seed that sets
direct_to_editor and editor_starter_project — this happens using the production-to-local script. Once both are
seeded it's at /en/projects/editor-neil-the-seal/editor. It's unlisted and in no pathway,
matching the current status of production, so it can't be reached by browsing.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have you on file. In order for us to review and merge your code, please complete this form and we'll get you added and review your contribution as soon as possible.

[Copilot]

🟡 Changes recommended

Newly added README guidance contains a couple of misleading/unclear statements that should be corrected to avoid developer confusion when running seeds.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Adds a Scratch (Blocks) starter project into the local seed/import pipeline so developers can work against realistic Scratch project data, and updates the seeding documentation to cover Scratch projects.

Changes:

• Add a new Scratch starter seed directory for neil-the-seal-starter (config + .sb3).
• Document how Scratch seeds are imported (and how this differs from content-repo project_config.yml files).
• Rename the Hello World starter project identifier to editor-hello-world-starter.

File summaries

File	Description
lib/tasks/README.md	Documents Scratch seed structure and config conventions, plus identifier guidance.
lib/tasks/project_components/neil-the-seal-starter/project_config.yml	Adds seed metadata for the new Scratch starter project.
lib/tasks/project_components/neil-the-seal-starter/neil-the-seal-starter.sb3	Adds the Scratch starter project archive used by the importer.
lib/tasks/project_components/hello_world_starter/project_config.yml	Updates the seeded project identifier for Hello World.

Review details

• Files reviewed: 3/4 changed files
• Comments generated: 2
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

Test coverage

93.57% line coverage reported by SimpleCov.
Run: https://github.com/RaspberryPiFoundation/editor-api/actions/runs/34213346003

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have you on file. In order for us to review and merge your code, please complete this form and we'll get you added and review your contribution as soon as possible.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have you on file. In order for us to review and merge your code, please complete this form and we'll get you added and review your contribution as soon as possible.

[zetter-rpf]

Nice one.

I've added you to the CLA list so you should be able to merge once you rebase/merge in main.