Point install examples at verified Direct v0.7.29 - #84
Merged
Merged
Conversation
The canonical release and exact-byte npm mirror now both pass readback, so new consumers can install the qualified semantic browser factory. Historical tags and release assets remain unchanged. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Member
Author
|
Delivered after exact-head check/Required and all CodeQL checks passed. The scheduled local release-contract suite also passed: 51 tests, 1,668 expectations. All public install examples now name the verified immutable v0.7.29 archive/skill and matching npm mirror. No released bytes or historical tags were changed. |
5 of 6 tasks
0thernet
added a commit
that referenced
this pull request
Oct 5, 2026
…cs (#85) ## Summary - **README: "Open a signed-in state without real credentials"** (under the article's verification walkthrough). Put sign-in behind a product port, declare `account.signed-in` and `account.signed-out` scenarios on `/settings`, and keep the identity provider as a `direct` coverage claim with no scenarios; open the state with `?__direct_scenario=account.signed-in`, confirm it from `window.__direct`, and keep Playwright saved auth state for the real sign-in. The definition was replayed against Direct's own source (`defineDirect` plus `createDirectSession` with query activation): each scenario opens, the manifest's `active` entry reports the scenario and `/settings`, and the coverage modes are `fixture`, `fixture`, `direct`. - **README: "Install the Agent Skill"** now lists, for Claude Code, Codex, Cursor, and Devin CLI, the global and project folders the skills installer writes and how to invoke the skill (`/direct`, `$direct` or `/skills`, the `/` menu). On 2026-10-04, skills 1.7.0 wrote these folders (the Claude Code and Devin CLI folders are links to the `.agents` copy) and Codex 0.160.0 listed the skill from both of its folders; the README says Claude Code, Cursor, and Devin CLI were not run with it. The install prompt says how to start it in each agent. - **Version bump to 0.7.30**, following `docs/publishing.md`: strictly increasing (v0.7.30 tag unused; Latest is v0.7.29), `CHANGELOG.md` `## 0.7.30` section, and the package identity test moved with `package.json`. Install examples stay on the delivered v0.7.29 until the new assets are live. Immutable releases are enabled and the two `refs/tags/v*` rulesets read back as documented. Between v0.7.29 and this head only docs changed, so the changelog says exports and tooling are unchanged. - The draft's line that called the semantic browser factory new in 0.7.30 was dropped; that factory shipped in 0.7.29. ## Release and hraness.com/direct steps after merge 1. Squash merge on green `Required`; `CI` on `main` passes; `auto-tag.yml` creates the annotated `v0.7.30` tag through the release tagger App. 2. The tag runs `release.yml`: full `bun run check`, isolated install, attestation, immutable five-asset GitHub Release "Direct v0.7.30", then the npm mirror through OIDC. Confirm the five assets, immutable Latest, and the npm readback separately. 3. Follow-up PR here (as in #84): move install examples in `README.md`, `docs/adoption.md`, `docs/publishing.md`, `docs/verification.md`, and `skills/direct/references/install.md` from v0.7.29 to v0.7.30. 4. In hraness/jungle (merge queue): change the catalog pin at `package.json:23` from `github:hraness/direct#v0.7.20` to `#v0.7.30`, regenerate `portfolio-inventory.generated.json` from `portfolio-inventory.fragment.json:476`, update the pinned strings in `projects/hraness/app/direct/page.test.tsx:40,43` and `scripts/standalone-tool-dependencies.test.ts:230`, refresh `bun.lock`, and check `projects/hraness/app/direct/launch/facts.ts:19` (v0.7.24 release URL). 5. After hraness.com deploys, `curl https://hraness.com/direct.md` and confirm the "When to use Direct" table, the two new sections, and the version string. ## Test plan - [ ] `host-run --mode=heavy --lane=compute -- bun run check` with npm 11.19.0 first on `PATH` (the repository's pinned npm); queued. An earlier run with the machine's npm 11.16.0 failed only the 12 historical `canonical npm package identity` cases on `npm 11.19.0 is required, received 11.16.0`. - [x] Offline replay of the README definition against `src/index.ts` and `src/testing/index.ts`. - [x] skills 1.7.0 global and project installs in isolated `HOME` folders (telemetry disabled); `codex debug prompt-input` lists `direct` from `~/.agents/skills` and `.agents/skills` without a model call. - [x] Read-only release controls: `gh api repos/hraness/direct/immutable-releases` (enabled), rulesets 19251098 and 21703866, `gh release list`, `git ls-remote --tags`. - [ ] Not run: the signed-in scenario in a browser or in `examples/todos` (the README sample is illustrative, not a shipped example); skill discovery or invocation in Claude Code, Cursor, or Devin CLI; the release itself. - [ ] Required CI on this head. --------- Co-authored-by: 0thernet <894119+0thernet@users.noreply.github.com> Co-authored-by: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Test plan
Generated with Devin