@iowarp/clio-coder 0.4.5 → 0.4.6

package/CHANGELOG.md

@@ -2,6 +2,30 @@
 
 All notable changes to Clio Coder are documented in this file. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and versions follow Semantic Versioning; pre-1.0 minor releases may include incompatible changes.
 
+## 0.4.6 - 2026-09-08
+
+This release restores reliable setup with Quick Connect and simplifies the terminal transcript with three consistent output styles. New users can connect a model and start working, while existing users retain their saved settings and can inspect more detail when needed.
+
+### Added
+- Make Quick Connect the first launcher option, with Settings and Diagnostics alongside it. Connect an endpoint, supply a key when needed, filter the live model list, review, and Connect. A single model skips selection; reconnecting preserves existing preferences and fleet assignments. Add `--quick` and `--settings` shortcuts.
+
+### Changed
+- Simplify rendering to Compact, Standard (default), and Detailed output styles. Alt+O cycles the session; Settings saves a default. Accept legacy output preferences and retire `/output` with migration guidance.
+- Bound reasoning, shell output, diffs, and worker previews after terminal wrapping. Inspect full available content through `/view transcript`; keep failures and validation outcomes visible in every style.
+- Give the footer sole ownership of live activity, with accurate concurrent-tool state and background worker counts. Remove separate reasoning, tool expansion, and live-output toggles.
+- Simplify the README around installation, the first session, scientific software, and HPC. Keep advanced configuration and multi-agent workflows in collapsible sections, and expand dependency and integration acknowledgements.
+- Use one worker, no prompt prewarm, and automatic TTY streaming as shipped defaults. Preserve explicitly saved values and document the full recommended default policy.
+- Check the ACP registry version against package metadata during release audits, and make version alignment and issue reconciliation explicit release-cut steps.
+
+### Fixed
+- Preserve every own JSON measurement field in numerical verification, including names inherited by ordinary JavaScript objects. Mismatched measurements can no longer disappear during parsing and produce a false pass in ordinary or host verification (#332).
+- Fix `configure` exiting successfully at the first question after an arrow-key menu. Scope readline to active questions, use arrow selectors and editable text fields for settings, and preserve menu position on Back.
+- Use the canonical autonomy levels in the configuration menu, so saved choices match the settings schema and existing `full-auto` configurations open on the correct selection.
+- Share the target wizard across first setup, Add, and Edit, with a review and explicit Save. Preserve existing role defaults, credential references, and capability overrides; reject duplicate target ids and allow clearing model overrides. Save pasted keys per target and review optional delegation peers after the primary setup is saved.
+- Authenticate generic OpenAI- and Anthropic-compatible discovery probes with the resolved target credential, including a pasted key before the target is saved.
+- Add `configure --edit` and All Settings for validated editing of the complete user settings schema, including repair of malformed YAML, a previous-file backup, and protection against overwriting concurrent changes.
+- Keep configuration inspection and upgrade dry runs from initializing user state. Give reset explicit setup/reconnection guidance and simplify the source installer's next step to `clio-coder configure`.
+
 ## 0.4.5 - 2026-09-07
 
 ### Added

package/CONTRIBUTING.md

@@ -95,22 +95,23 @@ historical record, not a reusable current checklist.
 
 1. During development, keep the top changelog section at `## Unreleased`. A
    maintainer collects release work on a **local-only** compact candidate
-   branch (`v043` for `v0.4.3`) and bumps `version` there. Never push this
+   branch (`v046` for `v0.4.6`) and bumps `version` there. Never push this
    candidate branch to the canonical repository. Before the cut, retitle the
-   changelog section `## <version> - YYYY-MM-DD`.
+   changelog section `## <version> - YYYY-MM-DD`, align the ACP registry manifest
+   version, and update the README's install tag and release notices.
 2. Run `pnpm run ci:release` on the exact candidate. It runs the full `ci` gate,
    then `scripts/check-release.mjs`, which verifies the built `dist/` and
    audits the exact npm package contents.
 3. Fetch `origin`, require the fetched `origin/main` to be the candidate's
-   ancestor, then fast-forward local `main` with `git merge --ff-only v043`.
+   ancestor, then fast-forward local `main` with `git merge --ff-only v046`.
    Re-run the release gate if the candidate changed and verify local `main`
    equals the reviewed candidate SHA.
 4. Fetch once more and stop on unexpected movement. With explicit maintainer
    authorization, push only `refs/heads/main:refs/heads/main`; no topic or
    release-candidate branch is pushed to canonical `origin`.
 5. Require CI for that exact `main` SHA to pass. Create the annotated tag on
-   that commit and push only it: `git tag -a v0.4.3` followed by
-   `git push origin refs/tags/v0.4.3`. The tag must match `package.json`; the
+   that commit and push only it: `git tag -a v0.4.6` followed by
+   `git push origin refs/tags/v0.4.6`. The tag must match `package.json`; the
    release workflow refuses mismatches.
 6. `.github/workflows/release.yml` verifies the tag against `package.json`,
    runs `pnpm run ci:release` on the tagged tree, and creates the GitHub release
@@ -118,7 +119,11 @@ historical record, not a reusable current checklist.
    body. It does not publish to npm.
 7. A maintainer publishes from the tagged commit with `npm publish`;
    `prepublishOnly` runs the same `ci:release` gate in release mode first.
-8. Verify the release and tag, then delete the local compact candidate branch.
+8. Verify the release and tag. Reconcile milestone tickets against tagged
+   implementation and acceptance evidence; plain issue references and release
+   tags do not close tickets. Verify automatic closures, explicitly close
+   completed tickets that remain open, and carry incomplete work forward before
+   closing the milestone. Then delete the local compact candidate branch.
    The canonical remote returns to its steady state: `main` plus immutable
    release tags and GitHub releases, with no release branch.
 
@@ -210,8 +215,8 @@ Examples:
 - `docs/github-governance`
 
 Maintainer branches are local-only. A temporary release candidate uses the
-compact version spelling with no dots: `v043` for release tag `v0.4.3`. Never
-create or push a branch named `v0.4.3`; dotted `vX.Y.Z` names belong exclusively
+compact version spelling with no dots: `v046` for release tag `v0.4.6`. Never
+create or push a branch named `v0.4.6`; dotted `vX.Y.Z` names belong exclusively
 to immutable release tags. The compact branch is local scaffolding and is
 deleted after its reviewed commit reaches `main` and the release succeeds.
 
@@ -244,7 +249,7 @@ verification and teardown safely. After a PR is merged or a release is tagged:
    `refs/heads/main`; every additional head is a cleanup failure.
 
 For a release, first verify `refs/tags/vX.Y.Z^{commit}` equals the reviewed
-commit on `main`, then close the compact candidate branch such as `v043`.
+commit on `main`, then close the compact candidate branch such as `v046`.
 Published tags are never deleted, moved, or recreated during cleanup.
 
 ## Commits

package/NOTICE

@@ -8,6 +8,22 @@ Illinois Institute of Technology.
 Licensed under the Apache License, Version 2.0. See the LICENSE file
 distributed with this work for the full license text.
 
+--------------------------------------------------------------------
+Technology acknowledgements
+
+Clio Coder builds on Earendil Works' Pi framework and, for optional Claude
+workers, Anthropic's Claude Agent SDK. Its runtime and development tools
+include Node.js, TypeScript, node-pty, Tree-sitter, Ollama's JavaScript
+client, esbuild, tsup, and Biome. The source GUI uses React, Deno, Vite,
+and community libraries for Markdown, diagrams, syntax highlighting,
+sanitization, images, and fonts.
+
+We thank these projects and their maintainers. Exact dependencies and
+versions are recorded in the package manifests and pnpm-lock.yaml;
+third-party components retain their upstream copyrights and licenses.
+README.md also acknowledges the optional inference and tool integrations
+that operators can connect to Clio.
+
 --------------------------------------------------------------------
 Pinned external tools