feat(phi-bias): complete PHI_BIAS implementation for GoldenFloat family

.claude/mcp/tri-ssot/manifest.json

@@ -0,0 +1,84 @@
+{
+  "name": "tri-ssot",
+  "description": "SSOT Integration for t27: GitHub Issues + PRs + Documentation → NotebookLM",
+  "version": "1.0.0",
+  "executable": {
+    "command": "python3",
+    "args": ["-m", "contrib.backend.github.mcp_server"]
+  },
+  "tools": [
+    {
+      "name": "tri_issue",
+      "description": "GitHub Issue management: create, update, list, close",
+      "inputSchema": {
+        "type": "object",
+        "properties": {
+          "action": {
+            "type": "string",
+            "enum": ["create", "update", "list", "close", "get"]
+          },
+          "title": {"type": "string"},
+          "body": {"type": "string"},
+          "labels": {"type": "string"},
+          "issue_id": {"type": "string"},
+          "state": {"type": "string", "enum": ["open", "in_progress", "closed"]}
+        }
+      }
+    },
+    {
+      "name": "tri_pr",
+      "description": "GitHub PR management: create, merge, close, get status",
+      "inputSchema": {
+        "type": "object",
+        "properties": {
+          "action": {
+            "type": "string",
+            "enum": ["create", "merge", "close", "get"]
+          },
+          "title": {"type": "string"},
+          "body": {"type": "string"},
+          "pr_id": {"type": "string"},
+          "issue_id": {"type": "string"}
+        }
+      }
+    },
+    {
+      "name": "tri_docs",
+      "description": "Documentation management: upload to NotebookLM, sync, query",
+      "inputSchema": {
+        "type": "object",
+        "properties": {
+          "action": {
+            "type": "string",
+            "enum": ["upload", "sync", "query"]
+          },
+          "file_path": {"type": "string"},
+          "title": {"type": "string"}
+        }
+      }
+    },
+    {
+      "name": "tri_sync",
+      "description": "Unified sync: sync all entities (issues, prs, docs) with NotebookLM",
+      "inputSchema": {
+        "type": "object",
+        "properties": {
+          "scope": {
+            "type": "string",
+            "enum": ["all", "issues", "prs", "docs"]
+          }
+        }
+      }
+    },
+    {
+      "name": "tri_search",
+      "description": "Unified search across GitHub Issues, PRs, NotebookLM docs",
+      "inputSchema": {
+        "type": "object",
+        "properties": {
+          "query": {"type": "string"}
+        }
+      }
+    }
+  ]
+}

.claude/plans/replicated-finding-plum.md

