docs: align AeroSim six-channel operations

docs/projects/aerosim.md

@@ -54,23 +54,27 @@ A playable MVP covering a light trainer, commercial airliner, and fighter-style
 
 ## Discord
 
-Exactly four same-project channels exist under category `corp-v1` (`1537070242335821924`):
+Exactly six same-project channels exist under category `corp-v1` (`1537070242335821924`):
 
 - `corp-v1-aerosim-general` — `1537227679374508132`
+- `corp-v1-aerosim-scope` — `1537544173366943886`
 - `corp-v1-aerosim-architecture` — `1537227680590733383`
+- `corp-v1-aerosim-kanban` — `1537548579856580739`
 - `corp-v1-aerosim-delivery` — `1537227683191197807`
 - `corp-v1-aerosim-releases` — `1537388451501056081`
 
-Hermes bot `1526860732917088266` successfully read, posted, and pinned project guidance. The general introduction is pinned as message `1537227685657444484`. The releases purpose message is `1537388452658815077`. RootAtSkic was resolved as Discord member `1518725627845283888`.
+Hermes bot `1526860732917088266` successfully read and posted project guidance. The general introduction is pinned as message `1537227685657444484`; Scope purpose guidance is message `1537544176621715506`; Kanban purpose guidance is message `1537548582003933326`; Releases purpose guidance is message `1537388452658815077`. RootAtSkic was resolved as Discord member `1518725627845283888`.
 
-Four staggered recurring synchronization jobs are active. Every job runs each hour, monitors only the other three AeroSim channels, loads its mapped adopted channel skill, proactively performs useful safe work within that channel's purpose, and records durable work in project documentation:
+Six staggered recurring synchronization jobs are active. Every job runs each hour, monitors only the other five AeroSim channels, loads its mapped adopted channel skill, proactively performs useful safe work within that channel's purpose, and records durable work in project documentation:
 
 - General: `6fc9c6a1328e`, `0 * * * *`, skill `corp-v1-channel-general--aerosim`, target `1537227679374508132`
+- Scope: `dd548489178e`, `10 * * * *`, skill `corp-v1-channel-scope--aerosim`, target `1537544173366943886`
 - Architecture: `c236b1e9642e`, `15 * * * *`, skill `corp-v1-channel-architecture--aerosim`, target `1537227680590733383`
+- Kanban: `73378876d226`, `20 * * * *`, skill `corp-v1-channel-kanban--aerosim`, target `1537548579856580739`
 - Delivery: `fdb061087f2f`, `30 * * * *`, skill `corp-v1-channel-delivery--aerosim`, target `1537227683191197807`
 - Releases: `9deaa76e0077`, `45 * * * *`, skill `corp-v1-channel-releases--aerosim`, target `1537388451501056081`
 
-All four jobs are enabled and restricted from cross-project inspection and approval-required, destructive, secret-bearing, or high-impact autonomous actions.
+All six jobs are enabled, explicitly constrained to the complete six-channel AeroSim boundary, and restricted from cross-project inspection and approval-required, destructive, secret-bearing, or high-impact autonomous actions.
 
 ## Adopted project skills
 
@@ -84,7 +88,9 @@ All use default branch `test` and are primary for AeroSim work:
 - `documentation-docusaurus--aerosim`
 - `template-engine-copier--aerosim`
 - `corp-v1-channel-general--aerosim`
+- `corp-v1-channel-scope--aerosim`
 - `corp-v1-channel-architecture--aerosim`
+- `corp-v1-channel-kanban--aerosim`
 - `corp-v1-channel-delivery--aerosim`
 - `corp-v1-channel-releases--aerosim`
 
@@ -98,7 +104,7 @@ Each repository records the central source branch and commit in `ADOPTION.md`. A
 - Application tests: four passed across web, API, and shared flight core.
 - Application and documentation production builds: passed.
 - Project-team access to both project repositories: verified.
-- Skills-team organization contains all eleven adopted skill repositories on default branch `test`: verified.
+- Skills-team organization contains all thirteen adopted skill repositories on default branch `test`: verified.
 - Harbor organization variable names and secret name `HL_V1_HARBOR_ROBOT_GITEA_ACTIONS_V1_SECRET`: verified without reading secret values.
 - Product lifecycle, solution traceability, and release-readiness registries now exist in project documentation. No Epic or Feature was assigned human approval retrospectively.
 - Both application and documentation `test` branches currently have no branch-protection rule.