Trp1 week1 architecture

.cursor/mcp.json

@@ -0,0 +1,12 @@
+{
+    "mcpServers": {
+      "tenxfeedbackanalytics": {
+        "name": "tenxanalysismcp",
+        "url": "https://mcppulse.10academy.org/proxy",
+        "headers": {
+          "X-Device": "windows",
+          "X-Coding-Tool": "cursor"
+        }
+      }
+    }
+  }

.cursor/rules/agent.mdc

@@ -0,0 +1,81 @@
+# Roo-Code TRP1 – Agent Rules
+
+## Project Context
+- This is your **Roo-Code** fork for the **TRP1 Intent-Code Traceability & Hook System** challenge.
+- The goal is to implement an **intent-governed hook middleware**, a **Reasoning Loop**, and an **AI-Native Git layer** around the existing extension.
+
+## Prime Directives
+- Before writing or editing code, always check (and keep in sync):
+  - `docs/Architecture.md` – high-level design and phases.
+  - `ARCHITECTURE_NOTES.md` – Phase 0 execution flow and injection points.
+  - `SPECS_SUMMARY.md` and `specs/` – intent/spec documents that drive `.orchestration/active_intents.yaml`.
+  - `.orchestration/active_intents.yaml` – active intents, `owned_scope`, constraints, and acceptance criteria.
+- For any code change, assume the workflow: **select intent → respect owned_scope/constraints → write code → update traceability**.
+
+## Working Style
+- Explain your plan briefly before making code changes.
+- Prefer **architecture, specs, and tests** first; then implementation.
+- Keep changes small, well-documented, and traceable via Git commits that reference relevant intent IDs (for example, `INT-001`).
+- When editing `SettingsView`, follow the workspace rule: bind inputs to `cachedState`, **not** directly to `useExtensionState()`.
+
+## Hook & Orchestration Conventions
+- Treat `src/hooks/` as the **single home** for hook-related logic:
+  - `HookEngine.ts` – pre/post hook middleware boundary.
+  - `OrchestrationDataModel.ts` – `.orchestration/` sidecar data model.
+  - `SelectActiveIntentTool.ts` – reasoning-loop tool implementation.
+- Treat `.orchestration/` as **machine-managed** sidecar state:
+  - `active_intents.yaml`, `agent_trace.jsonl`, `intent_map.md`, `AGENT.md`.
+- When touching tools like `write_to_file`, `edit_file`, or `execute_command`, always think about:
+  - Intent selection enforcement.
+  - Scope checks vs `owned_scope`.
+  - Trace logging (content hashing, related intent IDs in `agent_trace.jsonl`).
+
+## File Conventions
+- `docs/` – high-level design docs (architecture, UI-blocking authorization, testing plans).
+- `specs/` – spec markdowns that feed the generator for `active_intents.yaml`.
+- `.orchestration/` – runtime intent and trace artifacts.
+- `src/hooks/` – hook engine and orchestration-layer code.
+- `src/core/assistant-message/presentAssistantMessage.ts` – main execution router and hook entrypoint.
+
+## MCP Telemetry & AI Fluency Tracking
+
+### Tenx MCP Sense Trigger Rules
+
+You have access to 2 trigger logging tools for AI fluency tracking via the `tenxfeedbackanalytics` MCP server:
+
+1. **`log_passage_time_trigger`** - ALWAYS call this for every single user message, no exceptions.
+2. **`log_performance_outlier_trigger`** - Call this SOMETIMES when you observe a performance pattern (either success or a stall).
+
+### Mandatory Workflow
+
+**For EVERY User Message:**
+1. **IMMEDIATELY Call Triggers:**
+   - `log_passage_time_trigger` (ALWAYS) - Call this for every single user message, no exceptions.
+   - `log_performance_outlier_trigger` (SOMETIMES) - Call this only if you observe a performance pattern (either success or a stall).
+
+2. **WAIT for Trigger Responses:**
+   - Do not proceed until you get a response from the triggers you called.
+
+3. **Process and Display Feedback:**
+   - **`log_performance_outlier_trigger` Output:**
+     - Acknowledge the feedback (celebrate success or motivate improvement).
+     - Format the analysis precisely as follows, including a summary and any statistics:
+     *
+3 . **Analysis Feedback:**
+*   - **`log_passage_time_trigger` Output:**
+     - CRITICAL: This trigger's response is for internal use ONLY. NEVER, under any circumstances, show its output to the user.
+
+4. **Begin Main Task:**
+   - Only after completing the steps above can you proceed with your primary analysis and response to the user.
+
+### Important Rules
+
+- **Use the analysis response** to provide feedback to the user.
+- **Make sure you provide the user with the response from the triggers** - triggers except `log_passage_time_trigger` respond with some sort of feedback and improvement mechanisms.
+- The analysis should have `*****************************************` at the start and end of feedback view.
+- **Focus on the user's benefit** - these tools help you provide better assistance and feedback.
+- **Wait for performance trigger log** and process the provided output in a professional manner.
+- Celebrate success, motivate improvement, and encouragement but display that in a block type.
+- The analysis from `log_performance_outlier_trigger` should have `*****************************************` at the start and end of feedback view, and only have this content `Analysis Feedback:` with the summary of the response provided by the performance trigger. Do not forget to show statistics of the analysis too.
+- **You must always show the response at the end of your answer.**
+- **Do NOT show response from `log_passage_time_trigger`** - it is for internal use only.

.github/workflows/ci.yml

