diff --git a/docs/execution.md b/docs/execution.md index 7a19c63..4029745 100644 --- a/docs/execution.md +++ b/docs/execution.md @@ -8,7 +8,7 @@ Preparing materials is not equivalent to completing an external validation gate. | 1. Maintainer problem interviews | Five candidate projects researched; bilingual questions and invitation drafts prepared | Five actual interviews and two recurring, relevant problems | | 2. External pilots | Self-serve guide and report form available | Three external attempts; at least two useful comparisons without author assistance | | 3. Correct repeated pilot friction | Engineering review added explicit next steps for unsupported, partial, and unassociated results | Two repeated pilot blockers corrected and rechecked by participants | -| 4. npm distribution | Alpha.3 published publicly; isolated registry install and npx demo passed with matching release integrity; exact GitHub Trusted Publisher configured | First successful OIDC publication and clean install of that release | +| 4. npm distribution | Alpha.3 published interactively; alpha.4 published by the configured GitHub Trusted Publisher; isolated public installation, npx demo, artifact integrity, signature and provenance passed | Complete for the public alpha distribution; use the explicit alpha tag | | 5. Broader native compatibility | Ubuntu 24.04 x64 candidate and production checks passed on Node 22/24; macOS production checks pass | Complete for the newly admitted Codex 0.166.0/Linux x64 tuple; other combinations remain outside the evidence | | 6. Two useful external cases | Interview and evidence-register formats prepared | Two participant-confirmed, approved public accounts of help with an actual problem | | 7. Demonstration and README | 42-second GIF/MP4 and transcript published; public assets were fetched and matched their local hashes | Complete for the synthetic demonstration; actual user cases remain task 6 | diff --git a/docs/npm-evidence/alpha4-publication.json b/docs/npm-evidence/alpha4-publication.json new file mode 100644 index 0000000..50bf8eb --- /dev/null +++ b/docs/npm-evidence/alpha4-publication.json @@ -0,0 +1,32 @@ +{ + "checkedAt": "2026-11-03T05:24:26.832894+00:00", + "package": "@hyscodebase/skillwhy", + "version": "0.1.0-alpha.4", + "publishedAt": "2026-11-03T05:23:14.792Z", + "sha256": "3eaccea5703eff5fe188fa18a3827344e18b7ab651bd9eb3fc458ad2113af53e", + "integrity": "sha512-zNow/nckNdXQ34I71D10efiAFnbzsKafthqEUKnLTwtla0YRC1FOggtNsa9IaBurRVUHcsFTbou9cFMvbDlptg==", + "registryBytesMatchGitHubRelease": true, + "dist-tags": { + "latest": "0.1.0-alpha.3", + "alpha": "0.1.0-alpha.4" + }, + "isolatedInstallVersion": "0.1.0-alpha.4", + "installedDemoStatus": "complete", + "isolatedNpxDemoMatchesInstalled": true, + "registrySignaturesVerified": true, + "provenanceAttestationsVerified": true, + "userConfig": "empty", + "globalConfig": "empty", + "runtime": "v24.8.0", + "npm": "11.11.0", + "githubSourceCommit": "3cea7e8fa1a0da0c891ec9e92afc4713d27d537d", + "publicationRun": "https://github.com/hyscodebase/skillwhy/actions/runs/41583232129", + "githubReleaseRun": "https://github.com/hyscodebase/skillwhy/actions/runs/41583223317", + "provenanceSourceMatchesReleaseTag": true, + "provenanceWorkflow": { + "ref": "refs/tags/v0.1.0-alpha.4", + "repository": "https://github.com/hyscodebase/skillwhy", + "path": ".github/workflows/npm-publish.yml" + }, + "platform": "darwin/arm64" +} diff --git a/docs/npm-publishing.md b/docs/npm-publishing.md index 0feeb95..e28847a 100644 --- a/docs/npm-publishing.md +++ b/docs/npm-publishing.md @@ -3,6 +3,10 @@ The public [npm package](https://www.npmjs.com/package/@hyscodebase/skillwhy) is available. The initial `0.1.0-alpha.3` publication and an isolated public registry installation were verified on 2026-11-03; see [the validation record](validation.md#public-npm-installation). +The subsequent `0.1.0-alpha.4` release was published by GitHub Actions OIDC, +installed publicly, and had its registry signature and provenance verified. +[Preserved evidence](npm-evidence/alpha4-publication.json) records its source commit, +workflow, integrity, and installation checks. Use `npx --yes @hyscodebase/skillwhy@alpha demo` for the offline demo. The package is published as `@hyscodebase/skillwhy`, with public access, an `alpha` @@ -66,9 +70,10 @@ when configuring the package; a successful dry run does not prove npm publishing authorization is configured. A newly created connection must complete its first successful publication within -2 days. The connection was saved on 2026-11-03; its first real OIDC publication is -still pending. Do not treat saving the form or a dry run as successful registry -authorization. Once a version is published, use a new version and tag for the +2 days. The connection was saved and validated on 2026-11-03 by the successful +[alpha.4 publication](https://github.com/hyscodebase/skillwhy/actions/runs/41583232129). +npm reports this connection as `Valid`. Saving the form or a dry run alone does +not establish successful registry authorization. Once a version is published, use a new version and tag for the next attempt that changes package contents; do not replace published versions. ## Availability after publication @@ -80,3 +85,11 @@ describes a typical delay of a few minutes, which can take longer. An immediate republished. Check the existing version and its integrity again before any retry. The initial alpha.3 request returned HTTP 202 and became publicly installable before the clean-install checks above. + +## Distribution tags + +Use the explicit `alpha` tag or an exact prerelease version. After the initial +publication npm also assigned `latest` to alpha.3. An authenticated attempt to +remove that tag returned HTTP 400, so it still points to alpha.3; alpha.4 is +available through `@alpha` and `@0.1.0-alpha.4`. The package has no stable release. +This tag state does not change the verified alpha.4 artifact or its provenance. diff --git a/docs/outreach.md b/docs/outreach.md index 5559fd5..e94b259 100644 --- a/docs/outreach.md +++ b/docs/outreach.md @@ -50,9 +50,9 @@ CLI 도구가 해결했다고 연결하지 않는다. C03에는 installer 문제 > > 새 Codex CLI 프로세스가 반환한 목록을 저장하고, 활성 상태·수집한 SKILL.md fingerprint 등의 차이를 보여줍니다. 지원 요청에는 전체 설정 대신 직접 고른 한 항목의 최소 파일을 만들 수 있습니다. 기본 공유 파일에는 이름·경로·본문·fingerprint가 제외되며 자동 업로드는 없습니다. > -> 현재 live capture는 **Codex CLI 0.166.0 / macOS arm64·Linux x64**를 지원합니다. Linux에서 실제 검증한 환경은 Ubuntu 24.04입니다. 기존 Desktop 세션이나 모델의 실제 skill 선택·실행은 검사하지 않습니다. Node.js 22+와 Git이 있으면 다음 합성 데모를 실행할 수 있습니다. 최초 실행에는 다운로드와 빌드가 필요하고, 데모에는 Codex나 API 키가 필요하지 않습니다. +> 현재 live capture는 **Codex CLI 0.166.0 / macOS arm64·Linux x64**를 지원합니다. Linux에서 실제 검증한 환경은 Ubuntu 24.04입니다. 기존 Desktop 세션이나 모델의 실제 skill 선택·실행은 검사하지 않습니다. Node.js 22+가 있으면 다음 합성 데모를 실행할 수 있습니다. 최초 실행에는 빌드된 npm 패키지를 다운로드하며, 데모에는 Codex나 API 키가 필요하지 않습니다. > -> `npx --yes github:hyscodebase/skillwhy#v0.1.0-alpha.3 demo` +> `npx --yes @hyscodebase/skillwhy@alpha demo` > > TypeScript로 작성했고 runtime dependency는 없습니다. native 발견 검증 자체를 새로 발명한 것은 아니며, 작은 비교 결과와 검토 가능한 공유 파일에 범위를 좁혔습니다. 아직 외부 파일럿 결과는 없습니다. 출력에서 “확인된 차이”와 “아직 모르는 것”이 잘 구분되는지 피드백을 받고 싶습니다. 원본 설정이나 snapshot을 올리지 않아도 됩니다. > @@ -74,11 +74,11 @@ CLI 도구가 해결했다고 연결하지 않는다. C03에는 installer 문제 > > The implementation is TypeScript with no runtime dependencies. One deliberate boundary is that discovery does not prove a model selected, read, or executed a skill. SkillWhy also does not inspect an existing Desktop session or choose a winner among same-name copies. > -> Live capture currently supports **Codex CLI 0.166.0 on macOS arm64 and Linux x64**, with Linux native checks on Ubuntu 24.04. For a synthetic demo, you need Node.js 22+ and Git, but no Codex installation or API key: +> Live capture currently supports **Codex CLI 0.166.0 on macOS arm64 and Linux x64**, with Linux native checks on Ubuntu 24.04. For a synthetic demo, you need Node.js 22+, but no Codex installation or API key: > -> `npx --yes github:hyscodebase/skillwhy#v0.1.0-alpha.3 demo` +> `npx --yes @hyscodebase/skillwhy@alpha demo` > -> The first run downloads and builds the tagged source. Code and instructions: https://github.com/hyscodebase/skillwhy +> The first run downloads the compiled npm package. Code and instructions: https://github.com/hyscodebase/skillwhy > > There are no completed external pilots yet. I'd appreciate feedback on whether the result makes observed differences and unknowns clear. If you've had a similar support problem, what information was missing from your existing tools? No raw snapshots or private configuration are needed. > diff --git a/docs/pilot.md b/docs/pilot.md index 04f8ed8..39da49b 100644 --- a/docs/pilot.md +++ b/docs/pilot.md @@ -5,13 +5,13 @@ not evidence of adoption or time saved. Stop after ten minutes, even if blocked. ## 1. Try the demo (about 2 minutes) -With Node.js 22 or later and Git: +With Node.js 22 or later: ```sh -npx --yes github:hyscodebase/skillwhy#v0.1.0-alpha.3 demo +npx --yes @hyscodebase/skillwhy@0.1.0-alpha.4 demo ``` -The initial download/build needs internet access. The synthetic demo needs no +The initial compiled-package download needs internet access. The synthetic demo needs no Codex, API key, or model call. **Demo-only feedback is welcome and is kept separate from live native observations.** Note your approximate time to first success. @@ -27,7 +27,7 @@ downgrade Codex for this pilot. If you do not already have SkillWhy installed, use the compiled release: ```sh -npm install --global https://github.com/hyscodebase/skillwhy/releases/download/v0.1.0-alpha.3/hyscodebase-skillwhy-0.1.0-alpha.3.tgz +npm install --global @hyscodebase/skillwhy@0.1.0-alpha.4 skillwhy --version ``` diff --git a/docs/validation.md b/docs/validation.md index 566d270..7595ec0 100644 --- a/docs/validation.md +++ b/docs/validation.md @@ -18,6 +18,29 @@ macOS arm64, with no registry login available to the installation process. This establishes public package distribution and the offline demo, rather than additional native Codex compatibility or external adoption. +### Alpha.4 OIDC publication + +The [npm distribution run 41583232129](https://github.com/hyscodebase/skillwhy/actions/runs/41583232129) +published `0.1.0-alpha.4` from tag `v0.1.0-alpha.4` at commit +`3cea7e8fa1a0da0c891ec9e92afc4713d27d537d`. The separate +[GitHub release run 41583223317](https://github.com/hyscodebase/skillwhy/actions/runs/41583223317) +passed its shared Node 22/24 Linux/macOS CI and published the compiled tarball. + +The public registry download and the GitHub release asset were byte-identical, +with SHA-256 `3eaccea5703eff5fe188fa18a3827344e18b7ab651bd9eb3fc458ad2113af53e`. +A new temporary prefix and cache with empty user/global npm configs installed +`@alpha` as `0.1.0-alpha.4`. Its version command, installed JSON demo, and the +README's `npx --yes @hyscodebase/skillwhy@alpha demo --json` route passed on +macOS arm64, Node 24.8.0, npm 11.11.0. + +`npm audit signatures` reported one verified registry signature and one verified +attestation. The verified SLSA provenance's subject digest matched the tarball; +its source commit, tag ref, workflow path, and invocation matched the run above. +The npm Trusted Publisher now reports `Valid`. The +[sanitized publication record](npm-evidence/alpha4-publication.json) preserves +these checks without login credentials or local paths. These observations do +not constitute additional live native support or external pilot outcomes. + ## Alpha.3 native support investigation After extracting the production compatibility manifest, the existing macOS arm64