@@ -0,0 +1,110 @@
+# Issue: Full meta_compile.t27 Implementation
+
+## Context
+
+The `specs/compiler/meta_compile.t27` specification was added with PRs #529 and #531, defining a multi-backend compilation system with 5 target backends (Zig, C, Verilog, Rust, TypeScript). However, the current implementations are just stub functions that count newlines - they don't actually generate working code for any backend.
+
+**Problem**: The spec exists but has no functional implementation. Bootstrap codegen doesn't integrate with `meta_compile.t27` at all.
+
+## Current State
+
+**In `specs/compiler/meta_compile.t27`:**
+- ✅ `CompileResult` struct with all 5 backend fields
+- ✅ Stub implementations: `emit_zig()`, `emit_c()`, `emit_verilog()`, `emit_rust()`, `emit_typescript()`
+- ✅ Helper functions: `is_full_success()`, `total_lines()`, `any_backend_ok()`
+- ✅ 36 tests and invariants
+
+**In `gen/compiler/` (generated output):**
+- ✅ `meta_compile.zig` - Zig stub (line-counting only)
+- ✅ `meta_compile.c` - C stub (line-counting only)
+- ✅ `meta_compile.v` - Verilog stub (line-counting only)
+
+**In `bootstrap/`:**
+- ❌ No integration with `meta_compile.t27` spec
+- ❌ Existing `emit_verilog()` in `compiler.rs` is for testbench emission, unrelated to spec
+- ❌ No TypeScript or Rust code generation for `meta_compile` spec
+
+## Implementation Plan
+
+### Phase 1: Design Real Codegen Architecture
+1. Review existing parser and AST structures in `bootstrap/src/compiler.rs`
+2. Define codegen patterns for each backend target
+3. Design integration point between parser output and multi-backend codegen
+
+### Phase 2: Implement Target-Specific Codegen
+
+#### 2.1 Zig Backend
+- Implement actual Zig code emission from T27 AST
+- Generate syntactically valid Zig code for:
+  - Module declarations
+  - Function declarations with T27 types (φ, u32, i32, etc.)
+  - Expression statements (literals, calls, arithmetic, logic)
+  - Control flow (if, while, for)
+  - φ arithmetic operations
+
+#### 2.2 C Backend
+- Implement C code emission from T27 AST
+- Map T27 types to C types (φ → `uint16_t`, i32 → `int32_t`, etc.)
+- Generate valid C code for all AST node types
+
+#### 2.3 Verilog Backend
+- Implement Verilog code emission for hardware target
+- Map T27 constructs to Verilog (modules, wires, regs, always blocks)
+- Generate testbench-compatible output
+
+#### 2.4 Rust Backend
+- Implement Rust code emission from T27 AST
+- Map T27 types to Rust types
+- Generate valid Rust with proper type annotations
+
+#### 2.5 TypeScript Backend
+- Implement TypeScript code emission for web/browser target
+- Map T27 types to TS types (φ → `number`, i32 → `number`, etc.)
+- Generate valid TypeScript declarations and functions
+
+### Phase 3: Bootstrap Integration
+1. Add `meta_compile` module integration to `bootstrap/src/compiler.rs`
+2. Wire parser output to `meta_compile` backends
+3. Add CLI flags for target backend selection
+4. Add `--all-backends` flag to compile to all targets
+
+### Phase 4: Testing
+1. Run existing `tri test` suite for `meta_compile.t27`
+2. Add integration tests for generated code compilation
+3. Verify generated Zig/C/Verilog/Rust/TypeScript actually compiles
+
+### Phase 5: Documentation
+1. Update `docs/NOW.md` with issue closure
+2. Document multi-backend usage in README
+3. Add examples showing cross-compilation to different targets
+
+## Critical Files
+
+**Spec:**
+- `/Users/playra/t27/specs/compiler/meta_compile.t27`
+
+**Bootstrap (to modify):**
+- `/Users/playra/t27/bootstrap/src/compiler.rs` - Add meta_compile integration
+- `/Users/playra/t27/bootstrap/src/main.rs` - Add CLI flags for backend selection
+
+**Generated (verify after tri gen):**
+- `/Users/playra/t27/gen/compiler/meta_compile.zig`
+- `/Users/playra/t27/gen/compiler/meta_compile.c`
+- `/Users/playra/t27/gen/compiler/meta_compile.v`
+- `/Users/playra/t27/gen/compiler/meta_compile.rs` (to be created)
+- `/Users/playra/t27/gen/compiler/meta_compile.ts` (to be created)
+
+## Verification
+
+1. Run `./scripts/tri gen compiler/meta_compile.t27` to generate code
+2. Run `./scripts/tri test compiler/meta_compile.t27` to verify conformance
+3. Manually test: compile a simple T27 module to each backend
+4. Verify generated Zig/C/Verilog/Rust/TypeScript files compile with their respective compilers
+5. Close issue with `Closes #<issue>` in commit message
+
+## Notes
+
+- This is a multi-hour task involving both spec updates and bootstrap changes
+- The existing stub implementations in `meta_compile.t27` should be replaced with real codegen logic
+- Bootstrap needs new CLI options for backend targeting
+- Consider making backends pluggable for future targets (e.g., WASM, Python)

.claude/skills/tri/skill.md

@@ -92,6 +92,77 @@ tri wrapup --summary "completed <task>" \
 - "known issues with <spec>" — Find blockers
 - "architecture of <component>" — Get design context
 
