vibefast-cli 0.7.0 → 0.7.2

package/2/.claude/docs/tech-stack.md

@@ -1,157 +0,0 @@
-# Tech Stack Documentation
-
-## Overview
-
-Next.js application with Convex backend, Better Auth authentication, and Tailwind CSS v4 styling. Built with TypeScript and React 19.
-
-## Programming Language & Runtime
-
-- **TypeScript**: 5.x
-- **Node.js**: v18.20.8
-- **Package Manager**: pnpm
-
-## Frontend
-
-### UI Framework
-
-- **React**: 19.1.0
-- **React DOM**: 19.1.0
-- **Next.js**: 15.4.4 (App Router)
-
-### Styling
-
-- **Tailwind CSS**: v4
-- **PostCSS**: @tailwindcss/postcss
-- **tw-animate-css**: 1.3.6
-- **Fonts**: Geist Sans, Geist Mono (Google Fonts)
-
-### Component Libraries
-
-- **Radix UI**: Full suite of primitives (accordion, alert-dialog, avatar, checkbox, dialog, dropdown-menu, etc.)
-- **shadcn/ui components**: Built on Radix UI
-- **class-variance-authority**: 0.7.1
-- **clsx**: 2.1.1
-- **tailwind-merge**: 3.3.1
-
-### State Management
-
-- **jotai-x**: 2.3.3
-- **React Hook Form**: 7.61.1
-- **@hookform/resolvers**: 5.2.0
-
-### Data Fetching
-
-- **@tanstack/react-query**: 5.83.0
-- **@convex-dev/react-query**: 0.0.0-alpha.11
-
-### UI Components
-
-- **cmdk**: 1.1.1 (Command palette)
-- **date-fns**: 4.1.0 (Date utilities)
-- **embla-carousel-react**: 8.6.0
-- **input-otp**: 1.4.2
-- **lucide-react**: 0.526.0 (Icons)
-- **react-day-picker**: 9.8.1
-- **react-resizable-panels**: 3.0.3
-- **recharts**: 2.15.4 (Charts)
-- **sonner**: 2.0.6 (Toast notifications)
-- **vaul**: 1.1.2 (Drawer component)
-
-### Utilities
-
-- **next-themes**: 0.4.6 (Theme management)
-- **nuqs**: 2.4.1 (URL state management)
-- **ts-essentials**: 10.1.1
-
-## Backend
-
-### Backend Framework
-
-- **Convex**: 1.25.2
-- **convex-ents**: 0.15.0 (Entity system)
-- **convex-helpers**: 0.1.99
-
-### Authentication
-
-- **better-auth**: 1.3.4
-- **@convex-dev/better-auth**: 0.7.0 (Convex adapter)
-
-### Backend Components
-
-- **@convex-dev/aggregate**: 0.1.21
-- **@convex-dev/rate-limiter**: 0.2.10
-
-### Validation
-
-- **zod**: 3.25.76
-
-## Database & Storage
-
-- **Convex Database**: Built-in reactive database
-- **Schema**: Defined using convex-ents with users table
-
-## Development Tools & Workflow
-
-### Build Tools
-
-- **Next.js Turbopack**: Development server
-- **TypeScript**: Compiler with custom tsconfig
-
-### Scripts
-
-```json
-{
-  "build": "next build",
-  "dev": "concurrently 'pnpm dev:app' 'pnpm dev:backend'",
-  "dev:app": "next dev --turbopack",
-  "dev:backend": "convex dev",
-  "lint": "next lint",
-  "lint:fix": "next lint --fix",
-  "typecheck": "tsc --noEmit",
-  "typecheck:watch": "pnpm typecheck --watch",
-  "seed": "convex run seed:seed",
-  "studio": "pnpm convex dashboard"
-}
-```
-
-### Development Dependencies
-
-- **ESLint**: v9 with Next.js config
-- **@types/node**: v20
-- **@types/react**: v19
-- **@types/react-dom**: v19
-- **concurrently**: 9.2.0
-
-### Environment Configuration
-
-- **@t3-oss/env-nextjs**: 0.13.8
-
-## TypeScript Configuration
-
-```json
-{
-  "strict": false,
-  "strictNullChecks": true,
-  "target": "es2022",
-  "module": "esnext",
-  "moduleResolution": "bundler",
-  "jsx": "preserve",
-  "paths": {
-    "@/*": ["./src/*"],
-    "@convex/*": ["./convex/*"]
-  }
-}
-```
-
-## Path Aliases
-
-- `@/*` � `./src/*`
-- `@convex/*` � `./convex/*`
-
-## Convex Configuration
-
-- Better Auth integration
-- Rate limiting
-- User aggregation
-- Custom authentication with email verification
-- Session management (30-day expiry, 15-day update age)

package/2/.claude/scripts/tree.sh

@@ -1,70 +0,0 @@
-#!/bin/bash
-
-# Custom folders to ignore (in addition to .gitignore)
-CUSTOM_IGNORE="@trunk|skill-tree|@skill-tree|public|migrations|tracingDir|eslint.tsconfig.mjs|tooling|sentry*|.github"
-
-# Parse tsconfig.json exclude patterns
-TSCONFIG_IGNORE=""
-if [ -f "tsconfig.json" ]; then
-    # Extract exclude patterns from tsconfig.json
-    # Parse the JSON properly and handle wildcards
-    TSCONFIG_PATTERNS=$(node -e "
-        const fs = require('fs');
-        const tsconfig = JSON.parse(fs.readFileSync('tsconfig.json', 'utf8'));
-        if (tsconfig.exclude) {
-            const patterns = tsconfig.exclude.map(p => {
-                // Remove leading **/ and trailing /*
-                return p.replace(/^\*\*\//, '').replace(/\/\*$/, '').replace(/^\*\*/, '');
-            }).filter(p => p && !p.includes('*'));
-            console.info(patterns.join('|'));
-        }
-    " 2>/dev/null || echo "")
-    
-    if [ -n "$TSCONFIG_PATTERNS" ]; then
-        TSCONFIG_IGNORE="|$TSCONFIG_PATTERNS"
-    fi
-fi
-
-# Combine all ignore patterns
-FULL_IGNORE=".git|*.bak|$CUSTOM_IGNORE$TSCONFIG_IGNORE"
-
-# Output file
-OUTPUT=".claude/docs/project-structure.md"
-
-# Create directory if it doesn't exist
-mkdir -p .claude/docs
-
-# Header
-cat > "$OUTPUT" << 'EOF'
-# Project Structure
-
-EOF
-
-echo "_Last Updated: $(date +%Y-%m-%d)_" >> "$OUTPUT"
-echo "" >> "$OUTPUT"
-echo '```' >> "$OUTPUT"
-
-# Backup original .gitignore
-cp .gitignore .gitignore.bak
-
-# Remove !.* line temporarily (both commented and uncommented versions)
-grep -v '^!\.\*' .gitignore | grep -v '^# !\.\*' > .gitignore.tmp && mv .gitignore.tmp .gitignore
-
-# Use tree with gitignore (now without !.* line)
-tree --gitignore \
-  -a \
-  -I "$FULL_IGNORE" \
-  --dirsfirst \
-  >> "$OUTPUT"
-
-# Restore original .gitignore
-mv .gitignore.bak .gitignore
-
-# Close code block
-echo '```' >> "$OUTPUT"
-echo "" >> "$OUTPUT"
-
-echo "Project structure written to $OUTPUT"
-
-# Output the contents to stdout as well
-cat "$OUTPUT"

package/2/.claude/settings.json

@@ -1,30 +0,0 @@
-{
-  "permissions": {
-    "allow": ["Bash", "Edit", "mcp__task_master_ai__*"]
-  },
-  "enableAllProjectMcpServers": true,
-  "hooks": {
-    "Stop": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "DATA=$(cat); TRANSCRIPT=$(echo \"$DATA\" | jq -r '.transcript_path'); TITLE=$(grep -m1 '\"type\":\"summary\"' \"$TRANSCRIPT\" 2>/dev/null | jq -r '.summary' 2>/dev/null || echo \"Claude Code\"); terminal-notifier -message \"Claude finished responding\" -title \"$TITLE\" -sound Ping"
-          }
-        ]
-      }
-    ],
-    "PreCompact": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "DATA=$(cat); TRANSCRIPT=$(echo \"$DATA\" | jq -r '.transcript_path'); TITLE=$(grep -m1 '\"type\":\"summary\"' \"$TRANSCRIPT\" 2>/dev/null | jq -r '.summary' 2>/dev/null || echo \"Claude Code\"); terminal-notifier -message \"Compacting conversation...\" -title \"$TITLE\" -sound Bottle"
-          }
-        ]
-      }
-    ]
-  }
-}

