# Known Limitations

Status: Stage 10 release readiness

This document keeps planned functionality separate from implemented V1 behavior.
It should be updated before every release.

## Compression

V1 supports raw storage and a deterministic stored-block zlib profile. The zlib
profile validates container and codec plumbing, but it is not a real compression
ratio feature yet. It does not expose compression levels, dictionaries, or
adaptive codec selection.

## Metadata

Hot metadata supports basic listing and extraction. Cold metadata and manifest
sections are present as reserved architecture pieces, but rich query features are
not complete.

## Integrity

Payload integrity metadata detects accidental corruption. It is not a
cryptographic authenticity mechanism and does not replace signatures.

## Recovery

Recovery metadata and sidecar files are reserved. Full archive repair after
arbitrary damage is not implemented as a V1 guarantee.

## Filesystem

Regular files and directories are supported. Symlinks are rejected. Extended
attributes, permissions, ownership, sparse files, and platform-specific metadata
are deferred.

## Append and Rewrite

Selected extraction exists. Full append transactions, rewrite preservation of all
unknown optional metadata, and random-access mutation are deferred.

## SDK Stability

The V1 SDK targets source compatibility. ABI compatibility is not guaranteed.

## Auto Compression

`--compression auto` chooses the smallest currently available encoded payload per
file. Because V1 zlib is still stored-block based, this mode is mainly useful as
a policy foundation and usually selects raw payloads today.

## CI

Repository-side local release gate tooling exists, but GoCD pipelines and
dedicated Windows/Linux CI workers are not part of the current local repository
state. Windows and Ubuntu CI plan printers document intended job flow, but they
do not replace real machine execution.

## Security Testing

Local corruption, mutation, path, overwrite, and CLI contract tests exist.
Fuzz seed corpus generation and smoke validation exist. Coverage-guided fuzzing,
sanitizer CI, and platform-specific metadata abuse tests are deferred until the
dedicated CI machines are available.
