@simonesiega/codex-limits 1.0.0 → 1.2.0

package/CHANGELOG.md

@@ -16,6 +16,51 @@ All notable changes to codex-limits are documented in this file.
 
 ### Security
 
+## [1.2.0] - 2026-08-09
+
+### Added
+
+- Added a project Code of Conduct with private reporting and enforcement guidance.
+- Added JSON Schemas and sanitized example documents for `codex-limits coupons --json` and `codex-limits doctor --json`.
+- Added `codex-limits agents uninstall` with interactive, named, multi-agent, and `--all` modes for removing recognized OpenCode, pi, and GitHub Copilot CLI integrations.
+- Added automated packed-package compatibility checks that install, load, dispatch, and uninstall `/codex-limits` integrations in real OpenCode, pi, and GitHub Copilot CLI releases.
+
+### Changed
+
+- Changed the npm package description to include cross-platform CLI and agent integration support.
+
+### Fixed
+
+- Fixed OpenCode TUI plugin discovery in current hosts by exposing the loader-reserved `@simonesiega/codex-limits/tui` alias.
+- Fixed malformed coupon counters outside JavaScript's safe-integer range to be reported as partial data instead of reaching public output.
+
+### Security
+
+- Kept agent removal scoped to recognized Codex Limits registrations, revalidating bounded mutation targets before changing them and refusing stale, malformed, symbolic-link, or unrecognized targets while preserving unrelated agent configuration.
+- Hardened local session discovery against sessions-directory replacement races, pinned affected development dependencies to patched `fast-uri` 3.1.5 and `undici` 8.10.0 releases, and added dependency audits to CI and publishing.
+
+## [1.1.0] - 2026-07-31
+
+### Added
+
+- Added explicit OpenCode, pi, and GitHub Copilot CLI package subpath exports while keeping the package root dedicated to OpenCode loading and the internal core private.
+
+### Changed
+
+- Changed package safety messaging to distinguish read-only inspection commands from the explicitly confirmed `reset` remote mutation.
+- Changed packed-runtime checks to validate the packed CLI on macOS with Node.js 22.
+
+### Fixed
+
+- Fixed packed-package validation for canonical temporary-directory paths on macOS.
+- Fixed inconsistent reset-coupon counts to be reported as partial data instead of complete availability.
+- Fixed agent summaries to label unknown usage percentages as unknown instead of displaying them as 0%.
+
+### Security
+
+- Kept usage endpoint metadata and coupon redemption identifiers outside the combined limits data supplied to read-only TUI and agent renderers, and enforced resolved-path containment for local state reads.
+- Bounded pi integration filter matching against adversarial configuration patterns and updated the locked `brace-expansion` dependency to a non-vulnerable release.
+
 ## [1.0.0] - 2026-07-23
 
 ### Added
@@ -43,25 +88,13 @@ All notable changes to codex-limits are documented in this file.
 
 ## [0.1.6] - 2026-07-22
 
-### Breaking Changes
-
 ### Added
 
 - Added `codex-limits doctor` and `codex-limits doctor --json` for safe environment, connectivity, local usage, authentication, OpenCode, and pi integration diagnostics.
 - Added the pi agent integration with `codex-limits agents install pi` and a read-only `/codex-limits` overlay that does not send limit data to the LLM.
 
-### Changed
-
-### Fixed
-
-### Removed
-
-### Security
-
 ## [0.1.5] - 2026-07-22
 
-### Breaking Changes
-
 ### Added
 
 - Added bundled third-party license notices to published package artifacts.
@@ -81,8 +114,6 @@ All notable changes to codex-limits are documented in this file.
 - Fixed weekly-only usage data to use declared window durations across live and local sources, avoid stale local fallback for recognized live windows, and omit unavailable 5-hour sections from terminal dashboards and the OpenCode integration.
 - Fixed clean production builds and kept terminal rendering compatible with Node.js 20.
 
