docs: reference template method pattern

[lavaFreak]

Summary

Add a short note to the stage customization docs explaining that StagedScript follows the Template Method pattern.

Related Issue

Closes #105

What changed

• Added a brief explanation in the “Customizing Stage Behavior” docs section.
• Linked to a concise external reference for the Template Method pattern.

Validation

• Reviewed the updated docs text in context.
• Ran git diff --check.
• I was not able to run the repo's Python tooling locally in this checkout because pytest and ruff are not currently installed in this environment.

Summary by Sourcery

Document the Template Method pattern usage in stage customization examples.

Documentation:

• Add a brief explanation in the stage customization docs that StagedScript follows the Template Method design pattern.
• Link to an external reference describing the Template Method pattern from the stage customization documentation.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the stage customization documentation to briefly explain that StagedScript uses the Template Method pattern and adds an external reference link for further reading.

File-Level Changes

Change	Details	Files
Clarified documentation on how StagedScript can be customized by explicitly describing its use of the Template Method pattern and linking to an external reference.	Expanded the 'Customizing Stage Behavior' section to mention that StagedScript follows the Template Method design pattern. Added a short explanatory note tying the pattern concept to how stages are overridden/customized in practice. Inserted a link to a concise external reference that explains the Template Method pattern for readers unfamiliar with it.	doc/source/examples.rst

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[jmgate]

praise: Thanks so much for the contribution, @lavaFreak 😀. Definitely should've done this ages ago—thanks for taking care of it.

todo: Could you please relocate your addition to the end of the stage implementation details page? If a user is reading through the docs sequentially, I'd like it to show up the first time they might realize the template method pattern is in play.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (5760488) to head (c7b8c3a).

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #296   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines          177       177           
  Branches        15        15           
=========================================
  Hits           177       177           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jmgate]

Thanks again, @lavaFreak. If there are any other issues you'd like to take a crack at, feel free. As you use the package, do let me know if you run into any problems, usability improvements, etc.

[lavaFreak]

Thanks, Jason. I appreciate the helpful review and the invitation. I'll definitely be looking into some other issues in the repo.