v1.1.0

v1.1.0 Release Notes

Version 1.1.0 adds public checkout/task APIs and portable Context support.
The user approved the stable release through the existing protected workflow.
These source notes describe the implementation and pre-release evidence;
registry publication and channel state require the workflow's independent
registry/provenance readback, not the existence of this document.

Changes

• Portable Codex/Claude plugins bundle the Context runtime, consent/setup
  bridge, Java references and checker without requiring a source checkout.
• Shared guidance prioritizes unresolved decisions that change implementation,
  reuses approved choices, and handles explanation/cancellation without a fixed
  mandatory question sequence. The existing public interview V1 remains intact.
• Project rules use an explicitly approved, current-checkout-only connection.
  New context scope inspection/bind/unbind commands do not infer scope from
  directory names, branches or the sole available rule.
• New context task --session <handle> inspection/resume/preview/end commands
  connect an explicitly selected task to one checkout and host session. New
  sessions do not inherit the checkout's last task.
• Preview and delivery share complete PH-block rendering limits. Multi-target
  changes use consistent snapshots and fail closed rather than partially
  dropping required rules. Missing profiles/scopes are reported honestly.
• Project configuration and personal profile reads are bounded and no-follow.
  Profile mutations use one exclusive lock across read/decision/publication;
  concurrent writers fail closed with a busy result instead of losing history.

Preservation

Existing profile V1 records, approval history, explicit Context opt-out,
unrelated user configuration and Workflow Integrity/Finish authority remain
unchanged. Project/task bindings are separate private records, not profile
migrations. Corrupt, mismatched or symlinked bindings fail closed. Automatic
hooks do not write settings or grant execution authority. Normal host trust and
write approvals still apply. No host model/provider/authentication defaults are
changed by this release.

Evidence

Before version reconciliation, the final implementation passed integration
tests (26 files, 200 tests), focused distribution/skill/test contracts (16
tests), typecheck, generated-plugin checks, docs taxonomy and npm-installed
package smoke including task resume/Preview/end and new-session isolation.
After version reconciliation, 1.1.0 generated plugins, docs taxonomy and
npm run test:package passed again. The package check actually packed and
installed 1.1.0 and exercised its public CLI and bundled plugin contracts;
unchanged integration tests were not repeated just for the version change.

Isolated Codex CLI 0.153.4 observations used gpt-5.6-luna with reasoning max.
They covered material questions and answer-dependent follow-ups, explanation
and cancellation, approved personal/project rules, resume/compaction with a
profile update, and explicit task resume with task Preview before editing.
The last task observation produced a repeatable Java test, ended its binding,
left no background terminals, preserved profile/config/project binding bytes,
and passed independent fresh compilation plus 14 boundary cases. These are
synthetic local workflows, not independent-user acceptance.

Limits

• Claude has shared implementation and package/manifest evidence only; actual
  Claude model behavior was excluded by the user's updated scope.
• Task completion/switch detection and end are model instructions, not host
  enforcement. A missed end can leave a same-session binding; deleting one
  cannot retract context already read by a model.
• Earlier observations included direct profile/observer reads, a first edit
  before noticing an updated rule, and JShell processes requiring manual stop.
  Later successes do not erase those observations or prove universal behavior.
• The latest task model read the bridge implementation and needed normal
  one-time approvals for resume/end writes. Its test output used a fixed
  temporary directory, a remaining example-isolation limitation.
• Limits cover the full PH block, not every simultaneous host/plugin message.
  No universal first-edit, compaction or per-subagent isolation is claimed.
• Token experiments were stopped at user request. No savings claim is made.
• The evidence above is workspace/local-tarball and isolated installed-host
  evidence, not public registry smoke. Independent acceptance and protected
  workflow results are recorded against their exact source/artifact identity;
  prior historical acceptance records are not evidence for these changes.
• Generated-app product quality is not certified by this release.

The source checkout intentionally has no consumer project profile/workflow
state. It was not initialized merely to manufacture lifecycle evidence.

---

Release Status

This GitHub Release records v1.1.0 for the latest npm release
path. The governed publish workflow is the only route that can publish the
matching package to latest; registry and provenance readback record that
separate completion step.

Automation Metadata

• Source release notes: docs/current/release/v1.1.0-release-notes.md
• Package version: 1.1.0
• Tag: v1.1.0
• Intended npm dist-tag: latest
• Acceptance results index: docs/current/acceptance-results/README.md

Claim Boundaries

This GitHub release body is generated from the repository release notes. It does
not add token-saving, provider-token-saving, product-efficacy,
navigation-benefit, app-quality, full-TDD/test-sufficiency, CodeGraph/LSP
default/effectiveness, broad reliability, closure guarantee, Codex support,
code-nav replacement, or automatic downgrade/removal claims.

The governed workflows, not this prose, verify source/tag/package identity and
registry/provenance readback.