Project Audit / Health Check

What this is

A full project health check the user triggers with a phrase like "run an audit" or "what can I do from here?" — rendered as a color-coded HTML card matrix showing what's solid, what needs attention, and what's broken, with a recommended action for each issue. Also covers the reusable HTML assessment template and the close-out summary render.

Assess first

• Check whether admin\AGENT_INSTRUCTIONS.md already has a PROJECT AUDIT section.
• Confirm the values the audit checks are reachable: instructions sync, canonical path registration, connectors, brand standards, entity profile, logo, #drop\ contents, trackers, tracker index, seeded items, active flags, reconciliation items, version numbers, folder structure, project cache manifest and directory.
• Check whether trackers\templates\bootstrap_assessment_template.html exists (the reusable render template).

Ask, only if needed

Nothing to ask — proceed directly to Write. The audit is triggered by the user on demand.

Write

Add this section to admin\AGENT_INSTRUCTIONS.md:

◆ PROJECT AUDIT

Triggered by: "run an audit" · "health check" · "check everything"
  "read me the help file" · "what can I do from here?"

Render audit results as an inline HTML card matrix — color-coded rows
(green good / amber needs attention / red missing or broken), header bar
with project name and date, summary footer with item counts. Not text
output. Not ASCII art.

Header bar: "Project Audit — [Project Name]" · date/time · Bootstrap v[X.X]
Rows: each item with a status indicator and an action if needed.
Summary footer: X items confirmed · Y need attention · Z require action.

Items checked:
- Agent instructions sync (Project Instructions field vs. local file)
- Canonical path accessible via Filesystem MCP — confirm the path is
  REGISTERED in the connector, not just that the connector is live
- Connector status — anything dropped since last session?
- Brand standards present and current — in agent instructions AND uploaded
  to Project Files
- Entity profile complete — sanitized copy in Project Files, full in admin\
- Logo in Project Files (PNG, white background) — filename matches what the
  instructions reference
- #drop\ — files waiting to be sorted?
- Trackers — data files current, HTML generated (search broadly for HTML:
  subdirectories named tracking/tracker/templates/dashboard/matrix before
  declaring missing), README present
- Tracker index current
- Seeded items in the current session
- Active flags open
- Files missing version numbers
- Files outside expected folders
- Bootstrap reconciliation items — any open from prior runs?
- Bootstrap version on file vs. the current catalog version
- Project Cache manifest present in trackers\data\
- project_cache\ directory exists
- Last cache refresh date (prompt a refresh if more than one session has
  passed)

After rendering: report what's solid and what needs attention with
specific recommended actions. If reconciliation items are open, surface
them prominently.

Also note two related renders (produced during bootstrap wrap-up, same card-matrix visual language):

• Assessment template: present the Current State Summary HTML for download as bootstrap_assessment_template.html; instruct the user to save it to trackers\templates\. Future audits and bootstrap runs reference it for consistent visual output.
• Close-out summary: at bootstrap wrap-up, render an inline HTML close-out card (project, repository, type, entity/brand status, instructions version, trackers, reconciliation count) plus "what was done this session" and a "before you go" checklist. Include the logo reminder (upload [ProjectCode]_Logo.png, PNG white background, tightly cropped).

Confirm

Confirm: the Project Audit is installed — say "run an audit" anytime for a color-coded health-check matrix with recommended actions for anything that needs attention. Want to install another, or is that everything for now?