-### Removed
-
 ### Security
 
 - Refused symbolic-link files and path-replacement races when reading bounded local files, including agent configurations.

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,120 @@
+<p align="center">
+  <img src="docs/photos/logo/logo.png" alt="codex-limits logo" width="180" />
+</p>
+
+<h1 align="center">
+  Codex Limits Code of Conduct
+</h1>
+
+<p align="center">
+  Community standards for a respectful, inclusive, and constructive project.
+</p>
+
+<p align="center">
+  <img src="https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa" alt="Contributor Covenant version 2.1" />
+  <img src="https://img.shields.io/badge/Community-respectful-brightgreen" alt="Respectful community" />
+</p>
+
+## Contents
+
+- [Our pledge](#our-pledge)
+- [Expected behavior](#expected-behavior)
+- [Unacceptable behavior](#unacceptable-behavior)
+- [Scope](#scope)
+- [Reporting a conduct issue](#reporting-a-conduct-issue)
+- [Enforcement responsibilities](#enforcement-responsibilities)
+- [Enforcement guidelines](#enforcement-guidelines)
+- [Attribution](#attribution)
+- [Related documentation](#related-documentation)
+
+## Our pledge
+
+We pledge to make participation in the Codex Limits community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socioeconomic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Expected behavior
+
+Examples of behavior that contributes to a positive community include:
+
+| Behavior                   | What it means                                                                              |
+| -------------------------- | ------------------------------------------------------------------------------------------ |
+| Be respectful              | Treat contributors, users, and maintainers with patience and consideration.                |
+| Be constructive            | Give actionable feedback and focus criticism on ideas, code, and outcomes.                 |
+| Be collaborative           | Share relevant context, listen to other viewpoints, and work toward consensus.             |
+| Be accountable             | Accept responsibility, apologize when appropriate, and learn from mistakes.                |
+| Protect privacy and safety | Use sanitized examples and respect the project's security and redaction rules.             |
+| Respect project boundaries | Respect documented decisions about scope, compatibility, safety, and contribution process. |
+
+## Unacceptable behavior
+
+The following behavior is not acceptable:
+
+- harassment, intimidation, stalking, threats, or discriminatory language or imagery;
+- sexualized language, imagery, or attention, including unwelcome advances;
+- trolling, insulting or derogatory comments, personal attacks, or sustained disruption;
+- publishing another person's private information without explicit permission;
+- exposing credentials, private Codex data, private paths, or other sensitive information;
+- pressuring anyone to disclose personal, employment, account, or security information;
+- deliberately disrupting issues, Pull Requests, reviews, releases, or other project work;
+- retaliation against anyone who reports a concern or participates in an investigation;
+- other conduct that would reasonably be considered inappropriate in a professional setting.
+
+## Scope
+
+This Code of Conduct applies in all project spaces, including:
+
+- GitHub issues, Pull Requests, reviews, discussions, and repository content;
+- project-related email and other direct communication;
+- community events or conversations where someone is representing Codex Limits;
+- public spaces when an individual is acting as an official project representative.
+
+Representation includes using an official project account, posting from an official channel, or acting with delegated project authority.
+
+## Reporting a conduct issue
+
+Report abusive, harassing, or otherwise unacceptable behavior privately by emailing [simonesiega1@gmail.com](mailto:simonesiega1@gmail.com) with the subject `Codex Limits conduct report`. Do not open a public issue for a private conduct report.
+
+Include only the information needed to understand and review the concern:
+
+| Field              | What to include                                                      |
+| ------------------ | -------------------------------------------------------------------- |
+| Summary            | A concise description of what happened.                              |
+| Location and date  | Where and approximately when the behavior occurred.                  |
+| Supporting context | Relevant links, quotations, or sanitized screenshots when available. |
+| Requested outcome  | Any immediate safety concern or resolution you want considered.      |
+
+All reports will be reviewed as promptly and fairly as reasonably possible. The maintainer will respect the privacy and security of the reporter and affected parties, sharing information only when necessary to investigate or respond.
+
+If the report concerns the project maintainer or cannot safely be reported by email, use GitHub's [Report Abuse form](https://support.github.com/contact/report-abuse). Security vulnerabilities should instead follow the private process in [`SECURITY.md`](SECURITY.md#reporting-a-vulnerability).
+
+## Enforcement responsibilities
+
+Project maintainers are responsible for clarifying and enforcing these standards. They may remove, edit, or reject comments, commits, code, issues, Pull Requests, and other contributions that do not align with this Code of Conduct.
+
+Maintainers will communicate moderation decisions when appropriate and will not publicly identify a reporter without permission unless required by law or necessary to address an immediate safety risk.
+
+## Enforcement guidelines
+
+Maintainers will use these guidelines when determining consequences for behavior that violates this Code of Conduct:
+
+| Level | Consequence   | Community impact                                                                | Response                                                                                                     |
+| ----- | ------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| 1     | Correction    | Inappropriate language or behavior with limited impact.                         | A private explanation of the violation and a request for correction; a public apology may be requested.      |
+| 2     | Warning       | A single serious incident or repeated behavior after correction.                | A formal warning with conditions against further contact or specified behavior for a defined period.         |
+| 3     | Temporary ban | Sustained or serious violations, including continued inappropriate behavior.    | Temporary exclusion from project interaction and public or private communication with involved participants. |
+| 4     | Permanent ban | A pattern of violations, harassment, threats, or aggression toward individuals. | Permanent exclusion from project spaces and community interaction.                                           |
+
+Enforcement decisions will consider context, severity, impact, prior behavior, and the safety of the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html), available under the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/).
+
+The enforcement guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+## Related documentation
+
+- Read [`CONTRIBUTING.md`](CONTRIBUTING.md) for contribution workflow and review expectations.
+- Read [`SECURITY.md`](SECURITY.md) for private vulnerability reporting and project safety boundaries.
+- Use the [documentation hub](docs/README.md) to find product, automation, agent, and development guides.

package/CONTRIBUTING.md

@@ -18,7 +18,7 @@
     <img src="https://img.shields.io/github/issues/simonesiega/codex-limits" alt="Open issues" />
 </p>
 
-Read [`README.md`](README.md) first, then use the [documentation hub](docs/README.md) to find the canonical guide for the area you plan to change.
+Read [`README.md`](README.md) first, follow the [`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md) in every project interaction, then use the [documentation hub](docs/README.md) to find the canonical guide for the area you plan to change.
 
 ## Contents
 
@@ -39,13 +39,13 @@ Read [`README.md`](README.md) first, then use the [documentation hub](docs/READM
 
 If you are new to the project, read [`README.md`](README.md) and the [documentation hub](docs/README.md), then choose one focused issue or improvement.
 
-| Step | Action                                          |
-| ---- | ----------------------------------------------- |
-| 1    | Fork the repository.                            |
-| 2    | Create a branch from `main`.                    |
-| 3    | Make one focused change.                        |
-| 4    | Run the local checks.                           |
-| 5    | Open a Pull Request with context and rationale. |
+| Step | Action                                                                                                 |
+| ---- | ------------------------------------------------------------------------------------------------------ |
+| 1    | Fork the repository.                                                                                   |
+| 2    | Create a branch from `main`.                                                                           |
+| 3    | Make one focused change.                                                                               |
+| 4    | Run the local checks.                                                                                  |
+| 5    | Open a [Pull Request](https://github.com/simonesiega/codex-limits/compare) with context and rationale. |
 
 ## Branch naming
 
@@ -59,9 +59,9 @@ If you are new to the project, read [`README.md`](README.md) and the [documentat
 
 ## Issues
 
-Before opening a new issue, check existing [Issues](https://github.com/simonesiega/codex-limits/issues) to avoid duplicates.
+Before opening a new issue, check existing [Issues](https://github.com/simonesiega/codex-limits/issues) to avoid duplicates. Then use the [issue chooser](https://github.com/simonesiega/codex-limits/issues/new/choose) to open the bug-report or feature-request form. Security vulnerabilities must use the private process in [`SECURITY.md`](SECURITY.md#reporting-a-vulnerability), not a public issue.
 
-Please include:
+The issue forms prompt for:
 
 | Field               | Why it matters                                           |
 | ------------------- | -------------------------------------------------------- |
@@ -110,6 +110,12 @@ bun run docs:link
 bun run docs:schema
 ```
 
+Audit the locked dependency graph:
+
+```bash
+bun run audit
+```
+
 Run tests only:
 
 ```bash
@@ -122,6 +128,8 @@ Build the package:
 bun run build
 ```
 
+The `Check` workflow also runs `bun run agents:compat` against packed artifacts in real OpenCode, pi, and GitHub Copilot CLI installations. These Linux-only probes intentionally live outside the normal local `bun run check` gate because they download and launch external host releases; see [Compatibility](docs/readme/compatibility.md#tested-environments) for the current version matrix.
+
 ## Code guidelines
 
 Keep changes small, readable, and easy to review.
@@ -138,39 +146,28 @@ When adding a CLI command, create a focused command module and register it in `s
 
 ## Safety rules
 
-`codex-limits` treats local Codex data as read-only and should remain safe by default.
+[`SECURITY.md`](SECURITY.md#local-data-and-network-behavior) is the canonical reference for local-data, network, redaction, installer, diagnostic, and reset-mutation safeguards. Contributors must preserve those boundaries and use only synthetic or redacted values in output, tests, documentation, and screenshots.
 
-Do not print, log, snapshot, or commit:
-
-- access tokens;
-- account IDs;
-- auth headers;
-- cookies;
-- raw local Codex files;
-- private environment values.
-
-If a change touches local data discovery, live coupon data, warnings, output formatting, or agent integrations, make sure sensitive values are redacted before they can reach the CLI, TUI, JSON output, tests, or screenshots.
-
-Command handlers should let the router replace unexpected exceptions with their fixed command failure message. Use `AgentInstallError` only for bounded, deliberately user-safe adapter messages; never pass through a raw filesystem, network, or credential error.
+Command handlers should let the router replace unexpected exceptions with their fixed command failure message. Use `AgentInstallError` or `AgentUninstallError` only for bounded, deliberately user-safe adapter messages; never pass through a raw filesystem, network, or credential error.
 
 ## Adding a new agent
 
 New agents should use the same small adapter shape as [`src/agents/opencode`](src/agents/opencode), [`src/agents/pi`](src/agents/pi), and [`src/agents/copilot`](src/agents/copilot): `format.ts`, `install.ts`, `integration.ts`, and `plugin.ts`. Put reusable presentation and safe configuration behavior in `src/agents/shared`.
 
-| Step | Action                                                                                                                          |
-| ---- | ------------------------------------------------------------------------------------------------------------------------------- |
-| 1    | Create `src/agents/<agent-name>` with the standard four-file adapter layout.                                                    |
-| 2    | Define metadata, optional environment help, `install`, and `inspect` in `integration.ts`.                                       |
-| 3    | Keep `plugin.ts` focused on the target host API and load Codex data only through the shared package core.                       |
-| 4    | Register the integration descriptor once in `src/agents/index.ts`; shared install and doctor commands consume it automatically. |
-| 5    | Add installer, formatter, and host-behavior tests. When end-to-end automation is impractical, document the manual validation.   |
-| 6    | Add `docs/readme/agents/<agent-name>.md`.                                                                                       |
-| 7    | Add the integration to [Agent Integrations](docs/readme/agent-integrations.md).                                                 |
-| 8    | Update the README supported-agent summary and any target-specific package/build metadata.                                       |
-| 9    | Add or update screenshots when the visual output changes.                                                                       |
-| 10   | Run the documentation link and schema checks.                                                                                   |
-
-The goal of every integration is the same: show Codex limit information quickly, safely, and without sending unnecessary work to the LLM.
+| Step | Action                                                                                                                              |
+| ---- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| 1    | Create `src/agents/<agent-name>` with the standard four-file adapter layout.                                                        |
+| 2    | Define metadata, optional environment help, `install`, `uninstall`, and `inspect` in `integration.ts`.                              |
+| 3    | Keep `plugin.ts` focused on the target host API and load Codex data only through the shared package core.                           |
+| 4    | Register the integration descriptor once in `src/agents/index.ts`; shared lifecycle and doctor commands consume it automatically.   |
+| 5    | Add install, conservative uninstall, formatter, and host-behavior tests. Document manual validation when automation is impractical. |
+| 6    | Add `docs/readme/agents/<agent-name>.md`.                                                                                           |
+| 7    | Add the integration to [Agent Integrations](docs/readme/agent-integrations.md).                                                     |
+| 8    | Add `src/package/<agent-name>.ts`, its host-only `./<agent-name>` subpath, and the shared package-build metadata.                   |
+| 9    | Add or update screenshots when the visual output changes.                                                                           |
+| 10   | Run the documentation link and schema checks.                                                                                       |
+
+The goal of every integration is the same: show Codex limit information quickly and safely without sending the request or limit data to the LLM.
 
 ## Documentation changes
 
@@ -181,7 +178,9 @@ Keep documentation changes consistent with these rules:
 - use relative links for files in this repository;
 - keep commands executable from their documented working directory;
 - keep heading anchors stable when another file links to them;
-- synchronize JSON examples with `docs/schema/codex-limits.schema.json`;
+- keep deep safety behavior in [`SECURITY.md`](SECURITY.md), support requirements in [Compatibility](docs/readme/compatibility.md), cross-surface diagnosis in [Troubleshooting](docs/readme/troubleshooting.md), and agent-specific setup, removal, and troubleshooting in the matching guide under [`docs/readme/agents`](docs/readme/agents);
+- summarize and link to the canonical guide instead of copying its detailed procedures or guarantees;
+- synchronize every external and inline JSON example with its corresponding schema under `docs/schema`; `bun run docs:schema` enforces the linked examples in `docs/readme/json-output.md`;
 - use descriptive image alt text and sanitized screenshots;
 - never include tokens, account IDs, cookies, authorization headers, private paths, environment contents, or raw Codex files.
 
@@ -196,11 +195,13 @@ Documentation-only changes do not require unrelated runtime changes, but the com
 
 ## Pull request checklist
 
-Before requesting review, verify:
+Opening a Pull Request loads the repository's [Pull Request template](.github/pull_request_template.md). Complete its summary, related-issue, validation, and screenshot sections before requesting review.
+
+Then verify:
 
 - [ ] The PR title and description explain what changed and why.
 - [ ] The change is focused and does not include unrelated cleanup.
-- [ ] `bun run format` was run and `bun run check` passes locally.
+- [ ] `bun run format` was run and both `bun run audit` and `bun run check` pass locally.
 - [ ] Tests were added or updated for behavior changes.
 - [ ] Documentation was updated if commands, setup, output, or agent support changed.
 - [ ] No secrets, account data, tokens, cookies, or raw local files were committed.
@@ -214,7 +215,9 @@ Please follow the private reporting process in [`SECURITY.md`](./SECURITY.md).
 
 ## Community guidelines
 
-Be clear, respectful, and constructive in issues, Pull Requests, and reviews. Good contributions are focused, tested, documented, and easy to understand.
+Every project interaction is governed by the [`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md). Be clear, respectful, and constructive in issues, Pull Requests, and reviews. Report conduct concerns through its private reporting process rather than opening a public issue.
+
+Good contributions are focused, tested, documented, and easy to understand.
 
 ## Contact