Restructure examples and development tools

• Renames templates as `examples in comments and method names. Previous methods exist as wrappers only, but will be deprecated in a future release.
• Restructures tests to leave only examples within the package, not the tests or invalid cases.
• Reinstates CLI as a local testing tool, as this makes updating validation when working with MCP a smoother process instead of rewriting/committing a test.py file. This adds but does not change previous behavior. Also adds an examples command to list, and an --example option flag to validate built-in examples
• Updates missing items in the CHANGELOG

Add tests for hugo, django with celery, redis, pgvector

Add tests for hugo, django with celery, redis, pgvector

Build process automation

This release introduces no new functionality but is the first release with a more automated build system.

Better build process

Upgrading the build process to be easier to maintain.

Include tests (templates) in package

Includes the tests (valid templates) in the package.

Include template files in release - take 2

This release includes the valid test (.upsun/config.yaml) files which serve as best practice examples.

Include template files in release

This release fixes a bug in the release mechanism which prevented the .upsun/config.yaml template examples from being packaged with the release.

0.2.1

The new get template functionality needs the passing tests to be packaged with the release. This incremental release fixes that.

MCP Formatting

Library was restructured to prioritize string-based validation prompts for the MCP use case.

Additional post-release fixes

Running PR for additional tweaks and fixes following the initial release:

• Single installation path for now
• Update upgrade instructions
• Removes generate/gen command placeholder, as ultimately out of scope
• Raises ValidationError when top-level keys are included, instead of silently failing, and handle top-level duplicates within the same file.