Storage: Bool/Uint8/Bytes32 scalars, packed bool/address slots and FixedArray Uint256 gaps cannot be declared (solc layout parity)

Found while declaring the real solc 0.8.10 storage layout of the Pareto Credit Vault contracts (IdleCDOEpochVariant, IdleCreditVault) as verity_contract storage on top of #2413.

Rejected declarations (all needed for a layout-faithful model):

flag : Bool := slot 0            -- error: storage field cannot be Bool; use Uint256 (0/1) encoding
flag : Uint8 := slot 286         -- error: storage field cannot be Uint8; use Uint256 encoding
gap : FixedArray Uint256 49 := slot 1   -- error: storage fixed arrays currently support only Uint128 elements
b : Bytes32 := slot 1            -- error: storage field cannot be Bytes32; use Uint256 encoding

Consequences on the Pareto layout (IdleCDOEpochVariant):

Only narrow UintN/Uint16 fields participate in automatic packing (applyAutomaticPackedLayout), Address resets the packing cursor, and one word-sized field per slot is enforced, so none of these slots can be declared. The OZ uint256[49] __gap arrays and bytes32 _lastCallerBlock are also not declarable.

Workaround used in the closure repo: 0/1 words, offset-0 member at the physical slot, other packed members at a documented logical slot 1000000 + slot*1000 + offset, gaps undeclared.

Ask: allow Bool/Uint8 (1-byte) and Address (20-byte) members in the automatic packing cursor with their Solidity offsets, FixedArray Uint256 n storage, and Bytes32 scalars.

Closure-side tracking: audit/VERITY-GAPS.md G4/G17.

Start with applyAutomaticPackedLayout and the storage declaration errors, using the rejected Bool, Uint8, FixedArray Uint256, and Bytes32 declarations as cases. Compare the requested Solidity offsets and slot behavior with the workaround documented in audit/VERITY-GAPS.md; done means these declarations are accepted with packed offsets, Uint256 fixed arrays, and Bytes32 scalars.