sshar278

E-Invitations Revamp Master Brief

This file is the single source of truth for understanding the current E-invitations implementation, the target revamp, the data and architecture already available in the codebase, and what still needs confirmation before implementation.

It is written so it can be copied into a GitHub Gist as-is.

Later, this can be split into smaller documents for UI, architecture, API/data mapping, implementation plan, QA, and open questions.

1. Goal

sshar278

Feature Home Page Auth Merge Safety

This note is specifically about auth and auth-adjacent files from feature/nvite-bulk-upload-ui that may get pulled into feature/home-page.

It does not cover the guest-management UI files.

Quick Summary

Patch Immediately

sshar278

Preflight — FINAL Execution Spec (Claude Code CLI)

Your job is to implement Preflight EXACTLY as specified. Do NOT skip requirements. Do NOT add “nice to haves” unless explicitly instructed. Stop at each checkpoint and wait for confirmation.

0. Non-Negotiable Rules (must follow) PRIORITY ORDER (always)

(A) Must-have UI controls + navigation

sshar278

ForgeGuard — FINAL Execution Spec (Claude Code CLI)

Your job is to implement ForgeGuard EXACTLY as specified. Do NOT skip requirements. Do NOT add “nice to haves” unless explicitly instructed. Stop at each checkpoint and wait for confirmation.

---

0) Non-Negotiable Rules (must follow)

sshar278

ForgeGuard — Agent Execution Playbook (Steps 4 → 5)

You are an AI coding agent connected to an InsForge project via MCP. You are operating inside a sandbox environment.

Your goal is to build ForgeGuard:
a standalone, shareable AI-powered backend safety & deployment-readiness console.

Follow ALL instructions carefully and sequentially.