Skip to content

fix: correct APTL and LilRAE boundary - #297

Open
Brad-Edwards wants to merge 1 commit into
devfrom
296-correct-aptl-lilrae-boundary
Open

fix: correct APTL and LilRAE boundary#297
Brad-Edwards wants to merge 1 commit into
devfrom
296-correct-aptl-lilrae-boundary

Conversation

@Brad-Edwards

Copy link
Copy Markdown
Collaborator

Summary

Correct the repository's ecosystem model so APTL and LilRAE are one project across a rename, TechVault remains only a scenario pack, and no stale runtime-layer assumption weakens CodeQL coverage or authoring guidance.

Requirement UIDs

  • (none — bug/refactor/maintenance run; see Traceability section below)

Related Issues

Closes #296

ADR Impact

  • ADR-009
  • ADR-021
  • ADR-036

Changes

  • Correct current-role APTL references to LilRAE while stating rename continuity and keeping TechVault only a scenario pack.
  • Preserve APTL-era provenance and compatibility identifiers, update adapted SDL provenance, and regenerate the exact pack artifact manifest.
  • Remove dead TechVault runtime path exclusions so CodeQL scans the complete repository.
  • Strengthen ownership, CodeQL, and Ground Control plan-rule regression tests.

Test Plan

  • Unit tests pass
  • Integration tests pass if applicable
  • Configured completion command passes
  • No coverage regression

Focused ownership, CodeQL, Ground Control configuration, and TechVault tests passed. The canonical completion command, policy command, pack validation, and pack release gates passed. Codex and test-quality pre-push reviews were clean.

Ground Control Checks

  • Configured repository policy command passes
  • Pre-push code review and test-quality review completed; all findings fixed or dispositioned

Traceability

Checklist

  • Code follows the project's coding standards
  • Changelog: owned by Release Please (generated from the Conventional Commit PR title; no per-PR fragment)
  • Architectural docs updated if stack, package structure, or key behaviors changed

Documentation

Updated: see diff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant