[pranems]

Summary

Publish explanatory, user-facing 0.55.67 release notes for users upgrading
from customer0.55.20, grounded in exact published source6785200f and deployed
sourceb87412b0, and reconcile the documentation landing page with actual
cutover759f243a.

The existing canonical release-notes page gains a before/after matrix, four
rendered diagrams, PATCH/settings/lifetime worked examples, all eleven added
migrations (19 -> 30 SQL files), deprecations, upgrade/recovery steps and
explicit evidence boundaries. Historical preparation receipts remain clearly
labeled rather than being presented as current pending deployments.

Documentation only. No product, dependency, schema, version, deployed image or
cloud state change. Customer production remains on0.55.20; the migration-only
performance exception does not qualify performance or authorize promotion.

Linked Defect / Plan Reference

• DELIVERY_PLAN.md defect ID: N/A; operator-requested cumulative user release publication.
• Audit doc reference: docs/RELEASE_NOTES.md#05567, exact source comparison, docs/CUSTOMER_UPGRADE_05520_TO_05556_REPORT.md and docs/TENANT_10_MIGRATION_EXECUTION_2026_10_30.md.
• ADR (if applicable): N/A; reuse the existing canonical release entry point and freshness gate.

TDD Process

• RED test written first; observed it fail for the expected reason. N/A: prose-only change; no runtime behavior or new test logic.
• GREEN: minimal implementation that turns the test green. N/A; existing documentation checks validate this publication.
• Refactor (if any) keeps the test green. N/A; no code refactor.
• Permanent regression guard added (where applicable - see existing patterns in api/src/security/). Existing freshness/source-claim/link and real-browser diagram gates apply to the existing release document.

Feature / Bug-Fix Commit Checklist (standing rule)

Every behavioral change must include all that apply. Tick or strike through with N/A + reason.

• Unit Tests - service-level and controller-level coverage of the new behavior. N/A; no runtime behavior changed. Do not invent fresh release-suite counts.
• E2E Tests - end-to-end spec under api/test/e2e/ exercising the feature through HTTP. N/A; documentation only, retained release receipts explicitly identified.
• Live Integration Tests - new section in scripts/live-test.ps1 runnable against local + Docker + Azure. N/A; no cloud writes or live rerun for prose.
• Feature Documentation - dedicated doc in docs/ with architecture, RFC references, Mermaid diagrams, test coverage. Expanded canonical release notes with four diagrams and outcome/compatibility evidence.
• INDEX.md Update - add the new doc reference to docs/INDEX.md. Current release anchor and actual included/remediated scope updated.
• CHANGELOG.md Update - [Unreleased] entry with full test counts and feature summary. Documentation-only entry explicitly records no changed product/test counts.
• Session & Context Updates - Session_starter.md and docs/CONTEXT_INSTRUCTIONS.md.
• Version Management - bump api/package.json (and any other version refs) when behavior changed. N/A; retain the deployed0.55.67 identity.
• Response Contract Tests - API responses contain ONLY documented fields (key allowlist assertion at unit + E2E + live). N/A; no response contract changes.

Validation Output

Documentation freshness/link audit: PASS, all27 manifest documents.
Source-claim content audit: PASS, all27 user-facing documents.
Mermaid: PASS, four diagrams rendered in real Chromium,
  both light/dark themes and strict security mode.
Literal examples: PASS, two JSON blocks and one HTTP JSON body parse.
Migration inventory: PASS, all11 added migration SQL paths enumerated.
Representative dependency claim: PASS, locked Vite8.1.6.
Patch whitespace: PASS.
Known renderer warning: competing marketplace extension already installed;
  no shared VS Code extension changes, no claim of editor-side verification.
Normal protected push: PASS, all26 Fast gates, 626.4 seconds.
Hook-owned API unit and in-memory HTTP suites PASS.
Known Jest force-exit/open-handle warning retained, not hidden.
HTML export: PASS, one document with four pre-rendered SVG diagrams.
Exact-tip hosted checks: all five SUCCESS.
Review5780996738: approval recommended, no open issues;
  formal state COMMENTED, not APPROVED, zero review threads.
Normally merged as3bee7a3c22992af9a08fde8e36fc398fc37b2b48.
Published master release-note blob matches the exact merged source.

Commands and results:

• pwsh -NoProfile -File scripts\audit-doc-freshness.ps1: PASS,27 documents.
• node scripts\audit-doc-content.mjs: PASS.
• npm run docs:mermaid:render -- docs\RELEASE_NOTES.md: PASS,4 diagrams x2 themes under strict mode.
• git diff --check: PASS.
• npm run docs:html -- docs\RELEASE_NOTES.md: PASS, one standalone HTML
  document with all four diagrams pre-rendered.
• git push --set-upstream origin docs/release-05567-cumulative-20261105:
  PASS, all26 mandatory Fast hook gates in626.4 seconds, no bypass.