package/2/.cursor/commands/code-review-high.md

@@ -1,190 +0,0 @@
-<task>
-$1
-</task>
-
-<role>
-  You are a senior software engineer, security reviewer, and performance specialist. Review the provided change with a focus on correctness, security, performance, integration, test quality, and long-term maintainability. Be precise, cite file paths and line ranges, and prioritize risks that could impact users, data, uptime, or developer velocity.
-</role>
-
-<objectives>
-- Identify correctness defects, code smells, and anti-patterns.
-- Surface exploitable security issues and data-protection risks.
-- Spot performance/regression risks and complexity hotspots.
-- Check integration points (APIs, events, DB, configs, CI/CD, infra) for compatibility and rollout safety.
-- Assess tests for sufficiency, signal, reliability, and coverage.
-- Recommend minimal, safe, high-leverage improvements and monitoring.
-</objectives>
-
-<severity_rubric>
-
-- BLOCKER: Exploitable security flaw, data loss risk, broken build/deploy, user-impacting crash, irreversible migration risk, leaked secrets.
-- HIGH: Likely prod incident or major regression; authz/auth gaps; significant perf degradation; schema incompatibility.
-- MEDIUM: Correctness edge cases; non-exploitable but risky pattern; moderate perf concerns; flaky tests.
-- LOW: Maintainability, readability, style, minor test gaps; suggestions.
-- NIT: Optional polish.
-  </severity_rubric>
-
-<tasks>
-- Scope & Impact: Map all affected files/modules and why each is implicated. Note transitive and runtime impact (build, deploy, config, data).
-- Root Cause / Risk Analysis: Explain the change intent, risks introduced, and any hidden assumptions or environmental dependencies.
-- Security Review: Use the checklist below; escalate any secret exposure, injection, auth/authz flaws, SSRF/XXE/path traversal, insecure deserialization, command execution, mass assignment, CSRF/XSS, prototype pollution, weak crypto, missing TLS verification, permissive CORS, logging of secrets/PII, dependency vulns, or IaC/container misconfigurations.
-- Performance Review: Identify complexity issues, N+1 queries, unbounded loops, memory churn/leaks, blocking I/O on hot paths, missing indexes, cache misuse, chatty network calls, unnecessary allocations/boxing, and concurrency contention.
-- Integration Review: Validate API schema changes, versioning, backward/forward compatibility, idempotency, retries/timeouts/circuit breakers, feature-flag rollout, DB migrations (order/locking/rollback), message/event contracts, and config drift.
-- Testing Review: Evaluate unit/integration/e2e tests, coverage, negative/property-based cases, concurrency/time-dependent tests, fixture health, determinism, and flakiness risk. Propose a targeted test plan.
-- Observability & Operations: Check log levels, PII in logs, correlation/trace IDs, metrics and alerts, runbooks. Recommend what to monitor post-merge.
-- Documentation & DX: Flag missing or outdated README/CHANGELOG/ADRs/API docs/config comments/schema diagrams. Note onboarding and maintenance friction.
-- Minimal, Safe Fix: Propose the smallest viable change to eliminate blockers/high risks. Include tests and rollout/rollback steps.
-</tasks>
-
-<detailed_checklist>
-<category name="Correctness & Code Smells">
-
-- Duplicate code / long methods / large classes / deep nesting.
-- Leaky abstractions, tight coupling, poor cohesion, improper layering.
-- Dead code, unused variables/imports, TODOs that should be addressed now.
-- Non-idempotent operations where idempotency is required.
-- Edge cases: null/empty/NaN/overflow/encoding/timezone/locale.
-- Concurrency: shared state, race conditions, improper locking, async misuse.
-  </category>
-
-  <category name="Security">
-
-- Secrets in code/logs/env/examples; credential handling, key rotation, KMS/secret manager usage.
-- Input validation & output encoding; SQL/NoSQL/LDAP/OS injection; XSS (reflected/stored/DOM); CSRF.
-- AuthN/AuthZ: broken access control, least privilege, multi-tenant boundaries, insecure direct object references.
-- SSRF/XXE/path traversal/file upload validation; sandboxing for untrusted inputs.
-- Crypto: algorithms, modes, IVs, nonces, randomness, key sizes, cert pinning/TLS verification.
-- CORS/security headers (CSP/HSTS/X-Frame-Options/SameSite), cookie flags.
-- Dependency & supply chain: pinned versions, known CVEs, pre/post-install scripts, integrity checks.
-- IaC/Containers: public buckets, open security groups (0.0.0.0/0), missing encryption, root containers, mutable latest tags.
-- Data protection & privacy: PII/PHI handling, minimization, retention, encryption at rest/in transit.
-  </category>
-
-  <category name="Performance">
-
-- Time/space complexity, hot-path allocations, unnecessary synchronization.
-- N+1 queries, missing DB indexes, inefficient joins, full scans, pagination vs. streaming.
-- Caching: invalidation, eviction, key design, stampedes.
-- Network patterns: chattiness, batching, compression, timeouts, backoff.
-- Client-side perf (if UI): bundle size/regressions, critical path, images/fonts.
-  </category>
-
-  <category name="Integration & Rollout Safety">
-
-- Backward/forward compatibility; versioned contracts; consumer-producer alignment.
-- DB migrations: zero-downtime (expand/migrate/contract), locks, data backfills, rollback plan.
-- Feature flags: default off, kill switch, gradual rollout, owner/expiry.
-- Resilience: retries with jitter, timeouts, circuit breakers, idempotency keys.
-- Config changes: validation, defaults, environment parity, secrets not in plain text.
-- CI/CD: reproducibility, cache safety, test gates, artifact signing.
-  </category>
-
-  <category name="Testing & Quality Signals">
-
-- Tests exist for new behavior and regressions; meaningful assertions.
-- Coverage on critical branches/edge cases; mutation score (if available).
-- Isolation: minimal mocking vs. over-mocking; flaky patterns (sleep-based timing, order reliance).
-- Property-based/fuzz tests for parsers/validators/serializers.
-- Load/soak tests where perf risk exists; snapshot tests stability (if UI).
-  </category>
-
-  <category name="Docs, Observability, Accessibility, i18n">
-
-- README/CHANGELOG/ADR/API docs updated; code comments for non-obvious logic.
-- Logs/metrics/traces with actionable context; PII redaction; alert thresholds.
-- Accessibility (if UI): semantics, focus order, labels, contrast, keyboard nav, ARIA use.
-- i18n/l10n: hard-coded strings, pluralization, date/time/number formats.
-  </category>
-  </detailed_checklist>
-
-  <output_requirements>
-  <instructions>
-
-- Produce a concise but comprehensive report.
-- Group findings by category and severity.
-- Reference exact file paths and line ranges (e.g., src/foo/bar.py:120–147).
-- Include brief code excerpts only as necessary (≤20 lines per finding).
-- Prefer specific, minimal fixes and tests that maximize risk reduction.
-- If information is missing, state the assumption and its impact.
-  </instructions>
-  </output_requirements>
-
-  <report_skeleton>
-
-- Summary:
-  - What changed: <concise overview>
-  - Top risks: <1-3 bullets>
-  - Approval: <approve|comment|request_changes|blocker>
-
-- Affected files:
-  - <path> — <reason> (<added|modified|deleted>)
-
-- Root cause & assumptions:
-  - <analysis>
-  - Assumptions: <items>
-
-- Findings (repeat per finding):
-  - [<severity>] [<category>] <short title>
-    - Where: <file:line-range>
-    - Evidence: <brief snippet_trace>
-    - Impact: <what breaks_who is affected>
-    - Standards: <CWE/OWASP/Policy refs>
-    - Repro: <steps>
-    - Recommendation: <minimal fix>
-    - Tests: <tests to add_update>
-
-- Performance:
-  - Hotspots: <items>
-  - Complexity notes: <items>
-  - Bench/Monitoring plan: <how to measure & watch>
-
-- Integration:
-  - API/contracts: <compat/versioning/idempotency>
-  - DB migrations: <expand-migrate-contract, locks, rollback>
-  - Feature flags & rollout: <plan/kill switch_owner>
-  - Resilience: <timeouts/retries/circuits>
-  - Rollback plan: <how to revert safely>
-
-- Testing:
-  - Coverage: <statements_branches_critical_paths>
-  - Gaps: <cases>
-  - Flakiness risks: <items>
-  - Targeted test plan: <Given_When_Then bullets>
-
-- Docs & Observability:
-  - Docs to update/create: <paths/sections>
-  - Logs/Metrics/Traces/Alerts: <plan>
-  - Runbook: <updates>
-
-- Open questions:
-  - <items>
-
-- Final recommendation:
-  - Decision: <approve|comment|request_changes|blocker>
-  - Must-fix before merge: <items>
-  - Nice-to-have post-merge: <items>
-  - Confidence: <low|medium|high>
-    </report_skeleton>
-
-<process_notes>
-
-- Prioritize BLOCKER/HIGH issues. If any are found, set approval to “blocker” or “request_changes”.
-- Favor minimal, safe changes and targeted tests over broad refactors (unless safety demands it).
-- If diff is very large, focus on high-risk/new code paths, public interfaces, security-critical modules, and hot paths.
-- Reference concrete files/lines. Keep code excerpts minimal (≤20 lines). Do not rewrite large code blocks.
-- If required inputs are missing (e.g., DB migration script or API schema), flag as a risk and propose what is needed.
-  </process_notes>
-
-<constraints>
-- DO NOT write or generate full code implementations in this review. Provide patch outlines, pseudocode, or stepwise instructions only.
-- Maintain confidentiality: if a secret or sensitive data appears, describe it without reproducing it verbatim.
-</constraints>
-
-<success_criteria>
-
-- Findings are specific, actionable, and ordered by severity and blast radius.
-- Every high-risk change has a minimal fix and a concrete test/monitoring plan.
-- Output follows the provided report skeleton (markdown text only).
-  </success_criteria>
-
-<reminder>DON'T CODE YET.</reminder>

package/2/.cursorignore

@@ -1,3 +0,0 @@
-!.env
-!.env.local
-!.env.production

package/2/.github/ISSUE_TEMPLATE.md

@@ -1,13 +0,0 @@
-# Summary:
-
-## Steps to reproduce:
-
-## Expected behavior:
-
-## Additional notes:
-
-#### Tasks
-
-- [ ] Task 1
-- [ ] Task 2
-- [ ] Task 3

package/2/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,23 +0,0 @@
-## What does this do?
-
-<!---
-_Describe what your changes **do**; did you add a $COOL_FEATURE? Write about it here._
--->
-
-## Why did you do this?
-
-<!---
-_**Why** did you make these changes? This is your opportunity to provide the rationale that drove the design of your solution._
--->
-
-## Who/what does this impact?
-
-<!---
-_Does your code affect something downstream? Are there side effects people should know about? Tag any developers that should be kept abreast of this change._
--->
-
-## How did you test this?
-
-<!---
-_How did you test your change? Document it here._
--->

package/2/.github/actions/eas-build/action.yml

@@ -1,85 +0,0 @@
-# 🔗 Links:
-# Source file: https://github.com/obytes/react-native-template-obytes/blob/master/.github/actions/eas-build/action.yml
-# EAS Build docs: https://docs.expo.dev/eas-update/github-actions/
-
-# ✍️ Description:
-# This is a composite action, which means it can be used in other actions.
-# This action is used to trigger an EAS Build for a specific environment (local, staging, production).
-# This action accepts those inputs:
-#        `APP_ENV`, which is used to generate an APK for a specific environment (local, staging, production). We use staging by default.
-#        `AUTO_SUBMIT`, false by default, set to true if you want to automatically submit your build to stores.
-#        `EXPO_TOKEN`, required, access token for your Expo account. https://expo.dev/settings/access-tokens
-#        `VERSION`, required, version of the app to build. used as the build message.
-#        `ANDROID`, true by default, set to true if you don't want to trigger build for Android.
-#        `IOS`, false by default, set to true if you  want to trigger build for IOS.
-
-# Before triggering the build, we run a pre-build script to generate the necessary native folders based on the APP_ENV.
-# Based on the ANDROID and IOS inputs, we trigger the build for the corresponding platform with the corresponding flags.
-
-# 👀 Example usage:
-#      - name: ⏱️ EAS Build
-#        uses: ./.github/actions/eas-build
-#        with:
-#          APP_ENV: staging
-#          EXPO_TOKEN: ${{ secrets.EXPO_TOKEN }}
-#          VERSION: ${{ github.event.release.tag_name }}
-#          IOS: false
-
-name: 'Setup EAS Build + Trigger Build'
-description: 'Setup EAS Build + Trigger Build'
-inputs:
-  APP_ENV:
-    description: 'APP_ENV (one of): local, staging, production'
-    required: true
-    default: 'staging'
-  AUTO_SUBMIT: ## TODO: we need to handle this too
-    description: 'AUTO_SUBMIT (one of): true, false'
-    required: true
-    default: 'false'
-  ANDROID:
-    description: 'run for ANDROID (one of): true, false'
-    required: true
-    default: 'true'
-  VERSION:
-    description: 'VERSION'
-    required: true
-    default: '0.0.0'
-  IOS:
-    description: 'run for IOS (one of): true, false'
-    required: true
-    default: 'false'
-  EXPO_TOKEN:
-    description: 'EXPO_TOKEN'
-    required: true
-    default: 'false'
-
-runs:
-  using: 'composite'
-  steps:
-    - name: 💯 Check for EXPO_TOKEN
-      run: |
-        if [ -z "${{ inputs.EXPO_TOKEN }}" ]; then
-          echo "You must provide an EXPO_TOKEN secret linked to this project's Expo account in this repo's secrets. Learn more: https://docs.expo.dev/eas-update/github-actions"
-          exit 1
-        fi
-      shell: bash
-
-    - name: 📦 Setup Expo and EAS
-      uses: expo/expo-github-action@v8
-      with:
-        eas-version: latest
-        token: ${{ inputs.EXPO_TOKEN }}
-
-    - name: ⚙️ Run Prebuild
-      run: pnpm prebuild:${{ inputs.APP_ENV }}
-      shell: bash
-
-    - name: 📱 Run Android Build
-      if: ${{ inputs.ANDROID == 'true' }}
-      run: pnpm build:${{ inputs.APP_ENV }}:android --non-interactive  --no-wait --message "Build  ${{ inputs.APP_ENV }} ${{ inputs.VERSION }}"
-      shell: bash
-
-    - name: 📱 Run IOS Build
-      if: ${{ inputs.IOS == 'true' }}
-      run: pnpm build:${{ inputs.APP_ENV }}:ios --non-interactive  --no-wait --message "Build ${{ inputs.APP_ENV }} ${{ inputs.VERSION }}"
-      shell: bash

