# Scaffold registry lane severity annotations

## Why this note exists

This train adds `sync_lane_severity` annotations to the scaffold registry schema and moves external sync lane-severity ownership from hardcoded script sets into registry metadata.

The change is intended to keep project sync behavior the same while making the registry the single edit point for paths that need critical manual-merge handling or optional-feature-selection treatment.

## Applies to

- Template-derived projects that use `/external sync` or `pnpm sync:apply` from the Elevasis monorepo.
- Projects that receive `@elevasis/core` package-baseline updates through `core/package.json` or `operations/package.json`.
- Operators reviewing external-sync plans that mention critical manual-merge or optional-feature-selection paths.

## Required actions

1. Run the prepared external sync from the release train so this note reaches derived projects.
2. After the `@elevasis/core` publish stage, install the prepared core package baseline in template-derived project package files.
3. Review any sync plan lane labels against the registry entry metadata before widening a manifest or applying catch-up work.

No project-authored Organization Model content should be overwritten for this train.

## Verification

```bash
pnpm sync:verify
pnpm exec tsx scripts/external/sync-apply.ts --all --dry-run --manifest apps/docs/content/docs/in-progress/active-development/sdk-changes/ship/_external-sync-prep.json --strict-manifest
```

The strict manifest dry-run should authorize only the prepared sync note and the core package-baseline cascades.

## Not handled by /git-sync

`/git-sync` can deliver committed file changes, but it does not publish `@elevasis/core`, install package baselines, validate scaffold registry metadata, or enforce manifest-scoped external-sync write authorization.
