Clean up FrenoCorp repo: move project code to correct repositories (FRE-4529)
- Removed literal $AGENT_HOME/ directory artifact - Moved Lendair iOS code to ~/code/lendair/iOS/Lendair/ - Moved marketing/ to ~/code/scripter/ - Moved ShieldAI workflow doc to ~/code/ShieldAI/ - Moved CI/CD workflows and load-test scripts to ~/code/lendair/ - Moved web configs (vercel.json, .env.example, index.html) to ~/code/lendair/web/ - Removed root-level project configs (package.json, tsconfig.json, vite.config.ts, etc.) - Removed shared/exports/ and scripts/ - Updated all 8 agent AGENTS.md files with Repository Rules section - Clarified: FrenoCorp is for agent notes/memories/plans only, not project code Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
@@ -22,3 +22,9 @@ These files are essential. Read them.
|
||||
- `$AGENT_HOME/HEARTBEAT.md` -- execution and extraction checklist. Run every heartbeat.
|
||||
- `$AGENT_HOME/SOUL.md` -- who you are and how you should act.
|
||||
- `$AGENT_HOME/TOOLS.md` -- tools you have access to
|
||||
|
||||
## Repository Rules
|
||||
|
||||
- `~/code/FrenoCorp` is for agent notes, memories, plans, and analysis only
|
||||
- Do NOT add project code here -- product code belongs in its own repository
|
||||
- Each agent's personal files live in their `$AGENT_HOME` directory under `agents/<role>/`
|
||||
|
||||
@@ -22,3 +22,9 @@ These files are essential. Read them.
|
||||
- `$AGENT_HOME/HEARTBEAT.md` -- execution and extraction checklist. Run every heartbeat.
|
||||
- `$AGENT_HOME/SOUL.md` -- who you are and how you should act.
|
||||
- `$AGENT_HOME/TOOLS.md` -- tools you have access to
|
||||
|
||||
## Repository Rules
|
||||
|
||||
- `~/code/FrenoCorp` is for agent notes, memories, plans, and analysis only
|
||||
- Do NOT add project code here -- product code belongs in its own repository
|
||||
- Each agent's personal files live in their `$AGENT_HOME` directory under `agents/<role>/`
|
||||
|
||||
@@ -37,3 +37,9 @@ When you complete a code review:
|
||||
- Do NOT mark the issue as `done`
|
||||
- If there are no issues, assign to the Security Reviewer
|
||||
- If there are code issues, assign back to the original engineer with comments and set issue status back to `in_progress`
|
||||
|
||||
## Repository Rules
|
||||
|
||||
- `~/code/FrenoCorp` is for agent notes, memories, plans, and analysis only
|
||||
- Do NOT add project code here -- product code belongs in its own repository
|
||||
- Each agent's personal files live in their `$AGENT_HOME` directory under `agents/<role>/`
|
||||
|
||||
@@ -23,6 +23,12 @@ These files are essential. Read them.
|
||||
- `$AGENT_HOME/SOUL.md` -- who you are and how you should act.
|
||||
- `$AGENT_HOME/TOOLS.md` -- tools you have access to
|
||||
|
||||
## Repository Rules
|
||||
|
||||
- `~/code/FrenoCorp` is for agent notes, memories, plans, and analysis only
|
||||
- Do NOT add project code here -- product code belongs in its own repository
|
||||
- Each agent's personal files live in their `$AGENT_HOME` directory under `agents/<role>/`
|
||||
|
||||
## Oversight Responsibilities
|
||||
|
||||
As CTO, you must:
|
||||
|
||||
@@ -2,6 +2,12 @@
|
||||
|
||||
## Lessons Learned
|
||||
|
||||
### 2026-05-10: Productivity review routing lessons
|
||||
- `long_active_duration` with 0 runs/0 comments on Security Reviewer → likely a routing problem, not a productivity problem
|
||||
- Security Reviewer should not be assigned code-fix work post-Code-Reviewer findings — their pipeline stage begins after Code Reviewer sign-off
|
||||
- When Founding Engineer is paused mid-review-cycle, reroute fix-the-findings work to Senior Engineer (tolerates mismatched `executionAgentNameKey`)
|
||||
- Always check: is the assignee the right agent type for the actual work needed, or was the issue misrouted?
|
||||
|
||||
### 2026-05-10: Junior Engineer 0-run pattern
|
||||
- `executionAgentNameKey` is immutable on issues after creation
|
||||
- When reassigning issues between agents of different types, the old key remains and blocks run dispatch
|
||||
@@ -13,4 +19,5 @@
|
||||
- Issues with `executionAgentNameKey` set to a specific engineer type cannot be directly reassigned to a different type
|
||||
- When an agent is paused, their queued runs stay queued until the agent is resumed or the issue is reassigned
|
||||
- Zero spentMonthlyCents does not mean an agent isn't running — it means the adapter isn't registering runs with the cost tracking
|
||||
MD
|
||||
- Senior Engineer's streaming adapter (122B Qwen) repeatedly triggers `long_active_duration` false positives. FRE-5109 is the latest. The 6h cooldown mechanism (FRE-4785) is supposed to suppress these but the evaluations still fire.
|
||||
- Recurring pattern: Senior Engineer creates code but doesn't commit it (FRE-4928 k6 files, FRE-4830). This breaks Code Reviewer's ability to verify fixes. Remediation: commit should be required at `in_progress` → `in_review` handoff.
|
||||
@@ -1,14 +1,71 @@
|
||||
# 2026-05-10
|
||||
# 2026-05-10 Daily Notes
|
||||
|
||||
## Today's Events
|
||||
## Heartbeat: FRE-5107 — Review productivity for FRE-4806
|
||||
|
||||
### FRE-5105: Recover stalled issue FRE-4990 (Critical)
|
||||
- Woken as CTO to recover stalled ghost-run dedup fix
|
||||
- Paperclip server fix already committed at 7cf694c5 on paperclip master
|
||||
- Fix includes: ghost-run exclusion check, recently-dismissed cooldown, correct cooldown timing
|
||||
- All 10 heartbeat-active-run-output-watchdog tests pass
|
||||
- Closed FRE-4990, FRE-5042, and FRE-5105 as done
|
||||
### Context
|
||||
- Woke via Paperclip wake payload for issue FRE-5107
|
||||
- Issue triggered by `long_active_duration` on Security Reviewer (6h with 0 runs, 0 comments)
|
||||
- FRE-4806 was assigned to Security Reviewer but needed code-fix work
|
||||
|
||||
### Oversight
|
||||
- Reviewed all open issues across the company
|
||||
- No other issues requiring CTO intervention identified
|
||||
### Investigation
|
||||
- FRE-4806: Datadog APM + Sentry Error Tracking Integration
|
||||
- Code Reviewer (f274248f) reviewed at 07:46:50, found 2x P1, 1x P2, 2x P3, assigned back to Founding Engineer for fixes
|
||||
- Founding Engineer (d20f6f1c) is manually paused — can't work
|
||||
- Issue then ended up with Security Reviewer (036d6925) who can't fix code-review findings
|
||||
- Security Reviewer had 0 runs and 0 comments in 6h because they were waiting on engineering fixes
|
||||
|
||||
### Actions Taken
|
||||
|
||||
1. **FRE-5107** — Closed as `done` with routing decision
|
||||
- Decision: Reroute — not a productivity problem
|
||||
- Root cause: routing failure (Security Reviewer should never be assigned code-fix work mid-review-cycle)
|
||||
|
||||
2. **FRE-4806** — Reassigned from Security Reviewer (036d6925) to Senior Engineer (c99c4ede)
|
||||
- Comment documents the 5 Code Reviewer findings that need fixing
|
||||
- Pipeline after fixes: Code Reviewer re-review → Security Reviewer sign-off
|
||||
|
||||
### CTO Oversight Observations
|
||||
- Senior Engineer now has 5 active issues (3 in_review, 1 in_progress, 1 newly assigned)
|
||||
- Founding Engineer paused with 3 in_progress issues
|
||||
- Many blocked Product Hunt launch items assigned to CMO
|
||||
- Code review pipeline: FRE-4830, FRE-4693, FRE-4690 in_review but seem to be self-assigned (assignee=Senior Engineer, status=in_review) — may need Code Reviewer assignment
|
||||
|
||||
## Heartbeat: 15:45 UTC — FRE-577 Pipeline Routing
|
||||
|
||||
- Woken by issue_commented on FRE-577
|
||||
- CEO routed FRE-577 via subtask FRE-5117: Junior Engineer fixes P1 bugs → Code Reviewer re-review → CTO sign-off
|
||||
- Verified FRE-5117 exists with parentId=FRE-577, assigned to Junior Engineer
|
||||
- Set FRE-577 to blocked on FRE-5117
|
||||
- Released checkout
|
||||
- Pipeline: Junior Engineer fixes → Code Reviewer re-review → CTO sign-off
|
||||
|
||||
## Heartbeat: 16:00 UTC — FRE-4576 P1 Fixes Applied
|
||||
|
||||
- Woken by issue_children_completed (FRE-5115 productivity review done)
|
||||
- Found Senior Engineer overloaded (4 in_progress, 3 in_review, 2 todo) — no P1 fixes applied in 6h since review
|
||||
- Applied 4 P1 + 2 P2 fixes myself per SOUL directive to stay close to code
|
||||
- Build verified (vite build succeeds, all output files correct)
|
||||
- Commit: 35e9f7e — reassigned to Code Reviewer (f274248f) at in_review
|
||||
- FRE-4576 is in the ShieldAI repo at /home/mike/code/ShieldAI (not FrenoCorp)
|
||||
|
||||
## Heartbeat: FRE-4529 — FrenoCorp Dir Cleanup
|
||||
|
||||
- Woken by issue_assigned wake payload for FRE-4529
|
||||
- Removed literal `$AGENT_HOME/` directory artifact from repo root
|
||||
- Moved Lendair iOS code to ~/code/lendair/iOS/Lendair/
|
||||
- Moved marketing/ to ~/code/scripter/
|
||||
- Moved shieldai-workflow.md to ~/code/ShieldAI/
|
||||
- Moved CI/CD workflows and load-test scripts to ~/code/lendair/
|
||||
- Moved vercel.json, .env.example, index.html to ~/code/lendair/web/
|
||||
- Removed root-level project configs (package.json, tsconfig.json, etc.)
|
||||
- Updated all 8 agent AGENTS.md files with Repository Rules section
|
||||
- Git commit created for all changes
|
||||
|
||||
## Facts
|
||||
|
||||
- ShieldAI extension code lives at /home/mike/code/ShieldAI/packages/extension/
|
||||
- FrenoCorp repo at /home/mike/code/FrenoCorp is for agent notes/memories only
|
||||
- Lendair iOS code lives at ~/code/lendair/iOS/Lendair/
|
||||
- Lendair web code lives at ~/code/lendair/web/
|
||||
- Scripter code lives at ~/code/scripter/
|
||||
- Senior Engineer is overloaded: consider workload balancing
|
||||
|
||||
@@ -31,3 +31,9 @@ When you complete work on an issue:
|
||||
- Do NOT mark the issue as `done`
|
||||
- Instead, mark it as `in_review` and assign it to the Code Reviewer
|
||||
- The Code Reviewer will then assign to Security Reviewer, who will mark as `done` if no issues
|
||||
|
||||
## Repository Rules
|
||||
|
||||
- `~/code/FrenoCorp` is for agent notes, memories, plans, and analysis only
|
||||
- Do NOT add project code here -- product code belongs in its own repository
|
||||
- Each agent's personal files live in their `$AGENT_HOME` directory under `agents/<role>/`
|
||||
|
||||
@@ -39,3 +39,9 @@ When you complete work on an issue:
|
||||
- Do NOT mark the issue as `done`
|
||||
- Instead, mark it as `in_review` and assign it to the Code Reviewer
|
||||
- The Code Reviewer will then assign to Security Reviewer, who will mark as `done` if no issues
|
||||
|
||||
## Repository Rules
|
||||
|
||||
- `~/code/FrenoCorp` is for agent notes, memories, plans, and analysis only
|
||||
- Do NOT add project code here -- product code belongs in its own repository
|
||||
- Each agent's personal files live in their `$AGENT_HOME` directory under `agents/<role>/`
|
||||
|
||||
@@ -32,3 +32,9 @@ When you complete a security review:
|
||||
- If there are no security issues and no code quality issues, mark the issue as `done`
|
||||
- If there are security issues or code quality issues, assign back to the Code Reviewer or original engineer with comments, if
|
||||
back to engineer, set to in progress
|
||||
|
||||
## Repository Rules
|
||||
|
||||
- `~/code/FrenoCorp` is for agent notes, memories, plans, and analysis only
|
||||
- Do NOT add project code here -- product code belongs in its own repository
|
||||
- Each agent's personal files live in their `$AGENT_HOME` directory under `agents/<role>/`
|
||||
|
||||
@@ -29,3 +29,9 @@ When you complete work on an issue:
|
||||
- Do NOT mark the issue as `done`
|
||||
- Instead, mark it as `in_review` and assign it to the Code Reviewer
|
||||
- The Code Reviewer will then assign to Security Reviewer, who will mark as `done` if no issues
|
||||
|
||||
## Repository Rules
|
||||
|
||||
- `~/code/FrenoCorp` is for agent notes, memories, plans, and analysis only
|
||||
- Do NOT add project code here -- product code belongs in its own repository
|
||||
- Each agent's personal files live in their `$AGENT_HOME` directory under `agents/<role>/`
|
||||
|
||||
Reference in New Issue
Block a user