chore(deps): bump thiserror from 2.0.18 to 2.0.19 in /bots/echidnabot (#423)

Bumps [thiserror](https://github.com/dtolnay/thiserror) from 2.0.18 to
2.0.19.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/dtolnay/thiserror/releases">thiserror's
releases</a>.</em></p>
<blockquote>
<h2>2.0.19</h2>
<ul>
<li>Update to syn 3</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/dtolnay/thiserror/commit/e13a7854338e446f184725fc8b9c9e86a0a537d2"><code>e13a785</code></a>
Release 2.0.19</li>
<li><a
href="https://github.com/dtolnay/thiserror/commit/0a0e76cc0f041a32e638328b47721b00037d0690"><code>0a0e76c</code></a>
Update to syn 3</li>
<li><a
href="https://github.com/dtolnay/thiserror/commit/ec42ea70852f8db43e971700d1ccc184957d1b32"><code>ec42ea7</code></a>
Update actions/upload-artifact@v6 -&gt; v7</li>
<li><a
href="https://github.com/dtolnay/thiserror/commit/4178c4a0e1cb17473d95f42f5e441ef92d13d172"><code>4178c4a</code></a>
Update actions/checkout@v6 -&gt; v7</li>
<li><a
href="https://github.com/dtolnay/thiserror/commit/7214e0e8331d76afbea7173d8a14997512ac8713"><code>7214e0e</code></a>
Ignore items_after_statements pedantic clippy lint in test</li>
<li><a
href="https://github.com/dtolnay/thiserror/commit/febcc0381f003783efbb01595eb511bdf0c6f460"><code>febcc03</code></a>
Merge pull request <a
href="https://redirect.github.com/dtolnay/thiserror/issues/451">#451</a>
from vip892766gma/maint/20260521171412</li>
<li><a
href="https://github.com/dtolnay/thiserror/commit/c50e38779da40084363232252c46d86dc59286d0"><code>c50e387</code></a>
chore: improve thiserror maintenance path</li>
<li><a
href="https://github.com/dtolnay/thiserror/commit/d4a2507576d276dbebc4be45c9b3d657216b727f"><code>d4a2507</code></a>
Raise minimum tested compiler to rust 1.85</li>
<li><a
href="https://github.com/dtolnay/thiserror/commit/99e8a6cd6a312d455d74f40b449a6cbb868b2460"><code>99e8a6c</code></a>
Unpin CI miri toolchain</li>
<li><a
href="https://github.com/dtolnay/thiserror/commit/9ac165c40055a126fc5d2ca49f4024bbac575d95"><code>9ac165c</code></a>
Pin CI miri to nightly-2026-02-11</li>
<li>Additional commits viewable in <a
href="https://github.com/dtolnay/thiserror/compare/2.0.18...2.0.19">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=thiserror&package-manager=cargo&previous-version=2.0.18&new-version=2.0.19)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
Co-authored-by: Mistral Vibe <vibe@mistral.ai>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Author: 3 people

.github/funding.yml

@@ -0,0 +1,4 @@
+# Funding Configuration
+# See: https://docs.github.com/en/repositories/managing-your-repositorys-custom-fields/displaying-a-sponsor-button-in-your-repository
+
+github: metadatastician

ARCHITECTURE.md

@@ -0,0 +1,47 @@
+# Architecture
+
+## Overview
+
+This repository follows a modular, maintainable architecture designed for clarity, scalability, and long-term sustainability.
+
+## Directory Structure
+
+```
+.
+├── src/           # Source code
+├── tests/        # Test suites
+├── docs/         # Documentation
+├── scripts/      # Utility scripts
+├── config/       # Configuration files
+├── LICENSE       # License file
+├── LICENSES/     # Full license texts
+└── README.adoc   # Project documentation
+```
+
+## Design Principles
+
+- **Separation of Concerns**: Each module has a single responsibility
+- **Testability**: Code is written to be easily testable
+- **Documentation**: All public APIs are documented
+- **Configuration**: Environment-specific settings are externalized
+
+## Dependencies
+
+- External dependencies are minimized and clearly declared
+- Version pinning is used for reproducibility
+
+## Security Considerations
+
+- Sensitive data is never committed to the repository
+- Secrets are managed through environment variables or secure vaults
+- Regular dependency audits are performed
+
+## Maintainability
+
+- Code follows consistent style guidelines
+- Pull requests require review and CI checks
+- Issues and discussions are tracked transparently
+
+---
+
+*Last updated: 2026-07-18*

GOVERNANCE.md

@@ -0,0 +1,60 @@
+# Governance
+
+## Overview
+
+This project is governed by the following principles and structures to ensure transparent, inclusive, and effective decision-making.
+
+## Roles and Responsibilities
+
+### Maintainers
+
+Maintainers are responsible for:
+- Reviewing and merging pull requests
+- Managing releases and versioning
+- Ensuring code quality and standards
+- Triaging issues and bug reports
+- Community engagement and support
+
+### Contributors
+
+Contributors are expected to:
+- Follow the code of conduct
+- Submit well-documented pull requests
+- Write tests for new functionality
+- Maintain existing tests
+- Update documentation as needed
+
+## Decision Making
+
+### Minor Changes
+- Can be made by any maintainer
+- Include bug fixes, documentation updates, dependency updates
+
+### Major Changes
+- Require discussion in issues or pull requests
+- Include new features, architectural changes, API changes
+- Need approval from at least 2 maintainers
+
+### Breaking Changes
+- Require RFC (Request for Comments) process
+- Need approval from majority of maintainers
+- Must include migration guide
+
+## Code of Conduct
+
+All participants are expected to follow our Code of Conduct. Violations can be reported to the maintainers.
+
+## Communication
+
+- **Issues**: For bug reports and feature requests
+- **Discussions**: For questions and general discussion
+- **Pull Requests**: For code contributions
+
+## Licensing
+
+All contributions are made under the terms of the repository's LICENSE file.
+By submitting a pull request, you agree to license your contributions accordingly.
+
+---
+
+*Last updated: 2026-07-18*