Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -350,16 +350,20 @@ jobs:
run: npm publish "${TARBALL_PATH}" --access public --provenance

- name: Verify registry metadata, shasum, and dist-tag (bounded propagation retry)
timeout-minutes: 35
run: |
set -euo pipefail
# npm scans uploads before making them installable; processing can
# exceed 15 minutes. Wait at most 30 minutes, then still fail closed.
# https://github.blog/changelog/2026-07-28-npm-publish-time-malware-scanning-and-dual-use-metadata/
seen=0
for attempt in $(seq 1 30); do
for attempt in $(seq 1 90); do
if npm view "@cynrath/agent-context-kit@${RELEASE_VERSION}" version > /dev/null 2>&1; then
seen=1
break
fi
echo "attempt ${attempt}/30: published version not visible yet; waiting 10s"
sleep 10
echo "attempt ${attempt}/90: npm package processing or propagation pending; waiting 20s"
sleep 20
done
if [ "${seen}" -ne 1 ]; then
echo "::error::published version never became visible on the registry"
Expand Down
12 changes: 6 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# ACKit — AgentContextKit

Check notice on line 1 in README.md

View workflow job for this annotation

GitHub Actions / action smoke (uses ./)

ACKIT040: context-heavy file (~8946 estimated tokens)

<p align="center">
<a href="https://www.npmjs.com/package/@cynrath/agent-context-kit"><img src="https://img.shields.io/npm/v/@cynrath/agent-context-kit?label=npm&color=0B84FF&style=for-the-badge" alt="npm version"></a>
Expand Down Expand Up @@ -187,11 +187,11 @@
```bash
# global (recommended)
npm install --global @cynrath/agent-context-kit
ackit --version # 0.5.4
ackit --version # 0.5.5

# one-shot, pinned
npx --yes @cynrath/agent-context-kit@0.5.4 --version
npx --yes @cynrath/agent-context-kit@0.5.4 --help
npx --yes @cynrath/agent-context-kit@0.5.5 --version
npx --yes @cynrath/agent-context-kit@0.5.5 --help

# from source
pnpm install --frozen-lockfile && pnpm build
Expand Down Expand Up @@ -321,7 +321,7 @@

### 🤖 GitHub Action

Official `Cynrath/agent-context-kit@v0.5.4` (SHA-pinned for high-assurance):
Official `Cynrath/agent-context-kit@v0.5.5` (pin the release commit for high assurance):

```yaml
permissions:
Expand All @@ -331,7 +331,7 @@
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@f548e57e544e1ff5a4c46bf1e1b8685f8e4a348a
- uses: Cynrath/agent-context-kit@v0.5.4
- uses: Cynrath/agent-context-kit@v0.5.5
with:
command: scan
args: "--json"
Expand Down Expand Up @@ -456,7 +456,7 @@

### 🔖 Versioning

