Deploy to Production / Build & Verify (push) Failing after 5m56s
Ping Search Engines / Notify Search Engines (push) Successful in 2s
Deploy to Production / Pre-Deploy Tests (push) Has been skipped
Deploy to Production / Deploy to Railway (push) Has been skipped
Deploy to Production / Deploy to Render (push) Has been skipped
Deploy to Production / Deploy to VPS (PM2) (push) Has been skipped
Deploy to Production / Deploy to Fly.io (push) Has been skipped
Deploy to Production / Post-Deploy Verification (push) Has been skipped
Deploy to Production / Notify on Failure (push) Successful in 2s
E2E Test Suite / Critical User Journeys (push) Has been skipped
E2E Test Suite / API Integration Tests (push) Has been skipped
E2E Test Suite / Smoke Tests (P0) (push) Failing after 11m26s
E2E Test Suite / Form Interaction Tests (push) Failing after 11m42s
E2E Test Suite / Destructive & Chaos Tests (push) Failing after 12m2s
E2E Test Suite / Cross-Browser Regression (chromium) (push) Failing after 16m14s
E2E Test Suite / Cross-Browser Regression (webkit) (push) Failing after 17m45s
E2E Test Suite / Cross-Browser Regression (firefox) (push) Failing after 25m23s
E2E Test Suite / Security Header Tests (push) Failing after 7m55s
E2E Test Suite / Test Report Summary (push) Failing after 20s
E2E Test Suite / Mobile Device Tests (push) Failing after 2h49m9s
Uptime Monitor / Health & Response Time (push) Failing after 2s
Uptime Monitor / SSL Certificate (push) Successful in 2s
Uptime Monitor / Send Alerts (push) Failing after 3s
Uptime Monitor / Record Uptime Success (push) Has been skipped
28 lines
688 B
Markdown
28 lines
688 B
Markdown
---
|
|
user: Unknown
|
|
project: Company Site
|
|
last_updated: 2026-03-21T10:41:40.099526+00:00
|
|
---
|
|
|
|
# User Context — Company Site
|
|
|
|
## User
|
|
**Name**: Not specified
|
|
|
|
## Project
|
|
**Name**: Company Site
|
|
**Description**: No description provided
|
|
|
|
## User Preferences
|
|
- _No specific preferences recorded yet_
|
|
|
|
## Instructions
|
|
- Follow the project's existing code style and conventions
|
|
- Respect the directory structure already in place
|
|
- Use the same language/framework patterns found in existing code
|
|
- When in doubt, check with the user through the project chat
|
|
|
|
## Notes
|
|
_This file is updated as the user provides preferences and feedback._
|
|
_Agents should check this file before starting any task._
|