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
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
---
id: "TASK-0097"
title: "Context7 ownership-ready configuration and Docs7 documentation distribution"
status: pending
status: completed
schemaVersion: 2
dependencies: []
createdAt: "2026-10-15"
completedAt: null
completedAt: 2026-11-17
---

## Purpose
Expand Down Expand Up @@ -40,8 +40,8 @@ Expose the maintained ACKit documentation to Context7 and prepare Docs7 hosting
- [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.
- [x] Validated by repository checks, PR CI and Docs7 production build; external verification clearly recorded.
- [x] Release decision follows repository release governance and only occurs after complete evidence.

## Test steps

Expand Down Expand Up @@ -70,10 +70,10 @@ 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.
All literal acceptance criteria now have repository, exact-head CI and live
provider evidence. The conditional claim-key guide is deployed and verified.
Original blocked checkpoints and the historical manual ID fallback below are
retained as history, not current completion claims.

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

Expand Down Expand Up @@ -149,3 +149,28 @@ task; historical blocked TASK-0087/0092/0093 remain untouched.
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.

### Final production and governance proof

- PR #45 exact head `7a191414d7ff351acc20b8051914ca0492962ee2` passed 13/13
checks before protected merge `f42937d7ffc97a5d21307935995d1a858c4af847`.
Docs7 Production check `134300433187` on that merged master concluded
success, title "Deployment succeeded". No deployment was dispatched by this
task; the existing integration processed the authorized protected merge.
- All six live routes returned HTTP 200: site root, getting-started HTML,
llms.txt, llms-full.txt, getting-started Markdown and context7-docs7 Markdown.
The deployed guide contains the exact per-library challenge instruction;
getting-started is pinned to 0.5.5, and llms-full contains current canonicalPath
and exit_code_hint contracts plus 0.5.5 content. No static-only hosting claim.
- Official Context7 schema validation and 32 real navigation routes remain
verified; the actual Docs7 production build accepts the project configuration.
The earlier generic upstream PostHog-regex/AJV compilation limitation remains
explicitly recorded, not relabeled as a formal AJV Docs7-schema pass.
- Ownership, badge and repository-file configuration were read back from the
provider, and current SDK/MCP documentation was retrieved through Context7.
Existing hosting configuration/package identities were unchanged by this
documentation task. No account, credential, claim or config-source mutation.
- TASK-0103's separate compatible runtime/CI patch was user-authorized, gated
by exact-head CI and live Marketplace before tag/npm publication. Ownership
and the earlier successful Docs7 production build were verified before tag
push; these docs-only follow-ups created no extra release or changed tag.
Original file line number Diff line number Diff line change
@@ -1,15 +1,15 @@
---
id: "TASK-0103"
title: "Authorized patch publication and public-surface verification"
status: pending
status: completed
schemaVersion: 2
dependencies:
- "TASK-0102"
- "TASK-0105"
- "TASK-0106"
- "TASK-0107"
createdAt: "2026-11-17"
completedAt: null
completedAt: 2026-11-17
---


Expand All @@ -27,9 +27,24 @@ publication; tag-triggered npm OIDC Trusted Publishing; and GitHub Release
creation with audited VSIX assets. This is authorization for these exact actions
in this task, not permission for direct master push or credential disclosure.
Force push/reset/rebase/history rewrite/tag movement/deletion, workflow dispatch
or rerun, deployments, secret/permission changes and legacy .NET releases remain
or Release-workflow rerun, deployments, secret/permission changes and legacy .NET releases remain
prohibited. No release artifact may be overwritten.

On 2026-11-17 the user separately approved the concrete request to retry only
the two runner-capacity-canceled macOS CI jobs in run `44151390824` at head
`7a191414d7ff351acc20b8051914ca0492962ee2`, at most three attempts per job.
TASK-0107 records the exact scope and provider cancellation evidence. Other
workflow reruns remain unauthorized.

The user's follow-up instruction was to finish the current goal. Within this
goal, that direction is applied to the same bounded capacity-only normal CI
retries needed for protected post-merge/evidence integration, with at most three
retry attempts per canceled job. This is not authorization for Release-workflow
reruns, workflow dispatch, publication replacement, settings or permission changes.
The post-merge CI run `44157026151` at `f42937d` has exactly three non-success
jobs: macOS Node 22/24 and macOS package smoke, all canceled with zero steps and
verified hosted-arm64 capacity annotations. Only that non-success set is retried.

## Scope

- Push the fully committed branch, create a reviewable PR and wait for successful
Expand All @@ -47,7 +62,7 @@ prohibited. No release artifact may be overwritten.

## Out of scope

- Direct master push, workflow dispatch/rerun, deployment or site publication;
- Direct master push, workflow dispatch/unapproved rerun, deployment or site publication;
credential creation/storage; tag or immutable version replacement; changes to
unrelated repositories; closing old blocked tasks without literal evidence.

Expand Down Expand Up @@ -75,7 +90,7 @@ external blocker; do independent authorized work first, never partial-publish np
- [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;
- [x] Stable-pointer bookkeeping merged with CI; final master clean/aligned;
task evidence and open blockers match the actual public state.

## Test steps
Expand Down Expand Up @@ -107,8 +122,10 @@ 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.
All acceptance criteria and required release/post-merge validation are verified.
All three public channels serve 0.5.5, stable bookkeeping is merged after
exact-head CI, and its post-merge CI succeeded. This completion/archive record
uses the normal protected integration procedure; it changes no runtime artifact.

### Original plan checkpoint (historical)

Expand Down Expand Up @@ -250,3 +267,72 @@ 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.

### Protected stable-bookkeeping merge and task closure

- PR #45 exact head `7a191414d7ff351acc20b8051914ca0492962ee2` passed all 13
checks, including 12 required. The two capacity-canceled macOS jobs were
retried only after separate user authorization. CI run `44151390824`,
attempt 2, concluded success; macOS/Node 24 and Linux/Node 24 each report
126 files / 781 tests PASS, including real tarball/CLI and workflow contracts.
- Protected merge `f42937d7ffc97a5d21307935995d1a858c4af847` at
2026-11-17T19:17:40Z has the exact verified source tree
`d4ed9f68296312691879ccd5ec65a8d79ef6c01e`. Its temporary branch was deleted.
Primary checkout is clean master equal to origin/master. Source/stable parity
now both report 0.5.5. Production code, manifests, lock, schemas, templates,
extension and Action inputs are identical to immutable v0.5.5.
- Docs7 Production check `134300433187` on merged master concluded success.
All six current site/agent/guide routes returned HTTP 200; getting-started
serves 0.5.5 and the claim-key guide contains the exact per-library instruction.
Context7 independently returned the corrected SDK/MCP documentation.
- TASK-0107, TASK-0106 and TASK-0097 passed their literal acceptance gates and
were completed/archived with the repository CLI, without force. Their old
failure/manual-ID/provider-schema limitation evidence remains preserved.
Historical TASK-0087/0092/0093 remain blocked, unchanged.
- Post-merge CI run `44157026151` is being observed; Action run `44157026472`
already concluded success. This task's final completion remains gated on
truthful post-merge evidence and final clean master/archive integration.

The first post-merge CI attempt finished with eight successful jobs and the
three capacity-only macOS cancellations described in the authorization above.
No test step failed. A bounded failed-jobs-only retry follows the user's current
finish instruction; the original cancellation evidence is retained.

### Objective audit evidence map

| Required area | Verified evidence |
| --- | --- |
| Executable environment and Git preflight | Windows PowerShell/Git/Node and repository-built CLI exercised before edits; broken global pnpm launcher isolated from repository defects; pinned pnpm 11.22.0 used for validation (TASK-0098/0102). |
| Action threshold, CLI errors, cold distribution and SARIF | TASK-0098/0104/0105 tests and the v0.5.5 cold external Git consumer; scan/optimize/drift output/threshold contracts and real SARIF 2.1.0 schema/URI checks. |
| CI and VS Code/SDK parity | TASK-0099/0105/0107; real extension lint/unit/Electron gates, SDK built-ins, packaged resources/path bounds, snapshot cancellation and isolated prepack. PR #45 required matrix is successful. |
| MCP contract and startup boundary | TASK-0100/0101; all 16 input schemas match docs, ci hints and explicit CLI-root precedence exercised; fresh published SDK/MCP consumer passed. |
| Documentation, tasks and portability | TASK-0101/0097; repaired README links, 32 real Docs7 routes, live production/agent pages and Context7 retrieval; CLI task doctor validates live/archive IDs, while historical namespace/blocked evidence is preserved. |
| Security and offline behavior | Static offline/path/secret gates and production dependency audit passed. Full development-tool audit retains 19 triaged pre-existing advisories (6 high/11 moderate/2 low), documented in TASK-0101; it is not claimed clean. |
| Version, packaging and release order | TASK-0102/0103; source/extension/stable 0.5.5 parity, schema no-drift, real tarball/VSIX audits, Marketplace visibility before new immutable tag and npm OIDC/provenance. |
| Public consumers and artifact integrity | Fresh outside-checkout npx/CLI/SDK/MCP, tag Action consumer, registry SHA-1/SHA-512, 100 signatures/17 attestations, and equal public Marketplace/GitHub VSIX SHA-256. Rechecked all three public versions/latest on 2026-11-17T19:26:47Z. |
| Git and immutable history | PR #43/#44/#45 protected merges, deleted temporary branches, clean canonical master and unchanged v0.5.5 tag/released artifacts. Post-bookkeeping master CI succeeded; this final archive record follows the same protected integration procedure. |

No production data, migration, public API break, secret/permission mutation or
legacy .NET release change is part of this patch. Product runtime inputs on
master match the immutable release tag; post-publication differences are CI/
test tooling, current documentation, task evidence and the stable pointer.

### Final acceptance and post-merge proof

- Post-bookkeeping master CI `44157026151`, attempt 2, concluded SUCCESS on
exact master `f42937d7ffc97a5d21307935995d1a858c4af847`; all 11 CI jobs
succeeded. Separate Action run `44157026472` and Docs7 Production check
`134300433187` also succeeded. The capacity-only first-attempt cancellations
and the bounded retry are preserved above; no failed test was silenced.
- Required exact-head PR CI, post-merge CI, fresh published consumers, tag
Action consumer, Marketplace-first order, OIDC/provenance, registry/latest,
downloaded asset checksums, stable parity and clean canonical master all have
successful direct evidence. Every TASK-0103 acceptance item is satisfied.
- TASK-0098/0099/0100/0101/0102/0104/0105/0106/0107 and TASK-0097 are verified
and archived. This task is completed/archived through the normal CLI gate.
Historical TASK-0087/0092/0093 retain their unperformed/superseded criteria;
they are outside this patch and were not falsely closed.
- Public versions remain 0.5.5, tag object `857d91b...` still peels to `b7f07d6`,
and both public VSIX channels match SHA-256 `b0c66db5...e6939`. No legacy
release, tag, published package or asset was overwritten. No data migration,
deployment, secret or permission change occurred.
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
---
id: "TASK-0106"
title: "Tolerate npm publish-time processing without weakening release verification"
status: pending
status: completed
schemaVersion: 2
dependencies:
- "TASK-0105"
createdAt: "2026-11-17"
completedAt: null
completedAt: 2026-11-17
---


Expand Down Expand Up @@ -57,7 +57,7 @@ manual downstream repair authority; this task performs no publication action.
- [x] Delayed visibility beyond the old budget succeeds within a bounded wait.
- [x] Permanent absence, wrong shasum and wrong latest retain failure exits.
- [x] Marketplace-first, OIDC, immutable tag and all downstream gates remain.
- [ ] Local checks and required exact-head PR CI pass; evidence matches results.
- [x] Local checks and required exact-head PR CI pass; evidence matches results.

## Test steps

Expand Down Expand Up @@ -89,9 +89,8 @@ the released tag or overwrite an existing package/asset. No destructive Git.

## Completion notes

Local implementation and verification passed; required new-head PR CI remains
to be observed before completion. TASK-0103 resumes stable-pointer bookkeeping
while this task awaits the same protected-PR evidence.
All literal criteria passed locally and in exact-head hosted CI. The correction
is merged on protected master; TASK-0103 owns final stable release bookkeeping.

- Plan commit `1219388` preceded the workflow/test changes. The installed CLI
allocated this task with `task create`; the old title-only alias failed
Expand All @@ -113,3 +112,13 @@ while this task awaits the same protected-PR evidence.
- **Not run:** a new live publish/workflow dispatch or rerun; those actions
are outside this task. The existing 0.5.5 run remains failed at its original
visibility timeout, with downstream verification/release repair in TASK-0103.

### Exact-head completion evidence

PR #45 head `7a191414d7ff351acc20b8051914ca0492962ee2` passed all 13 checks
(12 required) and merged as `f42937d7ffc97a5d21307935995d1a858c4af847`.
Actual YAML-shell delayed-success and failure cases are among the 28 workflow
contracts passing on the default full OS/Node matrix. macOS/Node 24 and Linux/
Node 24 each report 126 files / 781 tests PASS. The later user-authorized CI
capacity retry belongs to TASK-0107; the original Release run remains unchanged.
The next-release change introduces no version, publication or permission change.
Loading
Loading