Development: **`0.5.5`** on `master` · Latest stable: **`0.5.4`** · [Changelog](CHANGELOG.md) · [Releases](https://github.com/Cynrath/agent-context-kit/releases/latest) · `latest → 0.5.4` via OIDC Trusted Publishing with provenance. Stable pointer: [`release-state.json`](release-state.json). Legacy `.NET/NuGet 1.0.0-rc.1` at `258918b` is frozen.
Development: **`0.5.5`** on `master` · Latest stable: **`0.5.5`** · [Changelog](CHANGELOG.md) · [Releases](https://github.com/Cynrath/agent-context-kit/releases/latest) · `latest → 0.5.5` via OIDC Trusted Publishing with provenance. Stable pointer: [`release-state.json`](release-state.json). Legacy `.NET/NuGet 1.0.0-rc.1` at `258918b` is frozen.

---

Expand Down
2 changes: 1 addition & 1 deletion docs/guides/agent-integration.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ duplicates.
## Managed-asset lifecycle (init → sync)

> Availability: `ackit sync` is RELEASED in `0.4.0` and ships in published npm
> `@cynrath/agent-context-kit@0.5.4`.
> `@cynrath/agent-context-kit@0.5.5`.

`ackit init` is the first-time onboarding; `ackit sync` is the later,
version-aware reconciliation. Both run on the same ownership engine — the
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/context7-docs7.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ By default, an owned Context7 library may say **Config source: Configuration is

Avoid switching blindly: existing dashboard exclusions may differ from the repository file. The repository config intentionally indexes maintained feature docs and the README, not archived tasks or generated content. Leave **Index every version, old ones too** disabled unless historical-version docs are explicitly required.

Never commit Context7 API tokens, npm credentials or other secrets. If this library is ever unclaimed by an owner, use the [official claim process](https://context7.com/docs/howto/claiming-libraries) only then.
Never commit Context7 API tokens, npm credentials or other secrets. If this library is ever unclaimed by an owner, use the [official claim process](https://context7.com/docs/howto/claiming-libraries) only then. Copy the exact per-library `url` and `public_key` from that library's **Claim Library** dialog in the owner's Context7 panel; never invent a key or reuse another library's challenge. Existing ownership needs no new challenge.

## 3. Apply for the verified badge

Expand Down
2 changes: 1 addition & 1 deletion docs/guides/feature-index.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# ACKit feature reference (v0.5.4)
# ACKit feature reference (v0.5.5)

This index covers the documented, implemented ACKit surfaces. The [CLI reference](../reference/cli.md), [SDK reference](../reference/sdk.md), [MCP reference](../reference/mcp.md) and [README](../../README.md) are authoritative for exact contracts. This index does not claim features beyond the current published code.

Expand Down
8 changes: 4 additions & 4 deletions docs/guides/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,17 +14,17 @@ npm install --global @cynrath/agent-context-kit
ackit --version
```

One-shot usage: `npx --yes @cynrath/agent-context-kit@0.5.4 --help` (pinned to stable `0.5.4`).
One-shot usage: `npx --yes @cynrath/agent-context-kit@0.5.5 --help` (pinned to stable `0.5.5`).

From a source checkout instead:

```bash
pnpm install --frozen-lockfile
pnpm build
node dist/cli/index.js --version # 0.5.4
node dist/cli/index.js --version # 0.5.5
```

## 30-second tour (verified commands — stable v0.5.4)
## 30-second tour (verified commands — stable v0.5.5)

Fastest check (no install): `npx --yes @cynrath/agent-context-kit@latest readiness` — scores the current repository 0–100 with actionable findings.

Expand All @@ -38,7 +38,7 @@ ackit optimize --explain # 8-class advisor with waste estimates
ackit pack --profile codex --max-tokens 50000 # provider-aware pack
ackit diagnostics --json # env/config/instructions/cache/policy/tasks
ackit dashboard --port 0 --open # localhost-only dashboard
ackit task "first task" # docs-first task with tool-allocated id
ackit task create "first task" # docs-first task with tool-allocated id
```

Deeper references: `docs/concepts/readiness.md` · `docs/reference/readiness.md` · `docs/guides/ci.md` · `docs/guides/watch-dashboard.md` · `docs/guides/vscode.md` · `docs/reference/sdk.md`.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: "TASK-0097"
title: "Context7 ownership-ready configuration and Docs7 documentation distribution"
status: blocked
status: pending
schemaVersion: 2
dependencies: []
createdAt: "2026-10-15"
Expand Down Expand Up @@ -36,10 +36,10 @@ Expose the maintained ACKit documentation to Context7 and prepare Docs7 hosting

## Acceptance criteria

- [ ] Repository metadata and exclusions match official Context7 schema.
- [ ] Docs7 schema and navigated paths match actual docs; existing pages remain source of truth.
- [ ] Claim instructions require exact per-library public key from the owner's Context7 panel.
- [ ] Existing hosting and released package identities are unchanged.
- [x] Repository metadata and exclusions match official Context7 schema.
- [x] Docs7 schema and navigated paths match actual docs; existing pages remain source of truth.
- [x] Claim instructions require exact per-library public key from the owner's Context7 panel.
- [x] Existing hosting and released package identities are unchanged.
- [ ] Validated by repository checks, PR CI and Docs7 production build; external verification clearly recorded.
- [ ] Release decision follows repository release governance and only occurs after complete evidence.

Expand Down Expand Up @@ -70,6 +70,13 @@ Revert the documentation/configuration PR; keep historical tags/releases untouch

## Completion notes

Current status: external ownership and production proof are now available.
The conditional claim-key instruction has been clarified without adding any
challenge or credential. Exact-head validation of this documentation follow-up
is still required before completing and archiving the task.

### Original blocked checkpoint (historical, retained verbatim)

PENDING. The GitHub connector provides file edits but no checkout/execution; source checkout failed DNS resolution to github.com (`Could not resolve host: github.com`) and pnpm is unavailable in the container, so the repository-built CLI could not allocate a task ID. `TASK-0097` uses the next unused ID after checked `TASK-0096` as a documented manual fallback. No local validation, Docs7 deploy, claim or badge may be asserted.

### Audit checkpoint 2026-11-17
Expand Down Expand Up @@ -99,3 +106,46 @@ task; historical blocked TASK-0087/0092/0093 remain untouched.
ownership or badge verification. No deployment/account action is authorized
by the corrective patch tasks. The task stays blocked, not completed/archived;
this external documentation work is not a patch-publication prerequisite.

### External evidence reconciliation 2026-11-17

- Public Context7 library `https://context7.com/cynrath/agent-context-kit`
returns 200. Provider metadata reports
`claimedBy=f799b9e6-8500-464e-a177-3bf3216860aa`, `verified=true`,
`verifiedAt=2026-10-15T10:16:21.849Z`, `configSource=context7json`.
This is provider read-back, not an inferred badge or a new account action.
- Docs7 Production check `134103983215` on master
`b7f07d68638a288a0c802f72dedd329014f4679d` concluded success with
"Deployment succeeded". The provider's existing site/deployment records are
`2adaa5e1-d7a5-49d4-9c9d-040f49885e22` /
`3fdd8869-f560-49b1-a866-c03963f2050f`, in the same owner teamspace.
- `https://cynrath-agent-context-kit.docs7.io/`,
`/guides/getting-started`, `/llms.txt`, `/llms-full.txt` and
`/guides/getting-started.md` each returned HTTP 200 with the expected HTML,
plain-text or Markdown content type. Agent content includes current
`canonicalPath`, `exit_code_hint` and feature-index documentation.
- The successful provider production render accepts this actual configuration
and its 32 real documentation routes. The previously recorded generic
upstream-schema regex compilation problem is preserved; no schema pattern
or validation gate was weakened to manufacture a formal-schema pass.
- The claim guide now explicitly requires the exact per-library URL and
public key from the owner panel only if the already-owned library becomes
unclaimed. No key was invented, no ownership/config-source setting changed,
no duplicate library/site created, and no deployment was dispatched.
- Existing GitHub Pages configuration and immutable package identities remain
unchanged by this documentation task. TASK-0103 separately owns the authorized
patch release for verified runtime/CI fixes; docs alone did not trigger it.
- PR #44 head `716dd255a351bbd338980f82c9b6cae24341039f` passed all required
cross-platform checks before merge. Follow-up guide/task changes still await
their own local documentation checks and exact-head PR evidence.
- Follow-up local validation: documentation distribution/canonical docs gates
11/11 PASS; repository text hygiene, task doctor and diff check PASS.
The current goal's explicit Git/PR/master-merge authorization, also recorded
in TASK-0103, covers this scoped evidence follow-up. It does not authorize
a deployment or account/credential change in this task.
- Context7's connected resolve/query tools independently found the exact
`/cynrath/agent-context-kit` library and returned the current master SDK/MCP
pages: SDK root descriptor `canonicalPath`, built-in/extra rules, fixed
MCP startup root, unsupported per-call root/includeGlobs and ci-controlled
`exit_code_hint=0/1`. Retrieval of the corrected documentation is verified,
beyond the public ownership/badge/config-source metadata above.
Original file line number Diff line number Diff line change
@@ -1,11 +1,13 @@
---
id: "TASK-0103"
title: "Authorized patch publication and public-surface verification"
status: active
status: pending
schemaVersion: 2
dependencies:
- "TASK-0102"
- "TASK-0105"
- "TASK-0106"
- "TASK-0107"
createdAt: "2026-11-17"
completedAt: null
---
Expand Down Expand Up @@ -70,9 +72,9 @@ external blocker; do independent authorized work first, never partial-publish np
## Acceptance criteria

- [x] PR merged only after all exact-head CI checks pass; master SHA verified.
- [~] Marketplace target visible before new immutable tag triggers npm publication.
- [ ] npm latest, fresh CLI/SDK/MCP and new-tag external Action consumer pass.
- [ ] GitHub Release tag/VSIX identity and downloaded asset checksum pass.
- [x] Marketplace target visible before new immutable tag triggers npm publication.
- [x] npm latest, fresh CLI/SDK/MCP and new-tag external Action consumer pass.
- [x] GitHub Release tag/VSIX identity and downloaded asset checksum pass.
- [ ] Stable-pointer bookkeeping merged with CI; final master clean/aligned;
task evidence and open blockers match the actual public state.

Expand Down Expand Up @@ -105,6 +107,11 @@ can correct artifacts; never overwrite/repoint/delete the released version.

## Completion notes

All three public channels now serve 0.5.5, independently verified below. The
stable-pointer follow-up still requires exact-head CI and protected merge.

### Original plan checkpoint (historical)

Plan allocated by repository CLI on 2026-11-17. No publication or tag action yet.

### Publication preflight 2026-11-17
Expand Down Expand Up @@ -153,4 +160,93 @@ temporary detached records worktree/PR transport, removed after merge; no direct
master push or persistent development branch is introduced. Publication still
waits for master checks, a fresh audited master VSIX and current target absence.

### Publication checkpoint — registry processing

- Protected records PR #44 head `716dd255a351bbd338980f82c9b6cae24341039f`
passed all 12 required checks plus Docs7 Preview, then merged as
`b7f07d68638a288a0c802f72dedd329014f4679d`. Both commits have identical tree
`0822388ec806d47223eb64eca22168858c48b294`. Primary checkout remains clean
master equal to origin/master; both old PR transport branches were deleted.
- Post-merge CI run `44101924915` had two macOS jobs canceled before acquiring
a hosted runner (empty steps/runner name; capacity annotation), not test
failures. Other executed jobs and Action run `44101925039` passed. The
identical-tree PR platform matrix passed; no workflow was dispatched/rerun.
- Marketplace publication of audited `ackit-vscode-0.5.5.vsix` succeeded;
public latest read-back returned 0.5.5 before tag push. Uploaded VSIX size
415230 bytes, SHA-256
`b0c66db5b6aa4f3b12c58126021cc66d5407c1b99825295060772e277f8e6939`.
- NEW annotated tag `v0.5.5` object
`857d91b4866fd88c691eca2b230457ef9da11310` peels to `b7f07d6`.
The tag has not been moved/deleted. New-tag cold external Action consumer
passed scan/optimize/drift, thresholds, CLI errors and canonical SARIF.
- Release run `44129100682` passed full quality, VSIX preflight, tarball smoke,
Marketplace-first gate and npm OIDC publication. Published tarball SHA-1
`41ff5b1865ef6ede16ac9c4d5743b34519f38537`; signed provenance transparency
log index `3949357822`. npm reported that package processing was pending.
- The 30 x 10s registry-visibility gate expired with exit 20. Subsequent fresh
npm-cache and direct HTTPS probes still returned 404; latest remained 0.5.4.
npm's official 2026-07-28 publish-time scanning announcement allows 15 minutes
or longer processing. This is not a failed upload or proof of public success.
Downstream consumer/GitHub Release steps were skipped. No second publish,
tag change, workflow rerun or stable-pointer update has been attempted.
- Publication read-back continues after the bounded TASK-0097 documentation
reconciliation unit; this scheduling change is not task completion.
- A temporary records worktree nested under ignored temp caused duplicate
skill discovery (8 issues). Moving that clean worktree outside the primary
repository restored 4 skills / 0 issues and doctor PASS; no product policy,
scan suppression or skill validator was changed. Scan CI remained exit 0.

### Public release verified; stable bookkeeping in progress

- npm version and latest both returned 0.5.5 after processing, without another
publish. Downloaded registry tarball SHA-1 equals the original workflow value
`41ff5b1865ef6ede16ac9c4d5743b34519f38537`; SHA-512 integrity also matches
`sha512-sjiGI6x/NP8IyPEoNt/QAB9kJMVdG/L7EiHF1kQyjF8QwT4FRZnGj0YDTwHdwwd9YrOOpJ08XSu7FP5E8r15Xw==`.
- Independent consumers used empty directories outside the checkout and unique
npm caches. Fresh npx and installed CLI returned 0.5.5. Published SDK found the
built-in marker rule. Published MCP handshook version 0.5.5, listed 16 tools
without per-call root/includeGlobs overrides, and produced ci false/true hints
0/1. `npm audit signatures --omit=dev`: 100 signatures / 17 attestations
verified. No global package or authentication state was modified.
- Public Marketplace latest remained 0.5.5 after npm. Its own VsixSha256 and
downloaded package match the exact uploaded VSIX:
`b0c66db5b6aa4f3b12c58126021cc66d5407c1b99825295060772e277f8e6939`.
- Manual downstream GitHub Release creation succeeded at
`https://github.com/Cynrath/agent-context-kit/releases/tag/v0.5.5`
(2026-11-17T17:00:09Z), after all independent npm/Marketplace consumers and
checksums passed. The release is public, stable, latest and uses the existing
immutable tag. Downloaded asset, API digest and release-note checksum agree
with the Marketplace VSIX above; packaged manifest/README/CHANGELOG, 31 ZIP
entries, CRC/bounds and offline/security preflight PASS (415230 bytes).
- The failed workflow's separately rebuilt ZIP had SHA-256 `35ae1f0...` and was
never uploaded as a Release asset. The repair attaches the original audited
Marketplace VSIX, byte-identical across both public extension channels. No
immutable asset was replaced and no workflow rerun/dispatch was performed.
- TASK-0106 owns the observed too-short next-release wait, planned before code
in `1219388` and implemented in `8e7452f`: bounded 30-minute visibility reads,
35-minute step timeout, unchanged fail-closed gates. Behavioral regression
proved the old failure and all 28 workflow contracts now pass. Full root suite
is 126 files / 778 PASS / 3 existing Windows privilege skips (781 total).
- Stable pointer/current install pins now advance to the verified 0.5.5 in the
same follow-up, including the Action demo's stale pin/distribution copy. The
getting-started task example uses the installed `task create` command.
Source/extension versions and all runtime files remain identical to the tag.
- Follow-up stable documentation checks: version/readme/distribution/canonical
docs contracts 48/48 PASS; version parity reports source/stable both 0.5.5.
Text hygiene, task doctor and diff check PASS. Exact-head PR CI and protected
stable-bookkeeping merge remain the final completion gate.
- TASK-0097's live ownership/production evidence is recorded; completion waits
for the guide follow-up's exact-head CI. Historical TASK-0087/0092/0093 remain
blocked and are not casually closed by this release.

Dependencies: TASK-0102

### Follow-up CI held for a shared-build race

PR #45 head `2e8e0ae89dc2164bf90cccaff468e47cf569c6d1` passed the new npm
processing contracts and other executed checks, but Linux/Node 24 job
`134218923233` failed one built-CLI assertion (exit 1 instead of 2): the loader
read an incomplete `dist/core/policy/tiers.js` during a parallel prepack rebuild.
TASK-0107 plans isolation of both source-checkout pack writers; no assertion is
weakened and no failed run is rerun. The protected bookkeeping merge remains
held. Independent public release/install verification is unaffected.
Loading
Loading