|
2472 | 2472 | "revision": 5, |
2473 | 2473 | "date": "2026-10-20", |
2474 | 2474 | "change": "fixtures.knownGaps[2]'s release attribution corrected — round 10 of wave anchor #24579. The line said the walled boot refusal was 18.0's ('the 18.0 refusal') and that 18.x step 4 (#24580) deleted it, so a runner on 18.0.0 could not tell whether its release boots the walled posture. Under ruling record 6282882793 on the v18 epic (items 1 and 2), 18.0.0 is published only after step 4 has merged, and a walled posture boots on it. Of the published @objectstack/cli prereleases only 18.0.0-next.5 carries serve.ts walledPostureRefusal: next.0 to next.3 predate it, measured in each npm tarball and at each version tag, and no next.4 was published. Only that attribution changed: no clause, step or other knownGap moved", |
2475 | | - "ref": "#PENDING-24579R10" |
| 2475 | + "ref": "#24788" |
2476 | 2476 | } |
2477 | 2477 | ] |
2478 | 2478 | }, |
|
2621 | 2621 | "revision": 7, |
2622 | 2622 | "date": "2026-10-20", |
2623 | 2623 | "change": "fixtures.knownGaps[0]'s release attribution corrected — round 10 of wave anchor #24579. The line said the walled boot refusal was 18.0's ('the 18.0 refusal') and that 18.x step 4 (#24580) deleted it, so a runner on 18.0.0 could not tell whether its release boots the walled posture. Under ruling record 6282882793 on the v18 epic (items 1 and 2), 18.0.0 is published only after step 4 has merged, and a walled posture boots on it. Of the published @objectstack/cli prereleases only 18.0.0-next.5 carries serve.ts walledPostureRefusal: next.0 to next.3 predate it, measured in each npm tarball and at each version tag, and no next.4 was published. Only that attribution changed: no clause, step or other knownGap moved", |
2624 | | - "ref": "#PENDING-24579R10" |
| 2624 | + "ref": "#24788" |
2625 | 2625 | } |
2626 | 2626 | ] |
2627 | 2627 | }, |
|
2954 | 2954 | "revision": 6, |
2955 | 2955 | "date": "2026-10-20", |
2956 | 2956 | "change": "source[5] and source[7] re-pointed — the two comma-range line citations round 9 of wave anchor #24579 left, because PR #24667 held the item then (round 9's report 6283532816, out_of_scope_findings[0]). At the authoring commit 45397edf53, line 200 of env.ts was the resolvePlatformOwnerEmail declaration and line 261 of admin-routes.ts was the DATASOURCE_ADMIN_CAPABILITY declaration. At base 795ff708d8 source[5] anchors both PLATFORM_OWNER_EMAIL_ENV and resolvePlatformOwnerEmail in env.ts, and source[7] anchors the DATASOURCE_ADMIN_CAPABILITY declaration in admin-routes.ts instead of the string literal manage_platform_settings. All three resolve as declarations in the shared resolver. The ',NNN' residue is what #13786's strip left of a two-range list. No clause, step or other field changed", |
2957 | | - "ref": "#PENDING-24579R10" |
| 2957 | + "ref": "#24788" |
2958 | 2958 | } |
2959 | 2959 | ] |
2960 | 2960 | }, |
|
3499 | 3499 | "revision": 4, |
3500 | 3500 | "date": "2026-10-20", |
3501 | 3501 | "change": "fixtures.knownGaps[0]'s release attribution corrected — round 10 of wave anchor #24579. The line said the walled boot refusal was 18.0's ('the 18.0 refusal') and that 18.x step 4 (#24580) deleted it, so a runner on 18.0.0 could not tell whether its release boots the walled posture. Under ruling record 6282882793 on the v18 epic (items 1 and 2), 18.0.0 is published only after step 4 has merged, and a walled posture boots on it. Of the published @objectstack/cli prereleases only 18.0.0-next.5 carries serve.ts walledPostureRefusal: next.0 to next.3 predate it, measured in each npm tarball and at each version tag, and no next.4 was published. Only that attribution changed: no clause, step or other knownGap moved", |
3502 | | - "ref": "#PENDING-24579R10" |
| 3502 | + "ref": "#24788" |
3503 | 3503 | } |
3504 | 3504 | ] |
3505 | 3505 | }, |
|
3838 | 3838 | "revision": 5, |
3839 | 3839 | "date": "2026-10-20", |
3840 | 3840 | "change": "fixtures.knownGaps[0]'s release attribution corrected — round 10 of wave anchor #24579. The line said the walled boot refusal was 18.0's ('the 18.0 refusal') and that 18.x step 4 (#24580) deleted it, so a runner on 18.0.0 could not tell whether its release boots the walled posture. Under ruling record 6282882793 on the v18 epic (items 1 and 2), 18.0.0 is published only after step 4 has merged, and a walled posture boots on it. Of the published @objectstack/cli prereleases only 18.0.0-next.5 carries serve.ts walledPostureRefusal: next.0 to next.3 predate it, measured in each npm tarball and at each version tag, and no next.4 was published. Only that attribution changed: no clause, step or other knownGap moved", |
3841 | | - "ref": "#PENDING-24579R10" |
| 3841 | + "ref": "#24788" |
3842 | 3842 | } |
3843 | 3843 | ] |
3844 | 3844 | }, |
|
3936 | 3936 | "revision": 4, |
3937 | 3937 | "date": "2026-10-20", |
3938 | 3938 | "change": "fixtures.knownGaps[0]'s release attribution corrected — round 10 of wave anchor #24579. The line said the walled boot refusal was 18.0's ('the 18.0 refusal') and that 18.x step 4 (#24580) deleted it, so a runner on 18.0.0 could not tell whether its release boots the walled posture. Under ruling record 6282882793 on the v18 epic (items 1 and 2), 18.0.0 is published only after step 4 has merged, and a walled posture boots on it. Of the published @objectstack/cli prereleases only 18.0.0-next.5 carries serve.ts walledPostureRefusal: next.0 to next.3 predate it, measured in each npm tarball and at each version tag, and no next.4 was published. Only that attribution changed: no clause, step or other knownGap moved", |
3939 | | - "ref": "#PENDING-24579R10" |
| 3939 | + "ref": "#24788" |
3940 | 3940 | } |
3941 | 3941 | ] |
3942 | 3942 | }, |
|
0 commit comments