docs: clean up imgcli scaffold

.github/repository-settings.toml

@@ -1,15 +1,13 @@
 # GitHub repository settings managed by scripts/configure_github_repo.py.
 #
 # Run:
-#   uv run scripts/configure_github_repo.py plan --repo OWNER/REPO
-#   uv run scripts/configure_github_repo.py apply --repo OWNER/REPO
+#   uv run scripts/configure_github_repo.py plan --repo meigma/imgcli
+#   uv run scripts/configure_github_repo.py apply --repo meigma/imgcli
 #
 # Notes:
 # - Supported settings are applied directly through the GitHub REST API.
 # - Unsupported settings stay in this file so the script can report manual follow-ups.
 # - The branch ruleset follows the repository default branch via ~DEFAULT_BRANCH.
-# - Status checks are enabled in the screenshots, but the actual contexts are repository-specific.
-#   Fill them in before expecting the status-check rules to be applied.
 
 [repository]
 default_branch = "master"
@@ -72,7 +70,7 @@ enabled = true
 strict_required_status_checks_policy = false
 do_not_enforce_on_create = false
 contexts = [
-  # "ci / build",
+  "ci",
 ]
 
 [rulesets.tags_default]
@@ -92,12 +90,10 @@ bypass = [
 ]
 
 [rulesets.tags_default.status_checks]
-enabled = true
+enabled = false
 strict_required_status_checks_policy = false
 do_not_enforce_on_create = false
-contexts = [
-  # "release / verify",
-]
+contexts = []
 
 [unsupported]
 # GitHub Archive Program

.gitignore

@@ -67,7 +67,7 @@ pnpm-debug.log*
 .svelte-kit/
 coverage/
 
-# Template repo outputs
+# Documentation outputs
 docs/node_modules/
 docs/build/
 docs/.docusaurus/

.moon/toolchains.yml

@@ -1,48 +1,14 @@
-# Active toolchains for the current template.
-# The docs project uses npm today, but this file is meant to be a starting
-# point for future repos that may choose different ecosystems.
+# Active toolchains for imgcli.
+# The current repository content is the npm-backed documentation site.
 
 javascript:
   packageManager: 'npm'
-  inferTasksFromScripts: true
+  inferTasksFromScripts: false
 
 npm: {}
 
 node:
   version: '22.22.2'
   syncVersionManagerConfig: 'nvm'
 
-# Configure npm directly when you want to pin the CLI or customize installs.
-# npm:
-#   version: 'REPLACE_ME_NPM_VERSION'
-#   installArgs: ['--include=dev']
-
-# Swap npm for pnpm, yarn, bun, or deno as needed.
-# javascript:
-#   packageManager: 'pnpm'
-#   inferTasksFromScripts: true
-#
-# pnpm:
-#   version: 'REPLACE_ME_PNPM_VERSION'
-#
-# bun:
-#   version: 'REPLACE_ME_BUN_VERSION'
-#
-# deno:
-#   version: 'REPLACE_ME_DENO_VERSION'
-
-# Stable non-JavaScript toolchains in Moon v2.
-# go:
-#   version: 'REPLACE_ME_GO_VERSION'
-#
-# rust:
-#   version: 'REPLACE_ME_RUST_VERSION'
-#   components: ['clippy', 'rustfmt']
-
-# Python remains unstable in Moon v2.
-# unstable_python:
-#   version: 'REPLACE_ME_PYTHON_VERSION'
-#   packageManager: 'uv'
-#
-# unstable_uv:
-#   version: 'REPLACE_ME_UV_VERSION'
+# Add the Go toolchain when the CLI implementation lands.

.moon/workspace.yml

@@ -1,4 +1,4 @@
-# Shared Moon workspace configuration for the repository template.
+# Shared Moon workspace configuration for imgcli.
 # Keep the current projects explicit, then uncomment the discovery patterns
 # below as the template grows into apps, packages, services, or tools.
 
@@ -24,7 +24,7 @@ projects:
 defaultProject: 'docs'
 
 vcs:
-  defaultBranch: 'main'
+  defaultBranch: 'master'
   provider: 'github'
 
 # Uncomment when you want Moon to aggregate project owners into CODEOWNERS.

CONTRIBUTING.md

@@ -1,19 +1,18 @@
 # Contributing
 
