Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions AGENTS.override.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# Agent Continuity Entry Point

Before work, read the existing `AGENTS.md` if present, then `docs/agent/PROJECT_KNOWLEDGE.md`, `docs/agent/INTEGRATIONS.md`, and `docs/agent/HANDOFF.md`. Read any project-native status file they name.

Continuity is part of the build:
- Before the final build/check, compare changed code/configuration with the durable context. Add material commands, environment-variable **names**, services, connectors, data sources, constraints, and decisions discovered during the work.
- After verification, update the handoff whenever work is incomplete, blocked, awaiting approval, or intentionally deferred.
- Record one exact executable next action, affected files, tests run, exact failures, environment state, and approval still required.
- If complete, clear stale steps and set `Status: Complete — no active handoff`.
- Never record secret values, tokens, credentials, private keys, private connection strings, customer data, or private infrastructure identifiers.

Operate autonomously for routine reversible work within the authorized repository. Prefer verified MCP connectors, then approved CLI/SDK access, then controlled browser work. Verify connectors with a harmless read. Pause for production deployment, destructive operations, production data writes, credential/permission changes, auth/security changes, billing, public publishing, or access outside the task.
21 changes: 21 additions & 0 deletions docs/agent/HANDOFF.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# Work Handoff

- Repository: `classicitbb/threeplmgmt`
- Status: Baseline complete — no task-specific active handoff recorded
- Last updated: 2026-08-24

## Current state

The continuity harness was generated from repository evidence.

## Exact next action

For the next substantive task, inspect the relevant implementation and tests, then replace this baseline with the exact continuation state if work remains.

## Baseline verification

Inspected available agent/status files, package manifest, README, environment example, Supabase configuration, and known hosting linkage. No application build, test, deployment, or external write beyond this draft branch/PR was performed.

## Required incomplete-work record

Objective; current state; completed steps; affected files; tests/commands and exact failures; deployment/environment state; blocker; approval required; one exact executable next action.
18 changes: 18 additions & 0 deletions docs/agent/INTEGRATIONS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# Integrations and Connector Contract

| Service | Purpose | Verification | Write boundary |
|---|---|---|---|
| GitHub | Source control and review | Verified repository access | Feature branches/PRs within task scope |
| Vercel | Hosting | Project `warehouse-wizard-v1` linkage verified | Preview first; production approval boundary |
| Supabase | Database/auth/storage/functions as used by code | Repository configuration detected | Verify project/account before writes |
| Lovable | Project editing/generation workflow | Repository evidence detected | Review generated diffs; verify publish path |

Add every real external service when verified. Access to one service does not imply access to another.

## Rules

- Prefer installed/authenticated MCP, then approved CLI/SDK, then controlled browser interaction.
- Verify the target project/account with a harmless read before writes.
- Store credential values only in approved secret systems.
- Use least privilege, idempotency, bounded retries, audit context, and reconciliation for automated writes.
- Production deployments/data, auth/security, credentials, billing, external messages, and destructive actions remain approval gates unless explicitly authorized.
63 changes: 63 additions & 0 deletions docs/agent/PROJECT_KNOWLEDGE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
# Project Knowledge

- Repository: `classicitbb/threeplmgmt`
- Default branch: `main`
- Visibility: `public`
- Last verified: 2026-08-24
- Business owner: Russell Hunte
- Existing project instructions: `AGENTS.md`
- Existing status ledger: none detected

## Purpose

Warehouse Wizard is a production-oriented internal WMS app for a 3PL-style warehouse operation. It supports warehouse setup, product master data, receiving, directed putaway, pallet-level inventory search, picking, transfers, cycle counts,

## Verified stack

- React (^18.3.1)
- Vite (^7.3.1)
- TypeScript (^5.8.3)
- Tailwind CSS (^3.4.17)
- Supabase (^2.106.2)
- TanStack Query (^5.100.14)
- Vitest (^4.1.8)
- Playwright (^1.60.0)
- Lovable-origin or Lovable-managed workflow is referenced by repository evidence.
- Vercel project linkage verified: `warehouse-wizard-v1`.

## Commands

Evidence: `package.json`.

| Script | Agent command | Implementation |
|---|---|---|
| dev | `npm run dev` | `vite` |
| build | `npm run build` | `vite build` |
| build:dev | `npm run build:dev` | `vite build --mode development` |
| lint | `npm run lint` | `eslint .` |
| preview | `npm run preview` | `vite preview` |
| test | `npm run test` | `vitest run` |
| test:watch | `npm run test:watch` | `vitest` |

Use the repository lockfile’s package manager. Commands above are discovered, not necessarily executed during this rollout.

## Environment-variable names

Names are defined in the repository environment example; inspect it only as required and do not duplicate private topology here.

Update this section whenever code introduces, removes, or renames configuration. Record names and purpose only, never values.

## Sources of truth

- Code and behavior: this repository.
- Commands/dependencies: package manifest and lockfile.
- Current work: `docs/agent/HANDOFF.md` until a project-native status file is established.
- Project rules: existing `AGENTS.md`, then the continuity override.
- Hosting: verified Vercel linkage `warehouse-wizard-v1`.
- Database/schema: `supabase/**` where present.

## Durable decisions

- Keep verified project context and resumable handoff state in `docs/agent/`.
- Update continuity during the same build/change that reveals new facts.
- Do not infer working behavior from UI placeholders or documentation alone.