Make ordinary config values readable consistently on Fastly #324

Description

This reported inconsistency is fixed on main. Fastly config reads transparently resolve EdgeZero chunk pointers while returning ordinary strings, direct envelopes and unrelated JSON verbatim. Envelope verification remains in the typed app-config layer. The original report described an earlier envelope-only implementation.

Steps to reproduce

Historical reproduction: read a plain string through Fastly ConfigStore::get and compare it with Axum/Cloudflare.

Current source inspection: current raw-value/chunk-pointer resolution contract returns non-pointer values unchanged; checked-in arbitrary-value regression covers ordinary text, empty/whitespace values, scalars, unrelated JSON and malformed JSON without fetching chunks. No tests were executed during this audit.

Expected behavior

Ordinary config values are readable consistently across adapters, while Fastly can still resolve its explicit reserved chunk-pointer format.

Impact

The original Fastly-only failure prevented uniform config-store use for plain flags, lists and key material. The mainline passthrough behavior removes the need for the reported custom plain-store workaround.

Proposed fix

No further fix is required for the reported bug. Close as completed based on merged PR #314 and the current implementation/regression evidence. Values explicitly claiming an unknown reserved edgezero_kind still fail closed by design.

Done when

• Fastly returns non-pointer values verbatim.
• Typed app-config decoding owns direct-envelope parsing and integrity checks.
• Explicit EdgeZero chunk pointers continue resolving with integrity checks.
• Regression coverage includes ordinary values and proves no chunk fetch is made for them.

Related

PR #314 delivered the fix; current raw-value/chunk-pointer resolution contract; checked-in arbitrary-value regression.