Initial commit

Author: KayTV

.env.example

@@ -0,0 +1,60 @@
+# Generate a random secret: https://generate-secret.vercel.app/32 or `openssl rand -base64 32`
+AUTH_SECRET=****
+
+# Google OAuth (for Google sign-in)
+GOOGLE_CLIENT_ID=****
+GOOGLE_CLIENT_SECRET=****
+
+# xAI API Key for chat and image models: https://console.x.ai/
+XAI_API_KEY=****
+
+# PostgreSQL database
+# Chat history, votes, documents, user data
+DATABASE_URL="postgresql://<user>:<password>@<host>.neon.tech/<dbname>?sslmode=require"
+
+# OpenAI API Key (primary AI provider)
+OPENAI_API_KEY=****
+
+# Alternative API keys (optional)
+ANTHROPIC_API_KEY=****
+
+# Google Cloud Configuration
+GOOGLE_VERTEX_LOCATION=****
+GOOGLE_VERTEX_PROJECT=****
+GOOGLE_APPLICATION_CREDENTIALS=./vertex-ai-credentials.json
+GOOGLE_CLOUD_PROJECT=****
+
+# Google Cloud Storage for file uploads
+GCS_BUCKET_NAME=****
+
+# Upstash Redis for shared links
+# Create a Redis database at https://console.upstash.com/
+UPSTASH_REDIS_REST_URL=****
+UPSTASH_REDIS_REST_TOKEN=****
+
+# Microsoft login
+AUTH_MICROSOFT_ENTRA_ID_ID=***
+AUTH_MICROSOFT_ENTRA_ID_SECRET=***
+AUTH_MICROSOFT_ENTRA_ID_ISSUER=https://login.microsoftonline.com/common/v2.0
+
+# API configuration
+# Customize these to connect to your external data source
+API_BASE_URL=https://api.example.com
+API_KEY=****
+
+# Environment name (dev, prod, preview-*, etc.)
+# Used for client-side environment checks (e.g. hiding suggested actions in prod)
+ENVIRONMENT=dev
+NEXT_PUBLIC_ENVIRONMENT=dev
+
+# Kernel.sh API key for remote browser management
+KERNEL_API_KEY=****
+
+# Feature flag for guest login
+# When true, enables guest login that bypasses OAuth (no credentials needed)
+# To enable locally: set both to true in your .env.local
+USE_GUEST_LOGIN=false
+NEXT_PUBLIC_USE_GUEST_LOGIN=false
+
+# Allowed email domains for OAuth sign-in (comma-separated)
+ALLOWED_EMAIL_DOMAINS=@example.com,@other.org

.eslintrc.json

@@ -0,0 +1,23 @@
+{
+  "extends": [
+    "next/core-web-vitals",
+    "plugin:import/recommended",
+    "plugin:import/typescript",
+    "prettier",
+    "plugin:tailwindcss/recommended"
+  ],
+  "plugins": ["tailwindcss"],
+  "rules": {
+    "tailwindcss/no-custom-classname": "off",
+    "tailwindcss/classnames-order": "off"
+  },
+  "settings": {
+    "import/resolver": {
+      "typescript": {
+        "alwaysTryTypes": true,
+        "project": "./tsconfig.json"
+      }
+    }
+  },
+  "ignorePatterns": ["**/components/ui/**"]
+}

.github/pull_request_template.md