• Inline Node source/evidence checks: PASS; JSON/HTTP parse, all11 migrations
  from git diff --name-only 6785200f b87412b0 -- api/prisma/migrations,
  source counts19/30, exact baseline/target package identities and locked
  Vite selection. No dependencies installed or regenerated.
• No manual API/Web/full browser/live reruns for a documentation-only change.
  The normal protected push still owns its applicable gates; no bypass.
• Final gh api repos/pranems/SCIMServer/contents/docs/RELEASE_NOTES.md?ref=master
  and Git blob comparison: PASS. Canonical runtime/package/Prisma/registry
  trees remain byte-identical to prior master759f243a.

Standing Rules Acknowledgment

• No em-dash (Unicode U+2014) anywhere in the diff. Verified via Select-String -Pattern ([char]0x2014).
• No git commit --amend on history that has been pushed.
• No new credentials, tokens, or secrets committed to source. Forbidden patterns regression spec at api/src/security/forbidden-source-patterns.spec.ts will catch known anti-patterns.
• Migrations are additive-only (expand-contract for column changes). Migration linter at api/src/scripts/lint-migrations.ts enforces this. N/A; no migration edited. Existing configuration rewrite and index-drop recovery implications are documented honestly.

Destructive Migration Override (skip if not applicable)

• This PR contains a NEW destructive Prisma migration (DROP TABLE/COLUMN, ALTER COLUMN ... TYPE, RENAME, INSERT ... SELECT FROM)
• I have set ALLOW_DESTRUCTIVE_MIGRATION=1 in the CI environment for this PR
• Justification (required if box above is ticked):

  <!-- Why this destructive change is necessary, what the rollback path is, and which release window it ships in -->
  

N/A: no migration or runtime change.

Reviewer Hint

Diff areas worth special attention from the reviewer:

• Baseline capabilities must not be mislabeled as new features.
• All11 migrations must be explained, including legacy-setting conversion,
  case-only name collision preflight, member-reference rollback and snapshot trigger.
• Synthetic worked examples are not claimed as live measurements.
• Retained validation lanes,42 in-memory skips, four live placeholders,
  unqualified performance and unchanged customer production must stay explicit.
• No external-client repointing, off-device recovery proof or blanket security
  certification is implied by deployment or documentation.
• Self-improvement: applied by reconciling source/artifact identities and current
  versus historical status in the canonical entry point.
• Design/architecture disposition: accepted; reuse existing documentation and
  gates, no extra version ledger or speculative test framework.

[Copilot]

🟢 Approval recommended

No active review issues are reported for the documentation-only release-guidance update.

No open issues 🎉

What changed in this PR

Publishes cumulative 0.55.67 release guidance for users upgrading from 0.55.20, using the existing canonical release-notes page. This is documentation-only; customer production remains unchanged and performance remains unqualified.

Changes:

• Adds capability comparisons, worked examples, four diagrams, eleven migration descriptions, and upgrade/recovery guidance.
• Separates current dev/canary deployment status from historical preparation receipts and documents validation limits.
• Updates the documentation index, project context, and changelog to reference the cumulative release notes.

File	Description
Session_starter.md	Records the release-documentation checkpoint and scope.
docs/​RELEASE_NOTES.md	Adds cumulative release details, migration guidance, and evidence boundaries.
docs/​INDEX.md	Links the current release and replaces obsolete pending-status descriptions.
docs/​CONTEXT_INSTRUCTIONS.md	Aligns assistant context with the published release guidance.
CHANGELOG.md	Records the documentation-only publication and unchanged runtime scope.

_{Review effort: Balanced}

[pranems]

Final publication evidence: normal protected push passed26/26 gates in626.4s; exact tip677bbcdd has five SUCCESS hosted checks (validate, build-and-push, CodeQL analysis/policy and freshness). Independent review5780996738 recommends approval with no open issues; formal state COMMENTED, not APPROVED, and zero review threads. Four diagrams render under strict Chromium light/dark themes; literal JSON/HTTP examples parse; all11 source-delta migrations are enumerated. Existing canonical freshness/source-claim/link gates pass27 docs. Standalone HTML export includes all4 SVG diagrams. No runtime, schema, version, dependency or cloud changes. Proceeding with normal exact-head merge; customer production remains unchanged and performance unqualified.

[pranems]

Publication verified on master at3bee7a3c: GitHub contents API returns release-note blob3c2fe368df9ce988b294cc5fbded7d3ae94de739, identical to the merged Git object. Merged-master CodeQL41984664562 also passes. Share current notes: https://github.com/pranems/SCIMServer/blob/master/docs/RELEASE_NOTES.md#05567 . Permanent reviewed snapshot: https://github.com/pranems/SCIMServer/blob/3bee7a3c22992af9a08fde8e36fc398fc37b2b48/docs/RELEASE_NOTES.md#05567 . API/web runtime, package versions, Prisma source and estate registry are unchanged from prior master759f243a. No cloud deployment or customer-production change.