[BUG] FAT snapshot access and internal enum layouts fail strict validation #14
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/fatd#14
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
FAT snapshot access and internal enum layouts fail strict validation. Maintained validation cannot reach its intended successful boundary.
Reproduction
Run the maintained strict Clippy, unit and warning-denied documentation workflow against the original signed component graph. The original failing source and current repairs are distinct; failures and true exit statuses are retained.
Expected and actual behavior
The maintained source should compile, discover its original controls and complete the specified checks without warnings. A metadata selector is inaccessible to its actual store sibling, and malformed permission result identifiers prevent compilation. Large internal variants retain redundant path/name payloads and fail strict Clippy; the transaction selects only one created or renamed child.
Environment and identity
Evidence and prior checks
Repair the actual source and existing independent controls in the owning repository. Preserve full-width identity, noncopyable ownership, exact wire and persistent formats, original effects and refusal boundaries. Tests and exact signed-head CI run independently alongside the source repairs; no pending or skipped check is a pass.
Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired.
Tracking
Phase completion tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.