@@ -0,0 +1,29 @@
+## Checklist
+
+- [ ] Update PR Title to follow this pattern: `[INTENT]:[MESSAGE]`
+  > The title will become a one-line commit message in the git log, so be as concise and specific as possible -- refer to [How to Write a Git Commit Message](https://cbea.ms/git-commit/). Prepend [Conventional Commit](https://www.conventionalcommits.org/en/v1.0.0/#summary) intent (`fix:`, `feat:`, `chore:`, `ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`).
+
+## Ticket
+
+Resolves #{TICKET NUMBER or URL or description} or Adds {new capability or feature}
+
+## Changes
+
+> What was added, updated, or removed in this PR.
+> Prefer small PRs; try to limit to 300 lines of code changes
+> * https://blog.logrocket.com/using-stacked-pull-requests-in-github/
+> * https://opensource.com/article/18/6/anatomy-perfect-pull-request
+> * https://developers.google.com/blockly/guides/modify/contribute/write_a_good_pr
+
+## Testing
+
+> What was tested? How did you test it? Add unit tests for new functions, integration tests for API/database interactions, and E2E tests for critical user flows.
+> * https://martinfowler.com/articles/practical-test-pyramid.html
+> * https://blog.logrocket.com/javascript-testing-best-practices/
+> * https://www.testim.io/blog/typescript-unit-testing-101/
+
+## Context for reviewers
+
+> Background context, more in-depth details of the implementation, and anything else you'd like to call out or ask reviewers.
+> Add comments to your code under the "Files Changed" tab to explain complex logic or code
+> * https://betterprogramming.pub/how-to-make-a-perfect-pull-request-3578fb4c112 

.github/workflows/lint.yml

@@ -0,0 +1,25 @@
+name: Lint
+on:
+  push:
+
+jobs:
+  build:
+    runs-on: ubuntu-22.04
+    strategy:
+      matrix:
+        node-version: [20]
+    steps:
+    - uses: actions/checkout@v4
+    - name: Install pnpm
+      uses: pnpm/action-setup@v4
+      with:
+        version: 9.12.3
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v4
+      with:
+        node-version: ${{ matrix.node-version }}
+        cache: 'pnpm'
+    - name: Install dependencies
+      run: pnpm install
+    - name: Run lint
+      run: pnpm lint

.gitignore

@@ -0,0 +1,55 @@
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# IDE
+.vscode
+
+# build artifacts
+*.tsbuildinfo
+next-env.d.ts
+
+# dependencies
+node_modules
+.pnp
+.pnp.js
+
+# testing
+coverage
+artifacts/session_*
+
+# next.js
+.next/
+out/
+build
+
+# misc
+.DS_Store
+*.pem
+
+# debug
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+.pnpm-debug.log*
+
+# local env files
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+# turbo
+.turbo
+
+.env
+.vercel
+.env*.local
+
+# Playwright
+/test-results/
+/playwright-report/
+/blob-report/
+/playwright/*
+vertex-ai-credentials.json
+
+.claude/

CODE_OF_CONDUCT.md

@@ -0,0 +1,126 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at labs@navapbc.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,70 @@
+# Contributing to the Form-Filling Assistant
+
+Thank you for your interest in contributing! The Form-Filling Assistant is an open-source AI tool built by [Nava Labs](https://www.navapbc.com/labs/ai-tools-public-benefits) to help caseworkers navigate benefit portals and complete applications on behalf of the families they serve. We welcome contributions from developers, designers, policy experts, and community members. This document explains how to get involved.
+
+## Community
+
+We are committed to providing a welcoming and respectful environment for all contributors. All contributors are expected to follow our [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Bugs and Issues
+
+Bug reports are welcome — they help us make this tool better for caseworkers and the communities they serve.
+
+When you're ready to file, [create a GitHub issue](https://github.com/navapbc/labs-form-filling-agent/issues/new) and include:
+- A clear description of the bug and what you expected to happen
+- Steps to reproduce
+- Your environment (OS, Node version, browser if relevant)
+- Any relevant logs or screenshots
+
+**Security issues:** Please do not file security vulnerabilities as public GitHub issues. See our [Security Policy](SECURITY.md) for how to report them privately.
+
+## Suggesting Features
+
+We're especially interested in feedback from people who work directly with caseworkers or benefit systems. If you have an idea for how this tool could better serve that context, [open a GitHub issue](https://github.com/navapbc/labs-form-filling-agent/issues/new) with the label `enhancement` and describe:
+- The problem you're trying to solve
+- Who it would benefit
+- Any ideas you have for how it might work
+
+## Getting Started
+
+To contribute code, start by forking the repository and setting up your local environment. See the [Getting Started](README.md#getting-started) section in the README for setup instructions.
+
+Once you're ready, submit a pull request with:
+- A clear title and description of what you changed and why
+- A reference to the related issue (e.g., `Closes #123`)
+- Screenshots or screen recordings for UI changes
+- Test results confirming nothing is broken
+
+## Code Review Process
+
+### Submitting for Review
+
+Before opening a pull request:
+- Make sure all tests pass locally
+- Update any documentation affected by your changes
+- Do a self-review of your diff before requesting others' time
+- Request a review from a maintainer
+
+### Review Criteria
+
+Reviewers will evaluate contributions for:
+
+- **Functionality** — does the code work as intended?
+- **Security** — are there any vulnerabilities or data exposure risks, particularly given the sensitive nature of benefit casework?
+- **Performance** — does this impact system responsiveness for users on lower-bandwidth connections?
+- **Accessibility** — does this maintain accessibility standards (WCAG 2.1 AA)?
+- **Maintainability** — is the code readable, well-structured, and documented?
+- **Testing** — is there adequate test coverage for the changes?
+
+### Addressing Feedback
+
+- Respond to review comments in a timely way
+- Make requested changes or explain your reasoning if you'd like to discuss an alternative
+- Update tests and documentation as needed
+- Re-request review once changes are complete
+
+## Questions?
+
+If you're unsure about anything before contributing, feel free to open a GitHub issue with the `question` label. We'd rather you ask than get stuck.
+
+Thank you for contributing to the Form-Filling Assistant!