-> Template note: replace every `ALL_CAPS` placeholder in this file before publishing or sharing the repository.
-
-Thank you for your interest in contributing to `PROJECT_NAME`.
-This guide covers questions, bug reports, feature requests, and pull requests.
+Thank you for your interest in contributing to `imgcli`. This guide covers
+questions, bug reports, feature requests, and pull requests.
 For private vulnerability reporting, use [SECURITY.md](SECURITY.md) instead of public channels.
 
 ## Asking Questions
 
-Use `REPLACE_ME_SUPPORT_CHANNEL` for usage questions, troubleshooting, and general discussion.
-If the project uses multiple support channels, document which kinds of questions belong in each one.
+Use [GitHub Discussions](https://github.com/meigma/imgcli/discussions) for usage
+questions, troubleshooting, and general discussion.
 
 ## Reporting Bugs
 
-Report non-security bugs through `REPLACE_ME_BUG_REPORT_CHANNEL`.
+Report non-security bugs through
+[GitHub Issues](https://github.com/meigma/imgcli/issues).
 Include the following details when possible:
 
 - version, commit, or environment details
@@ -26,8 +25,11 @@ If you are reporting a security issue, stop and follow [SECURITY.md](SECURITY.md
 
 ## Proposing Features
 
-Use `REPLACE_ME_FEATURE_REQUEST_CHANNEL` for feature requests and design proposals.
-For larger changes, describe the problem, the proposed approach, and any compatibility or migration concerns before starting implementation.
+Use [GitHub Issues](https://github.com/meigma/imgcli/issues) or
+[GitHub Discussions](https://github.com/meigma/imgcli/discussions) for feature
+requests and design proposals. For larger changes, describe the problem, the
+proposed approach, and any compatibility or migration concerns before starting
+implementation.
 
 ## Pull Requests
 
@@ -39,30 +41,22 @@ Unless the repository documents a different process, contributors should:
 4. Describe the change clearly in the pull request.
 5. Make sure CI passes before requesting review.
 
-Replace this section with any repository-specific expectations such as branch naming, commit conventions, changelog entries, or release notes requirements.
-
 ## Local Setup
 
-Replace this section with the actual setup steps for the repository.
-
 ```sh
-REPLACE_ME_SETUP_COMMAND
+npm ci --prefix docs
 ```
 
 Useful project commands:
 
 ```sh
-REPLACE_ME_TEST_COMMAND
-REPLACE_ME_LINT_COMMAND
-REPLACE_ME_FORMAT_COMMAND
+npm --prefix docs run typecheck
+npm --prefix docs run build
+moon ci --summary minimal
 ```
 
-## Code of Conduct
-
-Replace this section with the actual Code of Conduct path or URL.
-Example: `REPLACE_ME_CODE_OF_CONDUCT_PATH_OR_URL`
-
 ## License and Ownership
 
-State any contribution licensing terms only if the project actually requires them.
-If the repository uses a CLA, DCO, or other contribution agreement, replace this section with the real policy.
+Unless otherwise stated, contributions are accepted under the same dual license
+as the repository: Apache License 2.0 or MIT, at your option. This repository
+does not currently require a CLA or DCO sign-off.

LICENSE

@@ -0,0 +1,10 @@
+imgcli is licensed under either of:
+
+- Apache License, Version 2.0 ([LICENSE-APACHE](LICENSE-APACHE))
+- MIT License ([LICENSE-MIT](LICENSE-MIT))
+
+at your option.
+
+Unless you explicitly state otherwise, any contribution intentionally submitted
+for inclusion in imgcli by you, as defined in the Apache License, Version 2.0,
+shall be dual licensed as above, without any additional terms or conditions.

LICENSE-APACHE

@@ -0,0 +1,185 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and
+distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the
+copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other
+entities that control, are controlled by, or are under common control with
+that entity. For the purposes of this definition, "control" means (i) the
+power, direct or indirect, to cause the direction or management of such
+entity, whether by contract or otherwise, or (ii) ownership of fifty percent
+(50%) or more of the outstanding shares, or (iii) beneficial ownership of such
+entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising
+permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation source, and
+configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or
+translation of a Source form, including but not limited to compiled object
+code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form,
+made available under the License, as indicated by a copyright notice that is
+included in or attached to the work (an example is provided in the Appendix
+below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that
+is based on (or derived from) the Work and for which the editorial revisions,
+annotations, elaborations, or other modifications represent, as a whole, an
+original work of authorship. For the purposes of this License, Derivative
+Works shall not include works that remain separable from, or merely link (or
+bind by name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original
+version of the Work and any modifications or additions to that Work or
+Derivative Works thereof, that is intentionally submitted to Licensor for
+inclusion in the Work by the copyright owner or by an individual or Legal
+Entity authorized to submit on behalf of the copyright owner. For the purposes
+of this definition, "submitted" means any form of electronic, verbal, or
+written communication sent to the Licensor or its representatives, including
+but not limited to communication on electronic mailing lists, source code
+control systems, and issue tracking systems that are managed by, or on behalf
+of, the Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise designated
+in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf
+of whom a Contribution has been received by Licensor and subsequently
+incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this
+License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable copyright license to
+reproduce, prepare Derivative Works of, publicly display, publicly perform,
+sublicense, and distribute the Work and such Derivative Works in Source or
+Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this
+License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this
+section) patent license to make, have made, use, offer to sell, sell, import,
+and otherwise transfer the Work, where such license applies only to those
+patent claims licensable by such Contributor that are necessarily infringed by
+their Contribution(s) alone or by combination of their Contribution(s) with the
+Work to which such Contribution(s) was submitted. If You institute patent
+litigation against any entity (including a cross-claim or counterclaim in a
+lawsuit) alleging that the Work or a Contribution incorporated within the Work
+constitutes direct or contributory patent infringement, then any patent
+licenses granted to You under this License for that Work shall terminate as of
+the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or
+Derivative Works thereof in any medium, with or without modifications, and in
+Source or Object form, provided that You meet the following conditions:
+
+(a) You must give any other recipients of the Work or Derivative Works a copy
+of this License; and
+
+(b) You must cause any modified files to carry prominent notices stating that
+You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works that You
+distribute, all copyright, patent, trademark, and attribution notices from the
+Source form of the Work, excluding those notices that do not pertain to any
+part of the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its distribution, then
+any Derivative Works that You distribute must include a readable copy of the
+attribution notices contained within such NOTICE file, excluding those notices
+that do not pertain to any part of the Derivative Works, in at least one of
+the following places: within a NOTICE text file distributed as part of the
+Derivative Works; within the Source form or documentation, if provided along
+with the Derivative Works; or, within a display generated by the Derivative
+Works, if and wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and do not modify the
+License. You may add Your own attribution notices within Derivative Works that
+You distribute, alongside or as an addendum to the NOTICE text from the Work,
+provided that such additional attribution notices cannot be construed as
+modifying the License.
+
+You may add Your own copyright statement to Your modifications and may provide
+additional or different license terms and conditions for use, reproduction, or
+distribution of Your modifications, or for any such Derivative Works as a
+whole, provided Your use, reproduction, and distribution of the Work otherwise
+complies with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any
+Contribution intentionally submitted for inclusion in the Work by You to the
+Licensor shall be under the terms and conditions of this License, without any
+additional terms or conditions. Notwithstanding the above, nothing herein shall
+supersede or modify the terms of any separate license agreement you may have
+executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names,
+trademarks, service marks, or product names of the Licensor, except as required
+for reasonable and customary use in describing the origin of the Work and
+reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in
+writing, Licensor provides the Work (and each Contributor provides its
+Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied, including, without limitation, any warranties
+or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any risks
+associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in
+tort (including negligence), contract, or otherwise, unless required by
+applicable law (such as deliberate and grossly negligent acts) or agreed to in
+writing, shall any Contributor be liable to You for damages, including any
+direct, indirect, special, incidental, or consequential damages of any
+character arising as a result of this License or out of the use or inability to
+use the Work (including but not limited to damages for loss of goodwill, work
+stoppage, computer failure or malfunction, or any and all other commercial
+damages or losses), even if such Contributor has been advised of the
+possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or
+Derivative Works thereof, You may choose to offer, and charge a fee for,
+acceptance of support, warranty, indemnity, or other liability obligations
+and/or rights consistent with this License. However, in accepting such
+obligations, You may act only on Your own behalf and on Your sole
+responsibility, not on behalf of any other Contributor, and only if You agree
+to indemnify, defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason of your
+accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following boilerplate
+notice, with the fields enclosed by brackets "[]" replaced with your own
+identifying information. (Don't include the brackets!) The text should be
+enclosed in the appropriate comment syntax for the file format. We also
+recommend that a file or class name and description of purpose be included on
+the same "printed page" as the copyright notice for easier identification
+within third-party archives.
+
+Copyright 2026 Meigma
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.