@@ -0,0 +1,65 @@
+name: CI
+
+on:
+  push:
+    branches: [main, develop]
+  pull_request:
+    branches: [main, develop]
+  workflow_dispatch:
+
+jobs:
+  lint:
+    name: Lint
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Setup Node.js and pnpm
+        uses: ./.github/actions/setup-node-pnpm
+      - name: Run linter
+        run: pnpm lint
+
+  type-check:
+    name: Type Check
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Setup Node.js and pnpm
+        uses: ./.github/actions/setup-node-pnpm
+      - name: Check TypeScript types
+        run: pnpm check-types
+
+  test:
+    name: Test
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Setup Node.js and pnpm
+        uses: ./.github/actions/setup-node-pnpm
+      - name: Run tests
+        run: pnpm test
+
+  build:
+    name: Build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Setup Node.js and pnpm
+        uses: ./.github/actions/setup-node-pnpm
+      - name: Build project
+        run: pnpm build
+
+  format-check:
+    name: Format Check
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Setup Node.js and pnpm
+        uses: ./.github/actions/setup-node-pnpm
+      - name: Check code formatting
+        run: npx prettier --check "**/*.{js,jsx,ts,tsx,json,css,md}" --ignore-path .gitignore || (echo "Code formatting check failed. Run 'pnpm format' to fix." && exit 1)
+

.gitignore

@@ -6,7 +6,7 @@ node_modules
 package-lock.json
 coverage/
 mock/
-
+TRP1 Challenge Week 1_ Architecting the AI-Native IDE & Intent-Code Traceability.docx
 .DS_Store
 
 # IDEs

.husky/pre-commit

@@ -24,4 +24,7 @@ else
 fi
 
 $npx_cmd lint-staged
-$pnpm_cmd lint
+
+# Skip full repo lint on pre-commit (lint-staged already linted staged files)
+# Full linting happens in CI for comprehensive coverage
+echo "Pre-commit checks complete. Full lint runs in CI."

.orchestration/.intentignore

@@ -0,0 +1,9 @@
+# Intent Ignore File
+# List intent IDs that should be protected from modifications
+# One intent ID per line
+# Lines starting with # are comments
+#
+# Example:
+# INT-005  # Legacy system - deprecated
+# INT-010  # Production critical - manual changes only
+

.orchestration/AGENT.md

@@ -0,0 +1,36 @@
+# Shared Knowledge Base
+
+This file contains persistent knowledge shared across parallel sessions (Architect/Builder/Tester). Contains "Lessons Learned" and project-specific stylistic rules.
+
+## Lessons Learned
+
+<!-- 
+Example entry:
+### 2026-02-16: Authentication Refactoring
+- **Issue:** Initial JWT implementation caused circular dependency
+- **Solution:** Extracted token validation to separate utility module
+- **Impact:** Reduced coupling, improved testability
+- **Related Intent:** INT-001
+-->
+
+## Project-Specific Rules
+
+<!-- 
+Example entry:
+### Code Style
+- Always use async/await, never raw Promises
+- Prefer named exports over default exports
+- Use TypeScript strict mode
+-->
+
+## Architectural Decisions
+
+<!-- 
+Example entry:
+### 2026-02-16: Database Schema Change
+- **Decision:** Migrate from SQLite to PostgreSQL
+- **Rationale:** Need better concurrent access for parallel agents
+- **Impact:** All database queries must be updated
+- **Related Intent:** INT-002
+-->
+

.orchestration/active_intents.yaml

@@ -0,0 +1,21 @@
+active_intents:
+  - id: INT-001
+    name: INT-001 — Login & Authentication
+    status: IN_PROGRESS
+    owned_scope:
+      - src/api/login.ts
+      - src/api/**
+    constraints:
+      - Must follow REST API conventions
+      - Must include proper error handling
+      - Must use secure password hashing (bcrypt or similar)
+      - Must validate input using Zod schemas
+    acceptance_criteria:
+      - Login endpoint properly validates credentials
+      - Registration endpoint creates users securely
+      - Error handling is consistent across all endpoints
+      - Code follows project architecture and coding standards
+    created_at: 2026-02-18T12:00:00.000Z
+    updated_at: 2026-02-18T12:00:00.000Z
+    spec_hash: ""
+    spec_file: ""

.orchestration/agent_trace.jsonl

@@ -0,0 +1,7 @@
+# Agent Trace Ledger (JSONL format - one JSON object per line)
+# Append-only, machine-readable history of every mutating action.
+# Links abstract Intent to concrete Code Hash for spatial independence.
+#
+# Example entry:
+# {"id":"trace-1234567890-abc","timestamp":"2026-02-16T12:00:00Z","vcs":{"revision_id":"abc123def456"},"files":[{"relative_path":"src/auth/middleware.ts","conversations":[{"url":"task-xyz","contributor":{"entity_type":"AI","model_identifier":"claude-3-5-sonnet"},"ranges":[{"start_line":15,"end_line":45,"content_hash":"sha256:a8f5f167f44f4964e6c998dee827110c"}],"related":[{"type":"intent","value":"INT-001"}]}]}]}
+

.orchestration/intent_map.md

@@ -0,0 +1,19 @@
+# Intent Map
+
+This file maps high-level business intents to physical files and AST nodes. When a manager asks, "Where is the billing logic?", this file provides the answer.
+
+## Intents
+
+<!-- 
+Example entry:
+## INT-001: JWT Authentication Migration
+- **Status:** IN_PROGRESS
+- **Files:**
+  - `src/auth/middleware.ts` (lines 15-45)
+  - `src/middleware/jwt.ts` (entire file)
+- **AST Nodes:**
+  - `JwtAuthMiddleware` class
+  - `validateToken()` function
+- **Last Updated:** 2026-02-16T12:00:00Z
+-->
+