changelog.d/4994-artifact-projects-default.md

Rama main · réplica de lectura del repositorio original.

- **Artifact Projects are on by default (#4994).** Migration `20261105094324_artifact_projects_default_on` turns the `artifact_projects` instance default on, but only where the flag is still the untouched seed: an administrator who ever changed the instance flag (`crewship feature-flag update`, `PATCH /api/v1/feature-flags/artifact_projects`, manifest apply), or deleted or recreated it, keeps that choice, and workspace overrides are left alone. Turn Projects off for one workspace with `crewship feature-flag disable artifact_projects`, or for every workspace without an override with `crewship feature-flag update artifact_projects --enabled=false`; existing projects are kept, the routes answer `404` and availability reports `{"enabled": false}`. `CREWSHIP_ARTIFACT_PROJECTS_ENABLED=true` still forces Projects on. Dashboard data, Slides, Design and live workbook editing stay off by default, and the default production web build is unchanged.
- **Project links open in Artifacts (#4995).** Create, publish, restore and share now return `url` = `/artifacts/<page_id>?workspace_id=<ws>` (share: `/artifacts/<page_id>?version=<N>&workspace_id=<ws>`) instead of `/pages/<slug>?artifact=1…`. Old `/pages/<slug>?artifact=1[&version=N]` links keep working: with the Artifacts library in the build they redirect to `/artifacts/<page_id>` with the same workspace and version, otherwise they open the Pages project viewer. A shared-version link shows the shared version, never Latest; in a build without the library, `/artifacts/<page_id>` goes to `/pages/@<page_id>?artifact=1`.