rejected 53b6bc82-80d8-4164-84c1-84ab603a3559
package_import, authoring_guide, cid_logicInvestigate why a package authored from the local public-data portable package development guide can fail PWA package import with: blob key bencid:v0:blob:sha256:462c8adbf77c26abdb6fce207bd490bacff372e53fb63064a95482aa1ba95df1 is not a valid CID; skipping: CID body is not valid lowercase RFC 4648 base32: invalid symbol at 5.
Scope: do not fix or validate the specific package at /home/johnb/Downloads/benac_qwen3_4b_q4f16_webgpu_package.zip. Use the error only as a symptom. Investigate the authoring guide at /home/johnb/Downloads/benac-local-public-data-portable-package-development-guide-cleaned.md, the requirement/source records if relevant, and the business logic for package import and artifact availability. Determine whether the guide, requirements, business logic, or a combination is wrong.
Acceptance: identify root cause, update guide/requirements/business logic as needed, add focused tests or validation checks for the corrected contract, build/test, push to main, deploy if runtime/UI behavior changes, and propose resolution only after git/worktree state is clean and current.
Investigation completed without code changes. The guide appears correct on CID form and artifact availability: it uses DASL b... CIDs and package.benac-capsule.json, not bencid:v0 or ZIP. The observed bencid:v0 warning comes from stale browser IndexedDB blob keys during startup hydration, not from the selected package file. The current PWA import path only supports capsule JSON text and does not unzip package archives; requirements are strong on CID semantics but weak on explicit browser import container/diagnostic wording.
Intake phase complete. Confirmed operator MCP tools/list on the local unauthenticated sidecar, created and fetched the ticket, and scoped the work away from validating the specific package. Investigation phase will compare the provided authoring guide, requirements/term records, and package import/artifact availability business logic to determine the contract mismatch behind bencid blob keys being parsed as lowercase RFC 4648 base32 CIDs.
Investigation phase complete. The provided guide already defines portable CIDs as DASL b-prefixed lowercase RFC 4648 base32 strings and contains no bencid:v0 strings; its build/import examples use package.benac-capsule.json, not ZIP. The PWA package UI accepts and reads only capsule JSON, but it does not explicitly reject ZIP files, so a user can hit a confusing generic import path. Separately, the exact console warning comes from IndexedDB hydration of old blob-store keys, where stale pre-DASL bencid:v0:* local blobs are parsed as current Cids and skipped. Requirements also leave local import format behavior too broad: they say local import supports packages, bundles, and capsules from files without requiring supported file encodings and unsupported archive/container formats to be surfaced before CID parsing. Implementation phase will make the PWA import failure explicit for ZIP and legacy bencid content, make the stale IndexedDB warning actionable, clarify the requirement/term wording, and add a guide note that baseline browser import consumes capsule JSON rather than ZIP archives.
Correction phase complete. The handler prematurely edited PWA import UI, IndexedDB warning text, and two source records after the first investigation pass. The caller stopped that work. All uncommitted edits in apps/pwa/src/ui/package_panel.rs, apps/pwa/src/indexeddb_persistence.rs, records/req.benac-io-001/benac-io-001.md, and records/term.package-bundle/package-bundle.md were reverted; git status is clean on main. The final phase is investigation-only: document the guide/requirements/business-logic finding without code, build, deploy, or push.
Investigation-only resolution proposed. Root finding: the reported console warning is produced by PWA IndexedDB hydration, not by package-file import. apps/pwa/src/indexeddb_persistence.rs walks persisted blob-store keys at startup and parses each key as the current DASL Cid; stale pre-DASL keys like bencid:v0:blob:sha256:... begin with b, pass the first-character prefix check, then fail lowercase RFC 4648 base32 decoding on the colon. The provided authoring guide is not telling authors to emit bencid:v0: it defines raw blob and structured document CIDs as b-prefixed lowercase base32 DASL CID strings and its command examples build, validate, inspect, and import package.benac-capsule.json. The PWA package panel only imports capsule JSON: it labels the control Import capsule file, accepts .json/.benac-capsule.json/application/json, reads the selected file as text, then deserializes it as benac_core::capsule::Capsule. It does not unzip package archives. Requirements are correct on CID semantics and artifact role/CID-codec resolution; BENAC-IO-001 is broad enough to allow local file import but does not specify browser-supported concrete container formats or the diagnostic expected when a user selects an unsupported archive. No source changes remain: the premature edits were reverted, git status is clean on main, and no build, push, or deploy was performed.
Caller cancelled the ticket: this should have never been a ticket
Sign in as a human to drive this ticket from the page, or use the MCP tools.
Ticket created: Investigate bencid blob key import mismatch for authored packages