align stable release docs with 1.2.2 - #341

Summary

• add the missing v1.2.2 stable release note and keep the docs portal tied to the package version that is actually being published

What Changed

• added docs/releases/v1.2.2.md
• updated the root README and docs portal release links to point at v1.2.2, v1.2.1, and v1.2.0
• changed the documentation integrity test to derive the current stable release note from package.json instead of a stale hardcoded file name

Validation

• npm run lint
• npm run typecheck
• npm test
• npm test -- test/documentation.test.ts
• npm run build
• Focused tests: npx vitest run test/documentation.test.ts

Docs and Governance Checklist

• README updated (if user-visible behavior changed)
• docs/getting-started.md updated (if onboarding flow changed)
• docs/features.md updated (if capability surface changed)
• relevant docs/reference/* pages updated (if commands/settings/paths changed)
• docs/upgrade.md updated (if migration behavior changed)
• SECURITY.md and CONTRIBUTING.md reviewed for alignment

Risk and Rollback

• Risk level: Low
• Rollback plan: Revert acb932b

Additional Notes

• This keeps future release-doc drift from recurring when package.json is bumped again.

note: greptile review for oc-chatgpt-multi-auth. cite files like lib/foo.ts:123. confirm regression tests + windows concurrency/token redaction coverage.

Greptile Summary

docs-only pr that adds the missing v1.2.2 release note and re-targets all stable release links in README.md and docs/README.md. the most meaningful change is in test/documentation.test.ts, which now derives currentStableReleaseDoc from package.json at test runtime via a beforeAll hook, eliminating the drift risk when the package version is bumped again.

key changes:

• docs/releases/v1.2.2.md — new stable release note; all internal links resolve correctly
• README.md / docs/README.md — three release link rows updated to v1.2.2 / v1.2.1 / v1.2.0
• test/documentation.test.ts — readPackageVersion() + beforeAll replaces the hardcoded "docs/releases/v1.1.10.md" entry; previousStableReleaseDoc and earlierStableReleaseDoc remain intentionally hardcoded per the inline comment

minor issues found:

• a spurious leading tab was added to the describe("Documentation Integrity", ...) call — cosmetic, won't break vitest, but inconsistent with the rest of the file
• currentStableReleaseDoc starts as "" with no guard in getUserDocs(); safe today but fragile if the helper is reused outside it() bodies

no vitest coverage gaps introduced by this pr (docs/test changes only). no windows filesystem or token safety concerns in the changed code. full npm test checkbox is unchecked in the pr description — worth running the complete suite before merging to confirm no regressions across the 87-file suite.

Confidence Score: 5/5

• safe to merge — all findings are p2 style nits, no logic bugs or runtime errors introduced
• only two findings, both p2: a cosmetic indentation regression and a defensive-coding suggestion. the functional changes (doc links and test logic) are correct. v1.2.1 and v1.2.0 release docs exist on disk. the beforeAll / getUserDocs() wiring is safe for all current call sites. p2 findings do not reduce the score below 5 per scoring policy.
• test/documentation.test.ts — leading-tab regression on the describe block and missing guard on currentStableReleaseDoc

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant V as Vitest runtime
    participant B as beforeAll()
    participant PJ as package.json
    participant GD as getUserDocs()
    participant FS as Node FS

    V->>B: execute before any it()
    B->>PJ: readFileSync("package.json")
    PJ-->>B: { version: "1.2.2" }
    B->>B: set packageVersion = "1.2.2"
    B->>B: set currentStableReleaseDoc = "docs/releases/v1.2.2.md"

    V->>GD: called inside it() body
    GD-->>V: [..., "docs/releases/v1.2.2.md", "docs/releases/v1.2.1.md", "docs/releases/v1.2.0.md", ...]

    V->>FS: existsSync + readFileSync for each doc
    FS-->>V: all present and non-empty ✓

This is a comment left during a code review.
Path: test/documentation.test.ts
Line: 143

Comment:
**Spurious leading tab on `describe` block**

the `describe` line got an extra leading tab while its body (`it(...)` blocks) did not. all other top-level statements in this file sit at column 0. this looks like an accidental whitespace edit.

```suggestion
describe("Documentation Integrity", () => {
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: test/documentation.test.ts
Line: 34-38

Comment:
**`currentStableReleaseDoc` starts as empty string with no guard**

`currentStableReleaseDoc` is `""` at module-init time and only set inside `beforeAll`. `getUserDocs()` silently includes `""` in the array if it were ever called before `beforeAll` completes (e.g. during test collection in a future refactor, or if this helper is imported by another test file). `join(projectRoot, "")` resolves to the project root directory, so `read("")` would throw an `EISDIR` error instead of a meaningful assertion failure.

current call-sites are all inside `it()` bodies so it's safe today, but a defensive early throw would lock in that contract:

```typescript
function getUserDocs(): string[] {
	if (!currentStableReleaseDoc) {
		throw new Error("getUserDocs() called before beforeAll — currentStableReleaseDoc not set");
	}
	return [
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (6): Last reviewed commit: "chore: final CodeRabbit retrigger" | Re-trigger Greptile}