+<<<<<<< Updated upstream
+## MANDATORY WORKFLOW: Start Task Before Pushing
+
+**L7 UNITY Requirement:** Every push to the repository must have an active NotebookLM notebook.
+
+<<<<<<< Updated upstream
+```bash
+=======
+```
+>>>>>>> Stashed changes
+# Step 1: ALWAYS start a task before beginning work
+t27c bridge task start --title "Your task description"
+
+# This creates:
+# - .trinity/current_task/.notebook_id  (tracked in git)
+# - .trinity/current_task/notebook_meta.json
+# - A new NotebookLM notebook linked to your session
+
+# Step 2: Do your work (PHI LOOP, edits, commits, etc.)
+
+# Step 3: Push (gate will check for notebook)
+git push  # Succeeds only if .notebook_id exists and is valid
+```
+
+**Alternative: Attach existing notebook**
+
+<<<<<<< Updated upstream
+```bash
+=======
+```
+>>>>>>> Stashed changes
+t27c bridge task attach --notebook_id "abc123def456"
+```
+
+**Check current task status**
+
+<<<<<<< Updated upstream
+```bash
+=======
+```
+>>>>>>> Stashed changes
+t27c bridge task status
+```
+
+**Verify notebook is valid**
+
+<<<<<<< Updated upstream
+```bash
+=======
+```
+>>>>>>> Stashed changes
+t27c bridge task verify
+```
+
+**Emergency bypass (NOT recommended)**
+
+<<<<<<< Updated upstream
+```bash
+=======
+```
+>>>>>>> Stashed changes
+SKIP_NOTEBOOK_GATE=1 git push
+# Bypass is logged to .trinity/gate_bypasses.log
+```
+
+**Branch Protection Rule (to be configured):**
+- Required status check: "NotebookLM Gate / 🔒 NotebookLM notebook required"
+- Require branches to be up to date before merging: YES
+- Include administrators: YES
+
+<<<<<<< Updated upstream
 ## /tri wrapup
 
 Automatic session wrap-up with NotebookLM upload. This is the canonical way to end a session and preserve context for future agents.
@@ -222,6 +293,124 @@ t27 #343 — Restore phi-loop-ci.yml
 t27 #350 — NotebookLM Integration
   └─ Source 1: "Session 2026-04-08 17:00 — Spec creation"
   └─ Source 2: "Session 2026-04-08 18:00 — Backend impl"
+=======
+## tri task — Task Notebook Management (via t27c bridge)
+
+Quick NotebookLM commands for notebook management:
+
+```bash
+# Create a new notebook
+t27c bridge nb create --title "Sprint 9: NeurIPS"
+
+# List all notebooks
+t27c bridge nb list
+
+# Add a file as source to current notebook
+t27c bridge nb add --file path/to/file.md
+
+# Query current notebook with prompt
+t27c bridge nb query --prompt "что сделано вчера?"
+
+# Upload activity.md to notebook
+t27c bridge nb upload-log
+
+# Link current notebook to GitHub issue
+t27c bridge nb link --issue 370
+```
+
+**Configuration:**
+- Backend: `contrib/backend/notebooklm/` (Playwright-based)
+- Storage: `~/.notebooklm/storage_state.json`
+- Auth: Cookie-based via `notebooklm login` CLI
+- Python: `python3.10` (where `notebooklm-py` is installed)
+
+**MCP Integration:**
+- Server: `notebooklm-mcp` (installed via `npm install -g notebooklm-mcp`)
+- Config: `.claude/mcp.json`
+- Claude Code can directly create notebooks, upload sources, and query with Gemini citations
+
+**Bulk Creation:**
+```bash
+# Create notebooks for all open issues
+scripts/bulk-create-notebooks.sh
+>>>>>>> Stashed changes
+=======
+## Task Notebook Management (L7 UNITY Enforcement)
+
+**MANDATORY:** Every task must have a NotebookLM notebook assigned before pushing code.
+
+### Starting a New Task
+
+```bash
+# Initialize task with a new notebook
+t27c task start --title "Implement feature X" --sources "specs/*.t27,README.md"
+
+# This creates:
+# - A NotebookLM notebook with the given title
+# - .trinity/current_task/.notebook_id (tracked in git)
+# - .trinity/current_task/notebook_meta.json
+
+# Then proceed with PHI LOOP work
+tri notebook query "status of feature X"  # Check existing work
+tri spec edit <module>
+# ... rest of PHI LOOP ...
+```
+
+### Attaching Existing Notebook
+
+```bash
+# Use an existing notebook if one already exists for this work
+t27c task attach --notebook-id "existing-notebook-id"
+```
+
+### Checking Task Status
+
+```bash
+# Show current task notebook status
+t27c task status
+
+# Output shows:
+# - Notebook ID and URL
+# - Task title
+# - Branch
+# - Sources count
+```
+
+### Verifying Notebook Gate
+
+```bash
+# Verify notebook gate requirement is satisfied (called by pre-push hook)
+t27c task verify
+```
+
+### Mandatory Workflow Order
+
+1. **Before starting work:** Query NotebookLM to avoid duplication
+   ```bash
+   tri notebook query "status of <task>"
+   ```
+
+2. **Initialize task:** Create notebook if starting new work
+   ```bash
+   t27c task start --title "task description"
+   ```
+
+3. **Execute PHI LOOP:** tri spec edit, tri gen, tri test, etc.
+
+4. **After completing work:** Upload wrap-up
+   ```bash
+   tri notebook wrapup --summary "completed <task>" --decisions "..." --files "..." --next "..."
+   ```
+
+5. **Git push:** Pre-push hook verifies .notebook_id exists
+   ```bash
+   git push  # Blocked if no valid notebook
+   ```
+
+**Emergency Bypass** (logged to `.trinity/gate_bypasses.log`):
+```bash
+SKIP_NOTEBOOK_GATE=1 git push
+>>>>>>> Stashed changes
 ```
 
 ## Standard /tri Status Output