rigplane 2.0.0__tar.gz → 2.0.2__tar.gz

rigplane-2.0.2/.claude/skills/release/SKILL.md

@@ -0,0 +1,250 @@
+---
+name: release
+description: Cut and publish a rigplane PyPI release — version bump, changelog, tag, GitHub Release that triggers publish.yml. Use when the user asks to release, cut a tag, ship a patch/minor/major, or publish to PyPI.
+argument-hint: "patch | minor | major | X.Y.Z [--dry-run]"
+---
+
+# Release rigplane-core
+
+Cuts and publishes a release of the `rigplane` Python package to PyPI via the existing `publish.yml` workflow. Tailored to this repo's specifics: pure Python + Svelte/TS frontend, no Rust workspace, dynamic `__version__` via `importlib.metadata`, CHANGELOG symlinked from root, asymmetric CI gates.
+
+**Arguments:**
+- `patch` / `minor` / `major` — bump type (auto-suggest if omitted)
+- Explicit version like `2.0.2`
+- `--dry-run` — preview only; no edits, no commit, no push
+
+User-facing prompts in Russian. Commits / CHANGELOG / tags / release notes in English.
+
+---
+
+## Step 1 — Determine target version
+
+1. Read current version from `pyproject.toml` line 7: `version = "..."`. **This is the only source of truth.** Do NOT read or modify `src/rigplane/__init__.py` (it derives `__version__` from `importlib.metadata.version("rigplane")`); do NOT modify `src/icom_lan/__init__.py` (deprecation shim).
+2. Get previous tag: `git tag --list 'v*' --sort=-version:refname | head -1`.
+3. If no bump argument passed, **auto-suggest**:
+   - `git log vPREV..HEAD --no-merges --format='%s'`
+   - Any line with `BREAKING CHANGE` or `^\w+!:` → MAJOR
+   - Else any `feat(...)?:` or `feat:` → MINOR
+   - Else → PATCH
+   - Show suggestion: `Suggested: vX.Y.Z (PATCH — N fix commits, M feat, K breaking)`. Ask accept/override.
+4. Compute `NEW_VERSION` from bump type.
+
+## Step 2 — Pre-flight checks
+
+Match `publish.yml`'s `validate` job exactly so green pre-flight = green publish. Run sequentially. STOP on first failure.
+
+```bash
+# 2a. Clean tree
+git status --porcelain
+```
+Any output → stop.
+
+```bash
+# 2b. On main
+git branch --show-current
+```
+Not `main` → warn, ask confirmation.
+
+```bash
+# 2c. Sync deps
+uv sync --extra dev --extra bridge
+```
+
+```bash
+# 2d. Lint + format
+uv run ruff check src/ tests/
+uv run ruff format --check src/ tests/
+```
+
+```bash
+# 2e. Architecture gate
+uv run lint-imports
+```
+
+```bash
+# 2f. Type check (CI scope: web boundary only)
+uv run mypy --strict src/rigplane/web
+```
+
+```bash
+# 2g. Frontend gate
+cd frontend
+npm ci
+npm run check
+npx vitest run
+npm run build
+cd ..
+```
+
+```bash
+# 2h. Python tests
+uv run pytest tests/ --ignore=tests/integration -n auto --tb=short --timeout=300 --timeout-method=thread
+```
+
+```bash
+# 2i. Build smoke
+uv build && rm -rf dist/
+```
+
+```bash
+# 2j. Optional regression check (.claude/commands/regression-check.md)
+```
+
+```bash
+# 2k. Warn-only: prior FAILED issues in .claude/queue/history.json
+```
+
+Report: "All pre-flight checks passed ✓" and continue.
+
+## Step 3 — Generate CHANGELOG content
+
+**Canonical file:** `docs/CHANGELOG.md`. The repo-root `CHANGELOG.md` is a **symlink** — never write through the symlink; always edit `docs/CHANGELOG.md`.
+
+1. Read `## [Unreleased]` section. If non-empty, use as-is.
+2. If empty → auto-generate from `git log vPREV..HEAD --no-merges --format='%s%n%b%n---'`:
+   - `feat(...)?:` / `feat!:` → **Added**
+   - `refactor(...)?:` / `perf(...)?:` → **Changed**
+   - `fix(...)?:` / `fix!:` → **Fixed**
+   - `docs(...)?:` → **Docs**
+   - `chore|test|build|ci(...)?:` → skip unless scope is clearly user-facing
+   - Other → **Other**
+   - `!:` or `BREAKING CHANGE:` body marker → **Breaking changes** sub-section at top
+3. Strip type prefix; preserve `(#NNN)` issue refs and short SHAs. Match v2.0.1 entry style:
+   ```
+   - LAN TX audio bridge: fix audio not flowing in transmit direction (#1434, ba364e54)
+   ```
+4. Present draft inline:
+   ```
+   Draft CHANGELOG entries for vNEW (auto-generated from N commits).
+   Edit in place, or press Enter to accept.
+   ```
+
+## Step 4 — Preview plan (FIRST confirmation gate)
+
+Show consolidated preview:
+
+```
+Release plan for vNEW:
+
+  Bump:           vCURRENT → vNEW (TYPE)
+  Commits:        N (X feat, Y fix, Z other)
+  Files to edit:  pyproject.toml, docs/CHANGELOG.md
+  Changelog:      [counts] Added / Changed / Fixed entries
+  Tag:            vNEW
+  Push target:    origin/main (atomic --follow-tags)
+  GH release:     gh release create vNEW (triggers publish.yml → PyPI)
+
+  Dry-run: [yes/no]
+```
+
+Ask: **Proceed with version bump, changelog update, and local commit?** Single yes/no.
+
+## Step 5 — Apply edits (local only)
+
+1. **`pyproject.toml`** — `version = "OLD"` → `version = "NEW"` (line 7).
+2. **`docs/CHANGELOG.md`** — note: edit `docs/CHANGELOG.md` directly, NOT root `CHANGELOG.md` (symlink).
+   - Keep `## [Unreleased]` header (now empty) at top.
+   - Insert below: `## [NEW] — YYYY-MM-DD` with grouped sections from Step 3.
+   - Footer: update `[Unreleased]: https://github.com/rigplane/rigplane-core/compare/vNEW...HEAD`. Insert `[NEW]: https://github.com/rigplane/rigplane-core/compare/vPREV...vNEW`.
+   - **First-run repair**: if footer is missing entries for `[2.0.0]` and `[2.0.1]`, backfill with `https://github.com/rigplane/rigplane-core` URLs. Do NOT rewrite older `morozsm/icom-lan` URLs (GitHub auto-redirects).
+
+**Files NOT to touch:**
+- `src/rigplane/__init__.py` — `__version__` is dynamic via `importlib.metadata`
+- `src/icom_lan/__init__.py` — deprecation shim, no version
+- `CLAUDE.md` — no Version row exists post-rebrand
+- `frontend/package.json` — `private: true`, currently `2.0.0` (cosmetic; leave unless explicitly asked)
+- No `RELEASE_NOTES.md` — file is no longer used; pass changelog to `gh release create` via tempfile
+
+## Step 6 — Commit + tag
+
+```bash
+git add pyproject.toml docs/CHANGELOG.md
+git commit -m "chore(release): bump to NEW — <one-line summary>"
+git tag -a vNEW -m "Release NEW"
+```
+
+Show `git show HEAD --stat` and `git tag -l vNEW`.
+
+## Step 7 — Push and publish (SECOND confirmation gate)
+
+Ask once: **Push commit + tag to origin and create GitHub release?** On `no` → stop; print rollback. On `yes`:
+
+```bash
+git push --follow-tags
+```
+
+Failure → stop. On success:
+
+```bash
+NOTES=$(mktemp)
+# Extract the [NEW] section from docs/CHANGELOG.md to $NOTES
+gh release create vNEW --notes-file "$NOTES" --title "NEW"
+rm -f "$NOTES"
+```
+
+**State explicitly that `gh release create` is what triggers `publish.yml` (`on: release: published`); pushing the tag alone does NOT publish to PyPI.**
+
+Print release URL.
+
+## Step 8 — Post-release housekeeping
+
+1. Update `.claude/metrics.json`: `releases_count` += 1, `last_release_version = "NEW"`.
+2. Append to `.claude/workflow/release-notes.md`: version, date, commit count, headline.
+3. Print monitor link: `https://github.com/rigplane/rigplane-core/actions`.
+
+## Step 9 — Summary
+
+```
+Release vNEW complete.
+
+  version bump:   NEW (pyproject.toml)
+  CHANGELOG:      docs/CHANGELOG.md updated
+  Git tag:        vNEW
+  GitHub release: <URL>
+  Commits since vPREV: N
+
+CI will now:
+  - publish.yml → PyPI
+  - docs.yml → docs deploy
+
+Monitor: https://github.com/rigplane/rigplane-core/actions
+```
+
+---
+
+## Error recovery
+
+Print these verbatim when a step fails. Never auto-rollback.
+
+**Commit created but tag failed or not yet pushed:**
+```bash
+git reset --hard HEAD~1
+git tag -d vNEW  # if tag was created
+```
+
+**Commit + tag created locally, push failed:**
+```bash
+git tag -d vNEW
+git reset --hard HEAD~1
+```
+
+**Push succeeded but GitHub release failed:**
+```bash
+gh release create vNEW --notes-file <path-to-extracted-changelog-section> --title "NEW"
+```
+
+**Fully undo a pushed release:**
+```bash
+gh release delete vNEW --yes
+git push --delete origin vNEW
+git tag -d vNEW
+git revert HEAD  # or git push --force-with-lease (dangerous; ask first)
+```
+
+---
+
+## Notes for the operator
+
+- This skill replaces the old global `Release icom-lan` slash command (`.claude/commands/release.md`), which had stale references to `src/icom_lan/__init__.py` (a shim, never canonical), `RELEASE_NOTES.md` (no longer used), `CLAUDE.md` Version row (no longer exists), and root `CHANGELOG.md` (symlink — must edit `docs/CHANGELOG.md`).
+- Match `publish.yml`'s `validate` job exactly. If CI's validate gate changes, update Step 2.
+- For Pro releases (Tauri shell), use the `release` skill in `rigplane-pro` (different beast — single-tag-then-handoff to operator's Mac terminal, not single-shot publish).

{rigplane-2.0.0 → rigplane-2.0.2}/.github/scripts/check-rebrand-allowlist.sh

@@ -71,6 +71,9 @@ ALLOWLIST=(
     # Workflow definition for the gate: references the pattern in its
     # job description.
     '.github/workflows/rebrand-gate.yml'
+    # Release skill documents src/icom_lan/__init__.py shim as DO-NOT-TOUCH
+    # (deprecation shim — must not be modified during version bumps).
+    '.claude/skills/release/SKILL.md'
 )
 
 # Collect all files matching brand pattern.

{rigplane-2.0.0 → rigplane-2.0.2}/.gitignore

@@ -34,8 +34,9 @@ node_modules/
 
 # Local config & tools
 config/
-.claude/
+.claude/*
 !.claude/commands/
+!.claude/skills/
 .kombai/
 .firecrawl/
 .playwright-mcp/
@@ -47,6 +48,7 @@ rigs/.backups/
 
 # Internal dev artifacts (AI agent workspace, plans, strategies)
 AGENTS.md
+!AGENTS.md
 ROADMAP_TESTING.md
 
 # Internal docs (development-only, not published)

rigplane-2.0.2/AGENTS.md

@@ -0,0 +1,73 @@
+# AGENTS.md — rigplane-core
+
+## Repo identity
+
+This repository is the public open-core `rigplane` implementation.
+
+- Repository: `rigplane/rigplane-core`
+- License: MIT, unless a file says otherwise
+- Project board: https://github.com/orgs/rigplane/projects/2
+
+## Public/open-core boundary
+
+Everything in this repository should be safe to publish as open-core work:
+
+- protocol correctness;
+- generic radio control features;
+- transports and backends;
+- public SDK/API improvements;
+- generic local web UI improvements;
+- tests and docs useful to the community.
+
+Do not add proprietary, customer-specific, hosted-account, premium workflow, or
+private service integration code here. Those belong in `rigplane-pro`.
+
+If a task mixes public and proprietary scope, split it:
+
+- generic API/protocol/backend work stays here;
+- product workflow, packaging, account/device, and support automation go to
+  `rigplane-pro`.
+
+## GitHub Project workflow
+
+Use the GitHub Project as the development control plane for non-trivial work.
+
+- Project: `RigPlane Core Roadmap`
+- URL: https://github.com/orgs/rigplane/projects/2
+- Repository: `rigplane/rigplane-core`
+
+Default rule for agents:
+
+- Do not start non-trivial implementation from chat context alone.
+- Work from a GitHub issue that has acceptance criteria.
+- Add the issue to `RigPlane Core Roadmap` if it is missing.
+- Keep Project fields current while working:
+  - `Status`: `Todo`, `In Progress`, `Done`
+  - `WorkType`: `epic`, `feature`, `spike`, `bug`, `debt`, `docs`, `release`
+  - `Area`: `api`, `protocol`, `transport`, `rigctld`, `audio`,
+    `radio-models`, `web-ui`, `cli`, `docs`, `ci`, `release`, `architecture`
+  - `Priority`: `P0`, `P1`, `P2`, `P3`
+  - `Phase`: `inbox`, `spec`, `alpha`, `beta`, `stable`, `post-release`,
+    `backlog`
+  - `Owner`: `human`, `codex`, `mixed`
+  - `Risk`: `low`, `medium`, `high`
+  - `Size`: `S`, `M`, `L`
+- Treat issue bodies as the source of truth for requirements, acceptance
+  criteria, compatibility decisions, and test expectations.
+- Treat Project fields as routing/status metadata only.
+- Before opening a PR, confirm the linked issue is in the Project and update
+  `Status` to `In Progress` or `Done` as appropriate.
+
+See `docs/internals/github-project-workflow.md` for the exact CLI and UI
+workflow.
+
+## Engineering rules
+
+- Follow `CLAUDE.md` for commands, architecture, testing, and workflow gates.
+- Keep public API compatibility explicit. If a change breaks API, CLI, config,
+  rigctld wire behavior, or docs, call it out in the issue and PR.
+- Prefer tests before implementation for bugs and behavior changes.
+- Do not add new layers, abstractions, or broad refactors unless the issue
+  explicitly requires it.
+- Keep hardware-dependent work mockable where possible; otherwise mark the
+  issue as requiring human/hardware validation.

{rigplane-2.0.0 → rigplane-2.0.2}/CLAUDE.md

@@ -115,6 +115,12 @@ Incomplete → continue or FAILED. Never skip.
 
 ## Autonomous pipeline
 
+**GitHub Project control plane:** non-trivial work should be tracked in
+`RigPlane Core Roadmap` (https://github.com/orgs/rigplane/projects/2). Work
+from GitHub issues with acceptance criteria, add missing issues to the Project,
+and keep fields current while working. See
+`docs/internals/github-project-workflow.md`.
+
 Strictly linear. No phase may be skipped or reordered. No exceptions.
 State files (`.claude/workflow/*.md`) are the sole source of truth — not memory or reasoning.
 CLAUDE.md controls all workflow transitions. Agents must not self-direct transitions.

{rigplane-2.0.0 → rigplane-2.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rigplane
-Version: 2.0.0
+Version: 2.0.2
 Summary: Python library for controlling Icom transceivers over LAN (UDP) — no wfview/hamlib required
 Project-URL: Homepage, https://rigplane.dev/
 Project-URL: Documentation, https://rigplane.dev/
@@ -204,10 +204,10 @@ fair-use compatibility identification only — this project is not affiliated
 with, endorsed by, or sponsored by Icom.
 
 rigplane is the **open-core** half of a planned product split. A
-proprietary commercial layer (`rigplane-pro`) is under development and
-will integrate with this library through the public `Radio` protocol and
-the `local-extensions/` host API. Open-core constraints — no telemetry,
-headless mode is sacred, no hollowing out — are codified in
+proprietary commercial layer (`rigplane-pro`) is under active development
+and will integrate with this library through the public `Radio` protocol
+and the `local-extensions/` host API. Open-core constraints — no
+telemetry, headless mode is sacred, no hollowing out — are codified in
 [`docs/architecture/open-core-policy.md`](docs/architecture/open-core-policy.md).
 
 ## Status

{rigplane-2.0.0 → rigplane-2.0.2}/README.md

@@ -158,10 +158,10 @@ fair-use compatibility identification only — this project is not affiliated
 with, endorsed by, or sponsored by Icom.
 
 rigplane is the **open-core** half of a planned product split. A
-proprietary commercial layer (`rigplane-pro`) is under development and
-will integrate with this library through the public `Radio` protocol and
-the `local-extensions/` host API. Open-core constraints — no telemetry,
-headless mode is sacred, no hollowing out — are codified in
+proprietary commercial layer (`rigplane-pro`) is under active development
+and will integrate with this library through the public `Radio` protocol
+and the `local-extensions/` host API. Open-core constraints — no
+telemetry, headless mode is sacred, no hollowing out — are codified in
 [`docs/architecture/open-core-policy.md`](docs/architecture/open-core-policy.md).
 
 ## Status

{rigplane-2.0.0 → rigplane-2.0.2}/docs/CHANGELOG.md

@@ -7,6 +7,23 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.0.2] — 2026-05-06
+
+### Added
+- Tailored in-repo release skill (`.claude/skills/release/SKILL.md`) replacing the stale global slash command (#1436).
+
+### Fixed
+- Frontend e2e: closed pre-existing Wave 2 rebrand leak in `playwright.config.ts` and `v2-ui-interactive.impl.ts`; removed obsolete `ICOM_LAN_V2_URL` fallback (#1437).
+
+### Docs
+- IC-7610 WSJT-X TX level workaround for FT8/JS8/fldigi multi-peak waterfall (#1382, #1384).
+- GitHub Project workflow for Codex-style agents: `AGENTS.md`, project doc, `CLAUDE.md` link (#1431).
+
+## [2.0.1] — 2026-05-06
+
+### Fixed
+- LAN TX audio bridge: fix audio not flowing in transmit direction (#1434, ba364e54)
+
 ## [2.0.0] — 2026-05-05
 
 **Headline:** project renamed from `icom-lan` to **`rigplane`**. The old name was always misleading — the project shipped multi-vendor support (Icom CI-V, Yaesu CAT, Discovery TX-500, Xiegu X6200) over LAN, USB, and serial. Carrying "icom-lan" through a paid Pro tier also created a trademark risk on a vendor name we don't own. New brand at https://rigplane.dev.
@@ -1206,7 +1223,10 @@ These deprecation closures were announced in v0.19 and dropped on schedule.
 - Transport layer, authentication, CI-V commands, meters, PTT, keep-alive.
 - Clean-room Icom LAN UDP protocol implementation.
 
-[Unreleased]: https://github.com/morozsm/icom-lan/compare/v1.1.0...HEAD
+[Unreleased]: https://github.com/rigplane/rigplane-core/compare/v2.0.2...HEAD
+[2.0.2]: https://github.com/rigplane/rigplane-core/compare/v2.0.1...v2.0.2
+[2.0.1]: https://github.com/rigplane/rigplane-core/compare/v2.0.0...v2.0.1
+[2.0.0]: https://github.com/rigplane/rigplane-core/compare/v1.1.0...v2.0.0
 [1.1.0]: https://github.com/morozsm/icom-lan/compare/v1.0.1...v1.1.0
 [1.0.1]: https://github.com/morozsm/icom-lan/compare/v1.0.0...v1.0.1
 [1.0.0]: https://github.com/morozsm/icom-lan/compare/v0.19.0...v1.0.0

{rigplane-2.0.0 → rigplane-2.0.2}/docs/guide/ic7610-usb-setup.md

@@ -385,6 +385,33 @@ Use `rigplane --list-audio-devices` to find the correct indices.
 2. Check PTT is active before transmitting audio
 3. Verify `--tx-device` matches the USB audio device name
 
+### TX appears dirty / multiple peaks on waterfall during the first seconds
+
+**Symptom**: When transmitting from WSJT-X / JS8Call / fldigi via the USB Audio CODEC, the first 5–10 seconds of TX show on the waterfall (or a second receiver) as a "fat" carrier centred ~1500 Hz, or as several spurs spread across the audio passband. The signal then either settles into a clean tone, or never settles if the level is too high.
+
+**Cause**: IC-7610's USB audio input has less internal headroom before ALC compression than IC-7300 / FTX-1. With the WSJT-X power slider (the vertical slider on the right of the main window) at 100%, the FT8/JS8 tone clips inside the radio, producing IM3-style intermodulation products until ALC finds its working point. This is a hardware/firmware property of the IC-7610 USB CODEC — it occurs regardless of which CAT path (LAN, serial, direct rigctl) is used to control the radio, since the audio itself flows OS-level (WSJT-X → CoreAudio → USB Audio CODEC → radio) and never passes through RigPlane.
+
+**Fix**:
+
+1. **WSJT-X → main window → right-side TX power slider** → drop to **~20-25%** as a starting point.
+2. Optionally also reduce **Menu → Set → Connectors → MOD Level** on the radio to ~30%.
+3. PTT into FT8 / JS8 and verify on the waterfall: a single clean carrier at the FT8 audio centre, no spread peaks during the first seconds.
+
+!!! tip "Precise tuning with an external SWR/power meter"
+    A more precise way to find the optimal level — if you have an external SWR/power meter inline — is to dial the WSJT-X slider down while keying TX:
+
+    - Above the ALC threshold the radio's output power stays roughly **flat** as you reduce the slider, because ALC is compressing the overdrive.
+    - Continue lowering the slider until the **external meter starts to drop**.
+    - That's the point where ALC has stopped engaging. Set the slider at (or just slightly above) that level — that's the optimal clean drive: full rated output, no compression, no IM3 spurs.
+
+    This works because ALC behaves as a hard limiter: once you're below its threshold, output tracks input one-to-one again, so the meter "wakes up" at exactly the right level.
+
+!!! note "IC-7610 specific"
+    IC-7300 and FTX-1 tolerate the WSJT-X slider at 100% without this effect because their USB audio paths have more headroom. Don't apply this attenuation to those radios — it just costs you SNR.
+
+!!! tip "Verifying with a second receiver"
+    The cleanest way to confirm the fix is to monitor your TX on a second receiver (or a public web SDR — kiwisdr.com, websdr.org). Compare the waterfall during the first 10 seconds of TX at 100% slider vs 25% slider — the difference is unmistakable.
+
 ## Environment Variables
 
 For convenience, set these in your shell profile: