replace bash scripts with unified tutorial creator CLI

[todortodorovic]

Summary

Replaced two separate bash scripts with a single unified CLI tool that automates tutorial creation from start to finish.

Changes

Unified Tutorial Creator

• Replaced: scaffold-tutorial.sh + bootstrap-tests.sh → create-tutorial.js
• Command: npm run create-tutorial my-tutorial
• Does everything:
  • Creates git branch
  • Scaffolds folder structure
  • Sets up test environment
  • Installs dependencies
  • Validates input and shows next steps

Documentation

• Added: .github/TUTORIAL_WORKFLOW.md with visual Mermaid diagram
• Updated: CONTRIBUTING.md with quick start guide

Benefits

• 6 commands → 1 command for contributors
• Better validation and error handling
• Single source of truth (no confusion)
• Clearer progress feedback

Testing

npm run create-tutorial test-tutorial
cd tutorials/test-tutorial
npm test

[brunopgalvao]

Overall looks good. One feedback that I have is why not create the CLI in Rust? As a systems programming language, Rust would be an excellent choice for a CLI tool. The code would compile down into a CLI binary that users can download and execute e.g. create-tutorial test-tutorial. Additionally, since I consider Parity/Polkadot mostly as a "Rust shop", I think it is good for us to invest regular practice using Rust as the ROI will pay off in terms of becoming more fluent and knowledgeable with the Polkadot SDK.

[todortodorovic]

I agree with you, everything has now been fully migrated to Rust. A refactor has also been done, so the code is split into multiple files for easier future improvements. Tests have been added for all functions, along with end-to-end tests.

[brunopgalvao]

A good start.

[brunopgalvao]

Ideally we will have a CI job that builds this and users can download the binary according to their OS.
This can come in a later PR.

[brunopgalvao]

Please update the CONTRIBUTING.md to reflect these steps e.g. cargo build, npm run...

[brunopgalvao]

I recommend using a git crate instead of relying on using whatever git binary they have on their machine.