Verify a change
Updated
A workspace edit is done when four steps have passed and modelVersion of
each touched model is raised. The default core on a local stand is
http://localhost:5257.
Note
If the sync log is empty, check the fuse first:
GET /api/dev/workspace/sync-status. When too many files differ from the last export, sync stops applying anything, including your new files. The symptom looks like "sync died". It is alive and refusing.
How to#
0. Sync status. If held is true and the quarantine is not yours, do
not resume. sync-resume discards the files (discarded: N) and rewrites
the disk from the database. If you already wrote .cs while the gate was
closed, those bytes vanish.
1. Sync applied the file (~2–4 s after save): look for applied, not a
warning. A Core-gate or security-policy refusal is rewritten from the
database; do not fight the export.
2. Compile: POST /api/metadata/models/compile — every model Ok.
3. Schema: POST /api/schema/sync — physical tables for new objects.
4. Tests: an integration test per scenario, then
POST /api/metadata/tests/run-all.
Tip
Two instances sharing one workspace folder (SQL Server and Postgres) share the disk and not the database.
sync-resumeon the second rewrites the folder from its database and undoes what the first just accepted. Do not touch the gate on the second instance.
A script that uses the filesystem, the network, processes, or reflection around the platform is refused on import. Outbound I/O is the outbound seam, by channel name.
What's not there yet#
Live sync on a dev stand is not a substitute for the version bump. Tenants never see the file; they see the number.