Skip to content

graft: recover orphan branch rescue/orphan-762071627a6a-feat-publish-isolated-rust-dart-and-type onto main - #5

Merged
ORESoftware merged 219 commits into
mainfrom
graft/rescue-orphan-762071627a6a-feat-publish-isolated-rust-dart-and-type-20260905
Sep 12, 2026
Merged

ORESoftware merged 219 commits into
mainfrom
graft/rescue-orphan-762071627a6a-feat-publish-isolated-rust-dart-and-type-20260905

Conversation

@ORESoftware

Copy link
Copy Markdown
Contributor

Draft. rescue/orphan-762071627a6a-feat-publish-isolated-rust-dart-and-type was rescued from a dangling commit, so it has no common history with main and GitHub would not open a pull request for it.

This branch is a genuine two-parent merge of origin/main and 762071627a6a8ddfc3391cb7ca8ecf7277f21faa, built with git merge-tree/commit-tree plumbing — no checkout, no working-tree change anywhere.

How the overlap was resolved (both sides carried these files; there is no common ancestor to diff against):

  • .gitignore — union (8 extra rule(s) carried over)
  • kept main's current version: .zpkg.toml README.md

Those are scaffolding files that main has regenerated since the orphan was written; the orphan's own copies are not lost — read them with git show 762071627a6a8ddfc3391cb7ca8ecf7277f21faa:<path>. Everything else the orphan adds (138 file(s)) is here verbatim.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KAAGBnXTSw7zE5xnY4tiBY

ORESoftware and others added 30 commits July 23, 2026 14:22
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- zed-interfaces: VersionScheme (semver/calver/opaque), tolerant version parsing
  (v-prefix, Go +incompatible, PEP 440), npm-style range parsing, shared sync
  contract types (SyncWriteMode/ErrorPolicy/ChangeEvent), regenerated schemas.
- zed-cli: resolve via the shared calver-aware resolver; deterministic zip
  artifacts alongside tar.gz with magic-byte extraction.
- zed-api-server: persist and serve version_scheme (entity + migration + handlers).
- zed-clients: dependency-free sync wire types bridge.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…rl validation

- PackageSection gains bin, build ([build] command+outputs), build_dependencies,
  workspace ([workspace] members), and overrides.build sections for the polyglot
  build-cache, binary-hoisting, monorepo, and consumer-patch features.
- Validate repository URL scheme, bin names/targets, and build outputs; reject
  range-shaped requirements that don't parse (no silent degrade to opaque tag).
- Add is_sha256_hex + is_safe_relative_path guards for the CLI trust boundary.
- Add build_entry_rel/current_platform (per-platform build cache) and BIN_DIR.
- Yank REST DTOs (YankRequest/YankResponse) + yank_path helper.
- Regenerate JSON schemas; fix stale zed.toml/zed.lock doc references.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The generated schemas/ are the contract the non-Rust SDKs mirror; verify they
stay in sync with the source types on every push.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Adds an [install] section with a `dir` (default `zed_modules`; e.g. `.vendor/.zed`
or `.deps/.zed`) plus an optional `adapter`, and a Manifest::modules_dir() helper.
The dir must be a safe relative path (InvalidInstallDir otherwise). This lets zed
COMPLEMENT npm/maven rather than replace them: the few zed-sourced deps land in a
project-relative tree the ecosystem adapter then wires into the toolchain.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The InstallSection addition (install.dir / install.adapter) landed in the
Rust types but the committed JSON schemas were never regenerated, so the
"Schemas are up to date" CI gate failed. Regenerated via
`cargo run --example generate_schemas`.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The shared contract for the org audit trail (zed-docs issue #7), so the
server, CLI, and generated client schemas cannot disagree on it.

`AuditEntry` carries the raw `action` string alongside a parsed
`action_kind`, and `AuditAction::parse` returns Option: an unrecognized
action from a newer server deserializes cleanly on an older client
instead of failing the whole response.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ORESoftware and others added 28 commits August 4, 2026 07:53
Add the canonical Zed manifest and lockfile, ignore local package state, and provide a reusable parser-backed validation workflow for interface repositories.
Require exactly one `[targets.repository]` rooted at `.` whenever a manifest declares targets, while preserving the latest parser pin and all existing package-contract checks.
Extend the reusable validator to build real canonical and target archives with the pinned Zed packer, inspect their identities and contents, and preserve all existing manifest, lockfile, workflow, and permission checks.

Validated by successful Akrion multi-target and ACT single-target canaries.
Add canonical package- and target-level native dependency and lifecycle-hook declarations, strict validation, deterministic merge/projection behavior, generated schemas, and edge-case coverage.
Define strict npm/Cargo publication identities, portable/meta/platform roles, canonical deterministic JSON, immutable artifact evidence, complete topology validation, generated schema, cross-platform certification, and an external offline consumer canary.
Preserve the merged native-registry publication contract and current manifest/install-hook exports, while replaying only the reviewed six-file npm/Cargo requirement and exact-resolution contract.
Add source-aware npm/Cargo range canonicalization and exact immutable native dependency locks on the merged native-registry foundation. Preserve current manifest/install-hook and registry exports, reject unsupported or ambiguous native syntax, and bind exact resolved versions to immutable artifacts. Exact product workflows and independent current-main E2E canary #53 passed. Refs DEN-1507 and DEN-1420.
Leave only the six certified product and compatibility files for ordinary exact-head review.
Add source-aware exact npm/Cargo dependency provenance to .zpkg.lock v1 while preserving legacy package and Nix records. Validate native entries during parse, write, and upsert; enforce deterministic ordering and source-specific uniqueness; and retain immutable version and artifact identity. Exact product workflows and independent SDK canary #30 passed. Refs DEN-1565 and DEN-1507.
Honor !target, !target/, and !target/** overrides for built-in target exclusions while preserving unrelated defaults and later re-exclusions. Exact-head CI, Nix, and agent-policy checks passed.
Merge after successful exact-head checks and an immediate mergeability, review, draft, repository-state, and operational-policy refresh.
…rust-dart-and-type into main (graft, scaffolding reconciled)

`rescue/orphan-762071627a6a-feat-publish-isolated-rust-dart-and-type` was recovered from a dangling commit and shares no history with `main`. This is a real two-parent merge
built with plumbing (no checkout). Every path the orphan adds is taken verbatim (138 file(s)). The overlap was
scaffolding only:
  .gitignore: union (8 extra rule(s) carried over)
  kept main's current version: .zpkg.toml README.md 
The orphan's own copies remain readable at `git show 7620716:<path>`.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KAAGBnXTSw7zE5xnY4tiBY
@ORESoftware
ORESoftware merged commit 08ab0f7 into main Sep 12, 2026
9 of 16 checks passed
@ORESoftware
ORESoftware deleted the graft/rescue-orphan-762071627a6a-feat-publish-isolated-rust-dart-and-type-20260905 branch September 12, 2026 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant