Repository navigation
Propose fixed Bookworm parents and shared early APT check - #309
Conversation
|
Shared source proposal is now draft #309, exact The official Bookworm fixed pair is apt/libapt-pkg6.0 2.6.2, per Debian DLA-4880-1 and package records linked in the source README. Exact old index
Stock public Registry v2 metadata GETs authenticated the previously qualified exclusive CA/curl authority, each raw descriptor size/SHA256, native config architecture/PHP_VERSION8.4.27 and each SPDX child subject. Original old-parent inventory:6.827s/12876152B; distinct candidate discovery+inventory:6.574s/12876262B, each within120s+5/10MiB per object/24MiB total. Anonymous registry tokens remained memory-only. No rootfs layer, image pull, container, installed executable, APT, build or publisher ran. Metadata is publisher SOURCE evidence, not installed qualification.
Five focused consumed tests cover both fixed native positives, old/one-unfixed-member refusal, incomplete/duplicate/status/version/architecture/release/override negatives and no Python/PATH requirement. Full99 CI-trust controls and existing fixed-APT source controls pass; ordinary policy validation passes. Fresh current-head checks and normal central source review are pending. cli owns this central source, Sample owns later narrow adoption, General retains actual fixed-image/build/publisher selection. Initial297 root/setup qualification remains a separate profile/effect gate. |
|
The original native required job42112617052/127543816324 correctly refused because protected main moved from2928 to accepted308 c78c949 while that source snapshot was being checked. This was an actual protected-base identity refusal, not an archive/guard failure. The initial The branch is refreshed normally over accepted main c78c949; the five proposed source files and CI test collection are unchanged. Fresh current-head native/ordinary results now apply. Source/data review remains distinct from any fixed-parent pull/build/installed/publisher effect. |
|
Security SOURCE PASS — exact refreshed pair I independently read the complete five-path delta and reran This guard is deliberately a fixed-client floor preflight, not an exact-parent selector or a package-transaction quiescence verifier. The recorded old/fixed publisher descriptors remain inventory only, accurately declare that layers/rootfs/installed qualification were not performed, and do not admit the mutable discovery tag as a build selector. The README keeps consumer adoption, immutable accepted-central pinning, Docker-context/COPY order, actual image qualification, build, publication, and every operating effect as later gates. Current required checks are 9/9 successful, including the refreshed protected native-policy subject; the earlier stale protected-main refusal is not carried. This is a narrow source disposition only: no image pull/build, installed-image result, caller wiring, publication, or release effect is accepted here. |
|
Required checks on1978c6f are green, but direct public Sonar issue read found two first-party critical S131 findings: omitted explicit default shell cases. I corrected both locally as no-op defaults (unrelated os-release keys and valid versions), preserving all refusal logic. Local successor I am keeping this draft unmerged while the higher-priority exact manual-wiring#310 completes its source flow, then will refresh/push this useful correction over actual accepted main once. This avoids consuming another known stale protected-base check. The existing exact-source review and corrected Git identities remain durable; no image/installed/caller/build/publication effect is selected. |
|
Useful source successor is pushed: The original source PASS6670100699 remains correctly bound to1978c6f/tree742f8fa6. This successor does not claim a new image/installed/caller/build/publication effect. The manual initial hosted setup workflow inherited from accepted310 is separate, with no dispatch selected. Current initial-run proposal will use actual protected main after source acceptance, keeping its required expected_workflow_sha check honest. |
|
|
Security incremental SOURCE carry — current exact Relative to the reviewed PR #309 implementation, the only source change is two explicit no-op default arms in All current required checks are 9/9 successful, including Shared, SonarQube/SonarCloud, CodeQL, parser controls, and protected native policy. The prior SOURCE PASS at comment 6670100699 carries across this narrow current successor. No caller adoption, image pull/build, installed qualification, dispatch, publication, or release effect is accepted. |
|
Normal source integration is accepted at actual main cli completed the exact official two-architecture old/fixed PHP8.4.27 Bookworm publisher inventory, shared stock-shell early preflight and immutable-central-checkout/local-COPY source route. No caller is wired and no image/layer was pulled, built or executed. Next owners: Sample App owns its narrow concrete consumer diff after General's adoption selection, preserving both stages/platforms and early Brotli/later Playwright ordering; cli owns central source/qualification follow-through, General owns actual fixed-image/build/publisher effects. The initial hosted297 operation is distinct and does not qualify this image profile. The separate initial297 workflow remains byte-identical c94, immutable helper1b; the complete operation proposal is297/6670269900 and independent EFFECT-PACKET PASS6670345192. WorkflowID408671560 still has zero runs. General must distinctly select any original dispatch after immediate precondition rereads; no effect was inferred from source acceptance. Owned branch/worktree are clean and exact remote ref/ancestry/tree checks match; no open dependent PR uses the branch. Only those exact owned refs/worktree are removed. Source data/evidence, public caches and other owners' worktrees remain. |
|
Security SOURCE PASS — exact central PR #309 head Against current base Independent source checks:
This accepts the bounded common source/profile only. It does not qualify an installed image, caller wiring, image pull/build, APT execution, package mutation, or publication effect. |



Sample App's two PHP8.4.27 Bookworm stages run the APT-using Brotli helper before Python exists; the final stage later runs direct APT and Playwright
--with-deps. Add one shared stock-shell preflight and exact official fixed-parent source record for both amd64 and arm64. The README supplies the narrow future adoption route through immutable central checkout/local COPY, without a committed per-repo guard or external-image fallback.The publisher-source record binds old/fixed indices and both native child/config/attestation/SPDX descriptor sizes/SHA256. Old54b records APT/libapt2.6.1; proposed b3e907a1 records2.6.2 on both, preserving PHP8.4.27 and matching Debian's Bookworm fixed floor. Bounded public metadata GETs verified raw descriptors and child subjects; no rootfs layer or image was fetched/executed. The tag was discovery only, never a proposed build selector.
The read-only shell checks effective Debian12/native installed apt+libapt-pkg6.0, installed status and both >=2.6.2 floors with stock dpkg. It refuses malformed/incomplete/duplicate/foreign/unfixed inputs and all overrides. It needs no Python, APT, download or repair. No caller is wired; actual parent/tool/installed/image qualification, consumer source adoption, build and publication remain separate General/owner gates. The hosted initial PHP setup job inherited from accepted#310 is a different profile with no selected dispatch.
Validation:125 consumed CI-trust/protected-context/native-workflow tests and complete ordinary policy validation pass; nine exact-head contexts succeed; direct Sonar open/confirmed issues zero. The five guard/record test methods include fixed-pair positives on both native architectures, old and individually unfixed member refusals, status/version/duplicate/architecture/release/override negatives and no Python/PATH requirement. Security source PASS6670100699 binds the implementation at1978c6f/tree742f8fa6; the final quality delta only makes two existing no-op default cases explicit, plus accepted310 source carry. No new independent verdict or operating effect is inferred from the ordinary source integration.
Tracks #295; #297 hosted setup qualification remains separate.