boost-skill-cli 1.2.39__tar.gz → 1.2.41__tar.gz

boost_skill_cli-1.2.41/GOVERNANCE.md

@@ -0,0 +1,103 @@
+# Governance
+
+How boost makes decisions, who makes them, and what happens when people
+disagree. [MAINTAINERS.md](MAINTAINERS.md) is the companion: it lists who holds
+which role and which credential. This file is about the *process*.
+
+## The short version
+
+boost is a **single-maintainer project** run in the open. The lead maintainer
+decides; everything that shapes a decision — the roadmap, the quality gates, the
+reasoning behind a change — is public and arguable before it lands. That is a
+benevolent-dictator model, and naming it plainly is better than implying a
+committee that does not exist.
+
+This is stated as the current state, not an aspiration. It changes when a second
+maintainer is appointed under
+[MAINTAINERS.md](MAINTAINERS.md#becoming-a-maintainer), and this file changes
+with it.
+
+## How a decision gets made
+
+**1. Anyone may propose.** Open an issue, or open a pull request. There is no
+membership requirement and no form to fill in.
+
+**2. The argument happens in public, on the artifact.** Issues, pull requests,
+and the roadmap boards. A decision made in a private channel is not a decision
+this project recognises; if something was settled elsewhere, it gets written
+down in the open before it is acted on.
+
+**3. The gates decide what they can.** A large class of decisions is not a
+matter of opinion here — the change either passes the required checks or it does
+not. Coverage, mutation score, retrieval quality, the lint and type gates, the
+generated-file freshness checks: these are stated thresholds, and a maintainer
+does not get to wave one through. Changing a *threshold* is itself a decision
+that goes through this process, in its own pull request, with the measurement
+that justifies it.
+
+**4. The lead maintainer decides what the gates cannot.** Scope, design,
+priority, and whether a proposal fits the project at all. The decision is
+recorded where the work is: in the pull request, or as a roadmap card.
+
+**5. A "no" is recorded, not dropped.** The roadmap has a `declined` status
+precisely so a rejected proposal stops reading as backlog. Without it the same
+refuted question gets re-opened by the next person — or the next agent — who
+scans the board for work. If your proposal is declined you get the reason in
+writing, and it stays there.
+
+## Disagreements
+
+**With a decision.** Say so on the issue or pull request. Bring the thing that
+would change the answer: a measurement, a failing case, a constraint that was
+missed. This project changes its mind on evidence and says so when it does —
+several roadmap cards exist specifically to record that an earlier claim was
+wrong.
+
+**With the process, or with a person.** Conduct concerns go through the private
+reporting route in [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md), never a public
+issue.
+
+**When you cannot reach agreement.** With a single maintainer there is no appeal
+body, and pretending otherwise would be dishonest. The real backstop is the
+licence: boost is Apache-2.0 with full public history, so anyone who thinks the
+project is being run badly can fork it and prove it. That is a genuine check on
+the maintainer, not a consolation prize.
+
+## What is deliberately not decided by discussion
+
+Some things are settled by rule, and a pull request arguing the opposite gets
+declined on sight unless it changes the rule first:
+
+- **The runtime imports no third-party package.** Enforced by `import-linter`.
+- **Generated files are never hand-edited.** `registries.json`, both roadmap
+  boards, `commands.html`. Edit the source and regenerate.
+- **A suppressed finding needs a written argument**, naming what would have to
+  change for the suppression to stop being true. See
+  [`docs/dependencies.md`](docs/dependencies.md).
+- **A badge answer or a security claim must be checkable.** If the evidence
+  needs credentials nobody reading has, the claim gets softened to what *is*
+  checkable rather than asserted.
+
+## Roadmap and priority
+
+Priority is public and data-driven. Both boards are generated from one file per
+item under `docs/roadmap/items/`, so proposing work is a pull request adding a
+card, and claiming work is a pull request setting `status` and `owner` on one.
+Two people claiming different items touch different files and merge cleanly; two
+claiming the *same* item conflict on that one small file, which is the intended
+"already claimed" signal — first to merge wins.
+
+There is no private backlog. What is on the boards is what is planned.
+
+## Releases
+
+Every merge to `main` cuts a release. There is no release manager, no release
+meeting, and no window: the decision to release *is* the decision to merge.
+Consequences of that are set out in [SUPPORT.md](SUPPORT.md) — only the latest
+release is supported — and in
+[`docs/verifying-releases.md`](docs/verifying-releases.md), which is how you
+check that a release came from this repository.
+
+## Changing this document
+
+Like anything else: a pull request, argued in public, merged through the gates.

boost_skill_cli-1.2.41/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 Jonathan Michael Reyes and the boost contributors
+
+   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.

boost_skill_cli-1.2.41/MAINTAINERS.md

@@ -0,0 +1,102 @@
+# Maintainers
+
+Who has access to what, what each role is expected to do, and what has to
+happen before anyone is granted more. This file is the authoritative list; if it
+disagrees with someone's memory, this file is right and the memory is stale.
+
+## Current maintainers
+
+| Name | GitHub | Role | Since |
+|---|---|---|---|
+| Jonathan Reyes | [@jonnyeclectic](https://github.com/jonnyeclectic) | Lead maintainer | 2026-07 |
+
+boost is a **single-maintainer project today**. That is stated plainly rather
+than glossed, because it is the single largest risk to the project and it
+changes what you should expect: review latency depends on one person, and the
+bus factor is one. See [Continuity](#continuity) for what happens if that
+person becomes unavailable, and [Becoming a maintainer](#becoming-a-maintainer)
+for how that changes.
+
+## Access to sensitive resources
+
+Every credential and privileged surface the project depends on, and who holds
+it. Nothing not listed here grants access to anything.
+
+| Resource | Who has access | How access works |
+|---|---|---|
+| GitHub repository (admin) | Lead maintainer | GitHub account with 2FA |
+| `main` branch | **No one directly.** | A ruleset requires a pull request and the full required-check gate; `non_fast_forward` blocks history rewrites. Admin included. |
+| PyPI project `boost-skill-cli` | **No stored credential exists.** | Publishing is a [PyPI Trusted Publisher](https://docs.pypi.org/trusted-publishers/): GitHub mints a short-lived OIDC token for `publish.yml` on `main` only. There is no API token to leak, share, or rotate. |
+| GitHub Actions secrets | Lead maintainer | Only optional dashboard tokens (`CODECOV_TOKEN`, `SONAR_TOKEN`) and optional evaluation API keys. Every job reading one skips itself when it is absent, so none is required to build, test, or release. |
+| Security advisories / private vulnerability reports | Lead maintainer | GitHub private vulnerability reporting |
+| GitHub Pages docs site | Lead maintainer | Published from `main` by CI; no separate credential |
+
+## Roles and responsibilities
+
+**Lead maintainer.** Sets direction; reviews and merges pull requests; owns the
+release process; is the recipient of private vulnerability reports and owns the
+response; administers repository settings, branch rulesets and the required-check
+list; maintains this file.
+
+**Maintainer** (none appointed yet). Reviews and merges pull requests within an
+agreed area; may not change repository settings, rulesets, or the release path.
+A maintainer is expected to keep the quality gates green rather than route
+around them, and to say so publicly when a gate is wrong instead of disabling it
+quietly.
+
+**Contributor.** Anyone who opens a pull request. No standing permissions; a
+contribution is merged by a maintainer after the gates pass. See
+[CONTRIBUTING.md](CONTRIBUTING.md).
+
+**Security reporter.** Anyone who reports a vulnerability through the process in
+[SECURITY.md](SECURITY.md). Reporters are credited by name in the advisory and
+the release notes unless they ask not to be.
+
+## Becoming a maintainer
+
+Escalated permission is granted deliberately and never by default. The policy:
+
+1. **A track record first.** A sustained series of merged, non-trivial
+   contributions — enough that their judgement on this codebase is a known
+   quantity, not an assumption.
+2. **Review before the grant.** The lead maintainer reviews that history and
+   proposes the change in a public issue, naming the scope of access being
+   granted and why. Existing maintainers may object there.
+3. **Least privilege at the grant.** New collaborators receive the lowest
+   permission that lets them do the job. Write access is a separate, later
+   decision from repository administration, which is a separate decision again
+   from anything touching the release path.
+4. **This file is updated in the same change** that grants the permission. An
+   access grant that is not recorded here has not happened.
+
+The same review applies when an existing maintainer is given more access, not
+only to a first grant.
+
+## Removing access
+
+Access is removed promptly when a maintainer steps down, becomes unreachable for
+an extended period, or at their own request — and immediately if an account is
+believed compromised. Removal does not require agreement from the person losing
+access. Because publishing uses a short-lived OIDC identity rather than a stored
+token, removing someone's GitHub access removes their ability to release; there
+is no separate credential left behind to revoke.
+
+## Continuity
+
+If the lead maintainer becomes unavailable:
+
+- **The code is safe regardless.** It is Apache-2.0, the full history is public,
+  and every release is reproducible from a public tag. Anyone may fork.
+- **The published artifacts stay published.** PyPI releases and GitHub releases
+  remain available; nothing expires if no one logs in.
+- **Recovery of the canonical repository** would go through
+  [GitHub's account-recovery and inactive-repository processes](https://docs.github.com/en/site-policy).
+  Because the release path is a GitHub OIDC identity bound to this repository,
+  whoever legitimately controls the repository controls releases — there is no
+  personal token that has to be handed over.
+- **The practical answer is to fork.** Until a second maintainer exists, that
+  is the honest continuity plan, and the project would rather say so than
+  imply a succession process it does not have.
+
+Reducing this risk is open work: if you have been contributing and want to help
+carry it, say so in an issue.