[hidb4ai]

Which issue or RFC does this PR close?

Release preparation; no dedicated tracking issue. Follows the release process.

Rationale for this change

Prepare PowerContext v1.4.0 so installation instructions, API metadata, generated integration contracts, and the website changelog agree before tagging and publication.

What changes are included in this PR?

• Synchronize current release references to 1.4.0 across OpenAPI, English/Chinese/Japanese READMEs, installation guides, and the DSH README; regenerate Python, Desktop, and Dify contracts.
• Lead bilingual website release notes with four themes: Dream-driven knowledge revision, Working Notes for current progress, traceable knowledge changes, and project memory for Kimi Code. Retain the other release details and compatibility limits.
• Include the new bilingual manual-start guides in automated version synchronization and regression coverage, document Desktop/Dify regeneration, and update current API-version assertions.

Are there any user-facing changes?

Installation examples select package version 1.4.0 and the matching powercontext-v1.4.0 integration tag. Existing release history and independently versioned components retain their own versions.

The four release highlights are:

1. Dream: evolve knowledge (feat(dream): expand reviewed artifact and tag revisions #1716, merged) — explicitly review task outcomes, corrections, and usage feedback against selected knowledge and evidence before approving a revision.
2. Notes: retain current progress (feat(work): add source-backed working notes #1949, merged) — capture short-lived findings, progress, and next steps, and cite still-valid evidence in a Handoff.
3. Traceable knowledge changes (feat(dashboard): browse, compare, and roll back artifact revisions #1813, merged) — browse and compare historical versions, and restore supported content as a new revision with the source and reason recorded.
4. Project memory for Kimi Code (feat: add minimal Kimi Code integration #1964, merged) — experimental saving, search, exact reads, and relevant context injection in new sessions.

The release notes and installation guides explicitly document the implementation's Memory/Candidate contract changes and coordinated upgrade requirements. The unified migration bundle still reports server_ready=false; it is not a complete production upgrade path for existing Dream databases. This PR does not resolve that readiness limit or publish a release.

How was this change tested?

Local validation used Python 3.14.6, Node 24.14.1, and pnpm 11.13.1.

• make version-bump VERSION=1.4.0
• make release-check VERSION=1.4.0
• make contract-test — 56 passed.
• uv run python -m pytest tests/test_release_version.py tests/test_server.py -q — 70 passed.
• pnpm --dir desktop generate and pnpm --dir desktop generate:check.
• uv run python -X utf8 integrations/dify/generate_contract.py --check.
• make docs-test — lint, website tests, source link validation, production build, and static export passed; verified 946 exported public pages and their internal links.
• Website lint (oxlint) and tests (node --import tsx --test tests/*.test.ts) from the website directory — passed.
• SKIP=ty-check uv run prek run on staged changes — all remaining applicable hooks passed.
• uv run ty check scripts/release_version.py tests/test_release_version.py tests/test_api_contract.py tests/test_server.py — passed.
• git diff --check.

Full ty check currently reports unresolved-import for from task import increment in the unchanged tests/e2e/cross_host_work_continuity/fixtures/verify.py:23; the file matches the base commit exactly. The all-files hook command also could not process the workspace-protected .agents/plugins/marketplace.json, so other hooks were scoped to the staged release changes. No native Windows Desktop or external-model acceptance was rerun for this metadata/documentation change.

AI usage statement

Prepared with OpenAI Codex for release-reference updates, generated contracts, bilingual release notes, and local validation.