@symbiote-native/angular 0.3.1 → 0.3.3

package/src/modules/app-registry/app-registry.test.ts

@@ -1,4 +1,4 @@
-// Co-located Angular-driven test (ADR 0025), Angular twin of adapters/react/src/modules/
+// Co-located Angular-driven test, Angular twin of adapters/react/src/modules/
 // app-registry/app-registry.test.tsx. Proves the AppRegistry entry point:
 // `registerComponent(appKey, () => App)` stores a runnable that calls `mount` (driving
 // @symbiote-native/engine) AND bridges it to the host registrar (RN's own AppRegistry, injected via
@@ -19,8 +19,8 @@ const ROOT_TAG = 212;
 const WRAPPED_APP_KEY = 'canary-wrapped';
 const WRAPPED_ROOT_TAG = 213;
 
-// Angular's mount() batches change detection on a microtask (the `angular-adapter` skill's
-// whenCommitted-class gotcha), so assertions on the committed tree need one tick, same as Vue.
+// Angular's mount() batches change detection on a microtask, so a committed native tag isn't
+// available synchronously — assertions on the committed tree need one tick, same as Vue.
 const tick = (): Promise<void> => new Promise(resolve => setTimeout(resolve, 0));
 
 class TestText {}

package/src/primitives/shared.ts

@@ -36,8 +36,7 @@ import {
  *
  * Skipping this call for a new `ANCHOR_HOST_COMPONENTS` entry compiles clean under `tsc` AND a
  * real `ngc` AOT build — no type error, no template error — it just silently drops `class="..."`
- * forever; only a device/simulator render (or a committed-node style assertion) catches it. See
- * the `angular-adapter` skill §21 for the device-confirmed incident and the full checklist.
+ * forever; only a device/simulator render (or a committed-node style assertion) catches it.
  */
 export function anchorHostStyle(elementRef: ElementRef<unknown>): unknown {
   const node = elementRef.nativeElement;
@@ -178,7 +177,7 @@ export class SymbioteHostPropsDirective {
   // so the next root tick repaints the mutation. It targets the directive's injecting view
   // (`_cdRefInjectingView`, i.e. the host component), unlike `detectChanges()` which acts on a
   // resolved `_lView` that is NOT the host component here. The Angular twin of what React/Vue get
-  // for free (setState / proxy reactivity). See the `angular-adapter` skill §17.
+  // for free (setState / proxy reactivity).
   private wrapCallback(key: string, value: unknown): unknown {
     if (!ON_PREFIX.test(key) || typeof value !== 'function') return value;
     const handler = value as (...args: unknown[]) => unknown;

package/src/render.test.ts

@@ -139,9 +139,9 @@ describe('Angular mount', () => {
 
     expect(fabric.serialize(fabric.appRoot().children)).toContain('RCTRawText "tapped 1×"');
     // UnrelatedSiblingChild has no dirty descendant of its own, so it must not be re-checked
-    // just because CounterChild (a completely separate branch) got pressed. See the
-    // `angular-adapter` skill §20 for the full investigation, including what this test does
-    // NOT prove (the root's own template still re-runs on every press — see render.ts).
+    // just because CounterChild (a completely separate branch) got pressed. This does NOT prove
+    // the root's own template stays untouched — the root's template still re-runs on every
+    // press (see render.ts).
     expect(unrelatedRenderCount).toBe(afterFirstPaint);
   });
 });

package/src/render.ts

@@ -3,7 +3,7 @@
 // (no DOM) — createEnvironmentInjector + createComponent over @angular/core only, with our
 // SymbioteRendererFactory provided so Angular drives the engine, which commits into
 // nativeFabricUIManager; RN's own renderer never in the path. Angular twin of
-// adapters/vue/src/render.ts. See the `angular-adapter` skill (§2 bootstrap).
+// adapters/vue/src/render.ts.
 
 import {
   createElement as createEngineElement,
@@ -143,8 +143,7 @@ export function mount(
       // behavior, true in every Angular app, not something this swap changes. What DOES
       // still protect a sibling branch from an unrelated press is a genuine child
       // `@Component` boundary — SignalView-compiled children are skip-eligible regardless of
-      // this scheduler (see the `angular-adapter` skill §20 for the full investigation,
-      // including the test that disproved the stronger claim before it shipped).
+      // this scheduler.
       ...provideZonelessChangeDetectionInternal(),
       ColorSchemeService,
       WindowDimensionsService,

package/src/renderer.test.ts

@@ -1,4 +1,4 @@
-// Co-located headless test for the Angular renderer seam (ADR 0025). Drives SymbioteRenderer
+// Co-located headless test for the Angular renderer seam. Drives SymbioteRenderer
 // directly — no Angular runtime, no compiler — against the shared fake Fabric slot, proving
 // each Renderer2 method maps onto the engine mutation API and commits a correct Fabric tree.
 // The bootstrap (mount → createComponent) is validated separately on a real host / the AOT

package/src/renderer.ts

@@ -2,8 +2,8 @@
 // DOM directly — every paint goes through Renderer2 (created per-component by
 // RendererFactory2). We provide OUR factory, so each Renderer2 method maps onto the
 // engine's tiny mutation API; the engine owns all Fabric clone-on-write, shared with
-// every other adapter. This is the Angular twin of adapters/vue/src/renderer.ts and the
-// proof the core is framework-agnostic (R4). See the `angular-adapter` skill.
+// every other adapter. This is the Angular twin of adapters/vue/src/renderer.ts — proof
+// that the same engine mutation API drives both frameworks.
 
 import {
   appendChild,
@@ -150,8 +150,7 @@ function assertTextPlacement(child: ISymbioteNode, parent: IHostElement): void {
 
 // One renderer per mounted surface. Every mutation asks the surface to (microtask-
 // coalesced) recommit — the same seam Vue uses; a burst of Angular change-detection
-// mutations collapses into one completeRoot. wolf-tui likewise reuses a single renderer
-// instance for all components.
+// mutations collapses into one completeRoot.
 export class SymbioteRenderer implements Renderer2 {
   readonly data: Record<string, unknown> = {};
   // Angular calls destroyNode per-node only when this is non-null; teardown happens in
@@ -313,8 +312,7 @@ export class SymbioteRenderer implements Renderer2 {
   }
 
   // Ivy compiles every class= / [class.foo] / [ngClass] form down to per-token addClass/
-  // removeClass calls (never a single setAttribute('class', ...) — confirmed against the
-  // vendored Ivy sources, see the symbiote-sfc-style-compiler skill), so a per-node token set
+  // removeClass calls (never a single setAttribute('class', ...) call), so a per-node token set
   // is accumulated here and re-joined into one string on every change, then handed to
   // routeProp('class', ...) exactly like Vue's template `class="..."` and React's JSX
   // `className="..."` — all three resolve through the SAME centralized class+style merge in