Skip to content

Scope native staging key to build and use Pages page size 20 - #79

Merged
callumalpass merged 1 commit into
release/native-stagingfrom
fix/reader-extension-manifest-check
Oct 20, 2026
Merged

callumalpass merged 1 commit into
release/native-stagingfrom
fix/reader-extension-manifest-check

Conversation

@callumalpass

Copy link
Copy Markdown
Contributor

Parent actual-delta approval of qualified local16b2/tree724a. Concrete run39407095310/a1 failed in default-LAB extension manifest generation because staging public key was inherited at job scope. Move that PUBLIC input only to actual target build step; keep all staging key/ID/environment guards and original-byte checks. Add one YAML-bound causal regression. Co10:42: change Reader Pages list per_page100 to20 and assert that existing request; commit/URL/branch/UUID matching unchanged. Three files +31/-4. No dependencies/SDK/vendor/lock or new helper/proof mechanism.

Qualifications: actual matching-error RED171/1 then full check PASS (publisher172, Reader450+39, extension187, Connect167, lint/format/types/architecture). After late page20 addition, final publisher172, lint/format/actionlint PASS. No product compilation/repack. f5 historical local output and bee4 failed operational source remain distinct.

Source PR against release/native-staging only. Parent authorized normal SHA-bound merge and ONE necessary fixed-source operational publisher; no production authority.

@callumalpass
callumalpass merged commit 5353694 into release/native-staging Oct 20, 2026
@callumalpass
callumalpass deleted the fix/reader-extension-manifest-check branch October 20, 2026 10:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant