chore: rescue stranded sweep 2-4 commits (config, licenses, C-A-G-M)

.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*

LICENSES/MPL-2.0.txt

@@ -35,7 +35,7 @@ Mozilla Public License Version 2.0
     means any form of the work other than Source Code Form.
 
 1.7. "Larger Work"
-    means a work that combines Covered Software with other material, in 
+    means a work that combines Covered Software with other material, in
     a separate file or files, that is not Covered Software.
 
 1.8. "License"
@@ -357,7 +357,7 @@ Exhibit A - Source Code Form License Notice
 
   This Source Code Form is subject to the terms of the Mozilla Public
   License, v. 2.0. If a copy of the MPL was not distributed with this
-  file, You can obtain one at http://mozilla.org/MPL/2.0/.
+  file, You can obtain one at https://mozilla.org/MPL/2.0/.
 
 If it is not possible or desirable to put the notice in a particular
 file, then You may include the notice in a location (such as a LICENSE

MAINTAINERS

@@ -0,0 +1,43 @@
+# Maintainers
+
+This file lists the current maintainers of this project.
+
+## Active Maintainers
+
+| Name | GitHub | Role | Since |
+|------|--------|------|-------|
+| Metadatastician | @metadatastician | Primary | Project Start |
+
+## Emeritus Maintainers
+
+None at this time.
+
+## Becoming a Maintainer
+
+To become a maintainer:
+
+1. Demonstrate consistent, high-quality contributions
+2. Show understanding of the project's goals and architecture
+3. Be active in code reviews and community discussions
+4. Be nominated by an existing maintainer
+5. Be approved by consensus of existing maintainers
+
+## Maintainer Responsibilities
+
+- Reviewing and merging pull requests
+- Managing releases
+- Triaging issues
+- Enforcing code standards
+- Mentoring new contributors
+- Participating in decision-making
+
+## Maintainer Expectations
+
+- Respond to issues and PRs in a timely manner
+- Follow the code of conduct
+- Be transparent in decision-making
+- Communicate clearly and respectfully
+
+---
+
+*Last updated: 2026-07-18*

mise.toml

@@ -0,0 +1,57 @@
+[tools]
+# Language runtimes
+node = "latest"
+python = "latest"
+rust = "latest"
+go = "latest"
+zig = "latest"
+java = "latest"
+bun = "latest"
+denojs = "latest"
+
+# Package managers
+npm = "latest"
+yarn = "latest"
+pnpm = "latest"
+pip = "latest"
+cargo = "latest"
+go-task = "latest"
+
+# Formatting & Linting
+gofmt = "latest"
+black = "latest"
+isort = "latest"
+ruff = "latest"
+prettier = "latest"
+shfmt = "latest"
+stylua = "latest"
+
+# Build tools
+cmake = "latest"
+make = "latest"
+ninja = "latest"
+
+# Shell tools
+git = "latest"
+gnu-sed = "latest"
+gnu-tar = "latest"
+gnu-grep = "latest"
+
+# Testing
+vitest = "latest"
+pytest = "latest"
+jest = "latest"
+
+[env]
+# Common environment variables
+NODE_ENV = "development"
+PYTHONDONTWRITEBYTECODE = "1"
+PYTHONUNBUFFERED = "1"
+
+# Task runner alias
+[alias]
+task = "go-task"
+build = "cargo build --release || npm run build || go build"
+test = "cargo test || npm test || go test ./..."
+lint = "ruff check . || prettier --check . || black --check ."
+fmt = "ruff format . || prettier --write . || black ."