---
id: PLN-0083
ticket: render-frame-packet-boundary
title: Fade Removal
status: done
created: 2026-05-25
ref_decisions: [DEC-0030]
tags: [gfx, renderer, runtime, frame-composer, architecture, ui, pipeline]
---

## Briefing

Source decision: `DEC-0030`.

Remove fade fields, syscalls, packet members, renderer state, tests, and docs from canonical render contracts.

## Target

Fade is no longer a render pipeline feature. Future visual transitions remain the responsibility of `RenderManager` and require separate product/domain work.

## Scope

- Remove fade from specs, HAL packet types, syscall metadata, runtime state, renderer state, tests, and PBS declarations.
- Remove or update tests that assert fade behavior.
- Add guard tests or searches that prevent reintroducing fade in canonical render contracts.

## Out of Scope

- Implementing replacement visual transitions.
- Replacing fade with another transition API.
- Preserving backward compatibility for fade syscalls.

## Execution Sequence

1. Inventory all fade references in specs, crates, tests, examples, and PBS stdlibs.
2. Delete fade fields and syscalls from canonical ABI and packet definitions.
3. Remove renderer/runtime fade state and behavior.
4. Update callers and tests to stop setting or expecting fade.
5. Add documentation language that transitions belong to `RenderManager`.
6. Run targeted and full affected tests.

## Acceptance Criteria

- No canonical packet, syscall, or render contract contains fade.
- Runtime and renderer code do not maintain fade state.
- Tests no longer depend on fade behavior.
- Specs clearly state future transitions are `RenderManager` responsibility.

## Tests / Validation

- Run `rg -n "\\bfade\\b|Fade" specs crates discussion/workflow` and verify remaining references are only historical decision/agenda text or explicit removal notes.
- Run affected unit and integration tests.
- Add regression tests preventing fade fields in current packet types.

## Risks

- Removing tests can reduce coverage; replace fade-specific assertions with packet/transition boundary assertions where appropriate.
- Historical discussion files may keep fade references; do not rewrite history unless the framework requires it.

## Affected Artifacts

- Specs
- HAL, runtime, renderer, syscall, PBS, and tests under `crates/`