package/2/.github/actions/setup-jdk-generate-apk/action.yml

@@ -1,48 +0,0 @@
-# 🔗 Links:
-# Source file: https://github.com/obytes/react-native-template-obytes/blob/master/.github/actions/setup-jdk-generate-apk/action.yml
-# Composite actions docs: https://docs.github.com/en/actions/creating-actions/creating-a-composite-action
-
-# ✍️ Description:
-# This is a composite action, which means it can be used in other actions.
-# This action is used to set up the JDK environment and generate an Android APK for testing.
-# This action accepts one input: `APP_ENV`, which is used to generate an APK for a specific environment (local, staging, production). We use staging by default.
-# Before generating the APK, we run a pre-build script to generate the necessary native folders based on the APP_ENV.
-# On success, the APK is generated at `./android/app/build/outputs/apk/release/app-release.apk`.
-
-# 👀 Example usage:
-#       - name : 📦 Set Up JDK + Generate Test APK
-#         uses: ./.github/actions/setup-jdk-generate-apk
-#         with:
-#           APP_ENV: 'staging'
-
-name: 'Setup  JDK + GRADLE + Generate APK'
-description: 'Setup  JDK + GRADLE + Generate APK'
-inputs:
-  APP_ENV:
-    description: 'APP_ENV (one of): local, staging, production'
-    required: true
-    default: 'staging'
-
-runs:
-  using: 'composite'
-  steps:
-    - name: Set Up JDK
-      uses: actions/setup-java@v3
-      with:
-        distribution: 'zulu' # See 'Supported distributions' for available options
-        java-version: '17'
-    - name: Setup Gradle
-      uses: gradle/gradle-build-action@v2
-
-    - name: Generate Test APK
-      run: |
-        pnpm prebuild:${{ inputs.APP_ENV }}
-        cd  android
-        chmod +x ./gradlew
-        ./gradlew assembleRelease --no-daemon
-        cd ..
-      shell: bash
-      env:
-        EXPO_NO_DOTENV: '1'
-        APP_ENV: ${{ inputs.APP_ENV }}
-        CI: 'true'

