Audit clean Atomic table pin compatibility before migration #121

Open
michielbdejong wants to merge 1 commit from michielbdejong/clean-table-pin-compatibility into main AGit
Owner

Updating ELFA's Atomic gitlink to the clean extraction stack would remove APIs already used by the delivery app and the grid experiment. Record the compatibility work before changing that pin.

The reproducible source audit finds 72 imported table API names: all are present at the current afea6cc pin, while 45 are absent from clean validation batch bd4fa0e. Including test helpers gives 73 names and 46 missing. The plan also records signature/behavior differences in editors and quick-add helpers, the shared-UI file dependency/build requirements, and the migration/parity gates.

Add a source-level checker and its JSON inventory; link the plan from the existing port assessment. The checker does not claim signature, packed-consumer or runtime compatibility. Missing names are a checklist, not a request to copy the deferred state framework back into clean UI.

Validation: Node syntax; existing-pin positive oracle (zero missing) and clean-candidate negative oracle (expected nonzero) in both source scopes; diff/whitespace checks. No application, package, lockfile or submodule changes. Actual ELFA migration/type/build/browser gates remain unfinished; the gitlink stays afea6ccef5356560ae71b965e1a6d40fa9512f8a.

Upstream review map: https://github.com/ontola/atomic-server/pull/2536#issuecomment-6973727487

Updating ELFA's Atomic gitlink to the clean extraction stack would remove APIs already used by the delivery app and the grid experiment. Record the compatibility work before changing that pin. The reproducible source audit finds 72 imported table API names: all are present at the current `afea6cc` pin, while 45 are absent from clean validation batch `bd4fa0e`. Including test helpers gives 73 names and 46 missing. The plan also records signature/behavior differences in editors and quick-add helpers, the shared-UI file dependency/build requirements, and the migration/parity gates. Add a source-level checker and its JSON inventory; link the plan from the existing port assessment. The checker does not claim signature, packed-consumer or runtime compatibility. Missing names are a checklist, not a request to copy the deferred state framework back into clean UI. Validation: Node syntax; existing-pin positive oracle (zero missing) and clean-candidate negative oracle (expected nonzero) in both source scopes; diff/whitespace checks. No application, package, lockfile or submodule changes. Actual ELFA migration/type/build/browser gates remain unfinished; the gitlink stays `afea6ccef5356560ae71b965e1a6d40fa9512f8a`. Upstream review map: https://github.com/ontola/atomic-server/pull/2536#issuecomment-6973727487
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin '+refs/pull/121/head:michielbdejong/clean-table-pin-compatibility'
git switch 'michielbdejong/clean-table-pin-compatibility'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'main'
git merge --no-ff 'michielbdejong/clean-table-pin-compatibility'
git switch 'michielbdejong/clean-table-pin-compatibility'
git rebase 'main'
git switch 'main'
git merge --ff-only 'michielbdejong/clean-table-pin-compatibility'
git switch 'michielbdejong/clean-table-pin-compatibility'
git rebase 'main'
git switch 'main'
git merge --no-ff 'michielbdejong/clean-table-pin-compatibility'
git switch 'main'
git merge --squash 'michielbdejong/clean-table-pin-compatibility'
git switch 'main'
git merge --ff-only 'michielbdejong/clean-table-pin-compatibility'
git switch 'main'
git merge 'michielbdejong/clean-table-pin-compatibility'
git push origin 'main'
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ELFA/database-apps!121
No description provided.