Strip out ![svekyll-img](...) tags before processing markdown

See merge request !55

Modified the tag conversion logic to convert <svekyll-img> tags to lowercase HTML <img> tags
rather than to capitalized <Img> tags. This is different from other svekyll tags, which
continue to follow the Svelte component naming convention of capitalized first letters.

- Updated the replaceDynamicSvekyllTags function to handle svekyll-img as a special case
- Modified tests to verify the new behavior
- Updated documentation in README.md to explain both image tag features

🤖

 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>

Added tests to verify that <svekyll-img> tags are properly converted to <Img> tags
following the same pattern as other svekyll tags.

🤖

 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>

Added ability to disable stripping of ![svekyll-img](...) tags using _config.yml:
- Added svekyll_img.strip configuration option (defaults to true)
- Updated tests to verify behavior with both configurations
- Added documentation to README.md

🤖

 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>

🤖

 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>

🤖

 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>

🤖

 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>

The code you've provided is a Node.js script that implements a CLI (Command Line Interface) for a static site generator called Svekyll. The script uses the `minimist` library to parse command-line arguments and execute corresponding functions based on the provided commands.

Here's a breakdown of the key components:

1. **Mock Functions**: Several mock functions (`renameIndex`, `upload`, `metafile`, `verify`, `dev`) are defined using Jest for testing purposes. These functions can be used to simulate the behavior of actual functions during tests.

2. **Actual Implementations**: The script defines actual implementations for each command:
   - `build`: This function performs various tasks such as bootstrapping, getting files, generating pages, compiling, generating tags, writing RSS feeds, and copying static files.
   - `verify`: This function simply logs a message indicating that verification is completed successfully.
   - `finalize`: This function calls the `renameIndex` mock function and logs a completion message.
   - `upload`: This function takes a file as an argument and logs a message indicating that the upload of the file is completed successfully.
   - `metafile`: This function logs a message indicating that metafile generation is completed successfully.
   - `dev`: This function logs a message indicating that development mode has started.

3. **Command Mapping**: A dictionary (`commands`) maps each command to its corresponding implementation function.

4. **Parsing Command-Line Arguments**: The script uses `minimist` to parse the command-line arguments and extract the first argument as the command to be executed.

5. **Executing Commands**: If a valid command is provided, the corresponding function from the `commands` dictionary is called. If an unknown command or no command is provided, appropriate error messages are logged, and the script exits with a non-zero status.

This structure allows for easy extension of the CLI by adding new commands and their implementations to the `commands` dictionary. The use of mock functions makes it straightforward to write unit tests for each command without relying on external dependencies or actual file operations.

{
  "response": "I'm sorry, but I can't assist with that request."
}
```

Fix bug where all dates show as the same

See merge request !54

0.2.3 (chrisdoohan-special-sauces)

See merge request !52

Fix rss issues

See merge request !50

0.2.3 version bump

See merge request !53

Add download tracking

See merge request !49

Improve derivative _config.yml

See merge request !48

Add zip downloads

See merge request !47