package/2/.github/actions/setup-node-pnpm-install/action.yml

@@ -1,29 +0,0 @@
-# 🔗 Links:
-# Source file: https://github.com/obytes/react-native-template-obytes/blob/master/.github/actions/setup-node-pnpm-install/action.yml
-# Composite actions docs: https://docs.github.com/en/actions/creating-actions/creating-a-composite-action
-
-# ✍️ Description:
-# This is a composite action, which means it can be used in other actions.
-# It is used in almost all workflows to set up the environment and install dependencies.
-# Updating  the package manager or Node version here will be reflected in all workflows.
-
-# 👀 Example usage:
-#       - name : 📦 Setup Node + PNPM + install deps
-#         uses: ./.github/actions/setup-node-pnpm-install
-
-name: 'Setup  Node + PNPM + Install Dependencies'
-description: 'Setup  Node + PNPM + Install Dependencies'
-runs:
-  using: 'composite'
-  steps:
-    - uses: pnpm/action-setup@v4
-      with:
-        run_install: false
-    - uses: actions/setup-node@v4
-      with:
-        node-version: 20
-        cache: 'pnpm'
-
-    - name: 📦 Install Project Dependencies
-      run: pnpm install --frozen-lockfile
-      shell: bash

package/2/.github/scripts/expo-doctor.sh

@@ -1,26 +0,0 @@
-#!/bin/bash
-
-# Run expo-doctor and capture output and exit code
-output=$(npx expo-doctor@latest 2>&1)
-exit_code=$?
-
-# Output file location
-output_file=".expo/expo-doctor.md"
-{
-  # Add summary based on exit code
-  if [ $exit_code -eq 0 ]; then
-    echo "✅ **Good news!** We ran Expo Doctor for this PR and everything looks good, Great job!" > "$output_file"
-  else
-    echo "❌ **Action Required:**  We ran Expo Doctor for this PR and found some issues that need to be addressed. Please review the complete report below 👇" > "$output_file"
-    echo >> "$output_file"  # Add blank line
-    echo "\`\`\`shell" >> "$output_file"
-    echo "$output" >> "$output_file"
-    echo "\`\`\`" >> "$output_file"
-  fi
-}
-
-# Show original output in terminal
-echo "$output"
-
-# Return the original exit code
-exit $exit_code