build(release): publish the vendored framework and the native packages publicly

The three release sequences shipped with publishConfig.access: restricted, so
nothing in the @deepseek-ai scope was installable from outside the organization.

A restricted dependency is what actually blocks a public consumer: every harness
package declares the vendored framework as a peerDependency, and
dsh-sandbox-local declares the Landlock entry as a dependency. Those two
sequences therefore go public first — the nine vendor/* packages and the three
native/landlock-run packages — while the dsh family stays restricted until its
own sequence is opened deliberately. No public package requires a restricted one
in this arrangement.

Access is now per sequence, so no publish path can pass --access: one flag
cannot express two levels and would override the manifest that owns the fact.
publish.ts stops passing it, matching the native workflow, and
check-workspace-constraints holds each manifest to its own sequence's level,
which is what stops the scope from drifting one package at a time.

Harness consumers reference the Landlock entry as workspace:^ instead of
workspace:*, so a published harness package accepts the entry's patch and minor
releases. The entry keeps workspace:* for its platform packages, where the
binary must match the entry version exactly.

Two rationales that named a private registry no longer describe the vendored
sequence; they now state the durable reason, which is that the verification must
not depend on the registry already carrying matching versions.

scripts/release/publish.ts

@@ -20,9 +20,6 @@ import { releaseFamily } from './families.ts'
 import { attempt, isEntry, run } from './process.ts'
 import { packedIdentity, readPublishOrder } from './tarball.ts'
 
-/** npm access level for every package this repository publishes. */
-const ACCESS = 'restricted'
-
 /** What the registry knows about one version. */
 type RegistryState =
   | { readonly kind: 'absent' }
@@ -91,7 +88,11 @@ function main(): void {
     }
     // A prerelease version never takes the latest dist-tag.
     const tagArgs = version.includes('-') ? ['--tag', 'next'] : []
-    run('npm', ['publish', tarball, '--access', ACCESS, ...tagArgs])
+    // No --access: the sequences do not share one access level, so a
+    // command-line flag could not serve both and would override the manifest
+    // that does. Each packed manifest decides, and
+    // check-workspace-constraints holds every manifest to its sequence's level.
+    run('npm', ['publish', tarball, ...tagArgs])
     published += 1
   }