Skip to content

fix: verify Nightly sources, deployment upgrades and npm services - #539

Merged
harryisfish merged 22 commits into
mainfrom
fix/gh-issues-triage
Nov 10, 2026
Merged

harryisfish merged 22 commits into
mainfrom
fix/gh-issues-triage

Conversation

@harryisfish

@harryisfish harryisfish commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

Deployment archives must match the requested image ID before activation. Core rehearsal starts the previous complete release and verifies the candidate replacement, identity and persisted fixture data before host activation.

Nightly uses the verified scheduled main source to create a version-only commit and tag without a PAT or version PR. Release, npm, CI and deployment planning share complete-tree source validation. Recovery preserves the original tags, artifacts and build numbers. The four-hour GitHub schedule remains best effort.

Native npm acceptance replaces an immutable public baseline with the exact different-source CI candidate on disposable macOS ARM64 and Linux x64/ARM64 runners. The candidate passes the full service lifecycle, PID replacement, concurrency guards, data preservation and no-replay checks. macOS restart waits for confirmed launchd removal before loading the service again.

Shared Rust and client rules cover bounded redaction, business IDs, scheduler decisions, response parsing and JSON storage while preserving their distinct validation and failure contracts. Related authentication, SDK, npm recovery, Nightly and image-pin documentation follows the implemented behavior. Current-base acceptance also rebuilt Core/Web/WWW with the latest bootstrap defaults and verified a fresh default configuration plus a newly built offline container. CI pins an available Go toolchain for actionlint, and the existing service unit test acquires its deliberate held lock before any released lock can be inherited by a concurrent child.

Validation:

  • Final source checks and fixed-base integration checks passed. Independent source and surface reviews found no blocking defects. One unchanged proof-sandbox execution and the container rehearsal retain their original tested source identities with dependency validation.
  • Exact-source expanded CI passed, including all three POSIX native service targets and Windows npm startup.
  • The public baseline and candidate both declare 0.0.1-nightly.20261110.3; their source commits differ. This validates package replacement, without claiming a version-number upgrade or historical-format migration.
  • Previous-release container rehearsal passed with host activation disabled.

Closes #33
Closes #41
Closes #43
Closes #44
Closes #45
Closes #46
Closes #533
Closes #536
Closes #537

Owner: @harryisfish. Status: verified and ready for merge.

The initial npm publication (#32), retired Cursor SDK Bridge (#439) and accepted scheduling limitation (#534) are closed. The iOS locator failure #535 was fixed separately in #538 and passed its exact-source Mobile run. Its runtime-build and latest-compatible-version coverage limits remain explicit. This PR does not publish a release, deploy production services or invoke real AI Providers.

Reject mismatching imported images before activation and cover the CLI
boundary in the existing self-test.

Refs #537
Start the previous published Core before staging the candidate config and
activating its image. Verify preserved fixture data and repeat activation,
and fail closed when prior-release verification or the upgrade fails.

Refs #536
Validate rehearsal settings with the real activation config parser in the
existing self-test so its boundary constraints cannot drift.
Reuse bridge redaction for manager progress and errors while preserving streamed secret prefixes and masking overlapping credentials.
Reuse the same bounded ASCII predicate for runtime fields, bot definitions and client requests while keeping their existing error messages.
Keep reply completion distinct from steered input settlement and share the
known scheduler states used to rank observations and identify terminal jobs.
Share object, text and safe integer checks with workspace and progress
parsers while preserving field constraints and domain error messages.
Use the shared storage entry for device records while retaining optional
read fallbacks and blocking writes with the platform-specific error.
Carry the masked prefix length beside the raw secret suffix so overlapping matches stay redacted without growing the pending buffer.

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这次不合并。描述写明部署锁定核对、上一版重演、无 PAT 的 Nightly 和最终集成验收都还没有做完,状态仍是处理中。没有当前 head 的通过记录,不标成可审核,也不接走这个草稿。

View PR

Open in Web View Automation 

Sent by Cursor Automation: Vibeface 清理

@harryisfish harryisfish changed the title fix: resolve confirmed issue backlog and retire obsolete reports fix: resolve deployment, Nightly and shared validation issues Nov 10, 2026
@harryisfish
harryisfish deployed to vibeface-validation November 10, 2026 13:48 — with GitHub Actions Active
@harryisfish harryisfish changed the title fix: resolve deployment, Nightly and shared validation issues fix: verify Nightly sources, deployment upgrades and npm services Nov 10, 2026
Keep centralized scheduler decisions and deployment regression coverage
while adopting the current main parsers, fixtures and removed legacy paths.
@harryisfish
harryisfish deployed to vibeface-validation November 10, 2026 16:52 — with GitHub Actions Active
@harryisfish
harryisfish marked this pull request as ready for review November 10, 2026 18:07
@harryisfish
harryisfish merged commit 65fd43c into main Nov 10, 2026
42 checks passed
@harryisfish
harryisfish deleted the fix/gh-issues-triage branch November 10, 2026 18:08
cunoe added a commit that referenced this pull request Nov 13, 2026
…ontainerd hosts (#569)

* fix(deploy): activate pinned archives on containerd image store hosts

Every real activation since #539 failed with "imported image differs from
the pinned image ID": the pin is the build runner's classic-store
configuration digest, while the host's containerd image store reports
the manifest digest from `docker load`. The host now proves from the
archive's manifest.json, index.json and blobs that it holds exactly the
pinned image, accepts only the pinned ID or that proven manifest digest
after loading, and activates under the ID its store reports. The build
step runs the same archive proof right after `docker save`.

* ci: keep only core CI, release and deploy workflows

Remove CI / Desktop, CI / Windows native, CI / Mobile builds, CI / Mobile
device builds, CI / Native diagnostics with the Windows installer
diagnostic, and the Delivery small and live proofs, plus the two scripts
only they ran. Self-tests drop the assertions about the deleted files
and keep every Core, reusable and release contract; the CI guide, iOS and
e2e docs, the proof README and AGENTS.md stop pointing to them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment