Added a tiny test to cover banned user behavior

Author: daitangio

CODESPACES_EXTRA_TIPS.md

@@ -0,0 +1,8 @@
+# Codespaces
+
+> sudo apt-get install -y libvips
+> rvm install 3.4.5
+
+# MacOS
+
+Install rvm locally with single user install into https://rvm.io/rvm/install

EXTRA_TIPS.md

@@ -0,0 +1,36 @@
+# Campfire Architecture Overview
+Note: ChatGPT Codex autogenerated with edits
+
+## Rails stack
+- Campfire is a Rails application loaded from `config/application.rb`, running against the main Rails branch with Puma as the Rack server (`Gemfile`).
+- The Process model defined in `Procfile` runs a web process (`thrust bin/start-app`), a Redis instance, and a Resque worker pool, mirroring the production topology.
+
+## Server components
+### HTTP layer & concerns
+- Routes in `config/routes.rb` expose REST-style resources for accounts, rooms, messages, searches, and user onboarding, with controller logic under `app/controllers`.
+- `ApplicationController` wires in shared concerns for authentication, authorization, request context, and Turbo support (`app/controllers/application_controller.rb`), while scoped controllers (e.g. `accounts`, `rooms`, `sessions`) encapsulate feature-specific flows.
+
+### Domain models
+- Active Record models under `app/models` capture the chat domain: `Room` orchestrates membership grants and message fan-out, `Message` stores Action Text content and triggers broadcasts, and `Membership` tracks unread state and presence (`app/models/room.rb`, `app/models/message.rb`, `app/models/membership.rb`).
+- Users own push subscriptions, webhook endpoints, and other associations (`app/models/user.rb`, `app/models/user/bot.rb`), enabling bots and notifications with minimal coupling.
+
+### Real-time delivery
+- Turbo Streams allow immediate updates when messages post, via `Message::Broadcasts` (`app/models/message/broadcasts.rb`).
+- Action Cable channels handle live room traffic, typing state, presence, and heartbeat pings (`app/channels/**/*`). `RoomChannel` scopes streams to authorized users, while `PresenceChannel` updates connection counters and fires read receipts.
+
+### Background jobs & integrations
+- Active Job dispatches asynchronous work; production runs jobs through Resque (`config/environments/production.rb`). Examples include `Room::PushMessageJob` (web push fan-out) and `Bot::WebhookJob` (outbound bot integrations) under `app/jobs`.
+- Web push delivery is handled by a dedicated thread pool (`lib/web_push/pool.rb`), which coalesces HTTP connections and asynchronously invalidates expired subscriptions.
+- The PWA surface is served through `PwaController` and the custom service worker script in `app/views/pwa/service_worker.js` to manage push notifications and badge counts.
+
+## Redis-backed storage
+- Action Cable uses Redis for its pub/sub adapter (`config/cable.yml`), enabling multi-process fan-out of channel traffic and presence updates.
+- Resque persists job queues and worker state in Redis; the pool is configured via `config/resque-pool.yml`, and each worker reconnects to Postgres while closing Redis connections before forking (`lib/tasks/resque.rake`).
+- Rails caching switches to `:redis_cache_store` in production (and when dev caching is enabled), so fragment and view caches are stored alongside queue data (`config/environments/production.rb`, `config/environments/development.rb`).
+- Local development optionally launches a bundled Redis server through `Procfile` and `bin/setup` if one is not already running, keeping all Redis-backed concerns co-located.
+
+## VAPID keys and push delivery
+- VAPID keys are loaded at boot from credentials or environment variables into `Rails.configuration.x.vapid` (`config/initializers/vapid.rb`).
+- The layout exposes the public key through a `<meta>` tag (`app/views/layouts/application.html.erb`), so the Stimulus notifications controller can subscribe the service worker with the proper `applicationServerKey` (`app/javascript/controllers/notifications_controller.js`).
+- When a message arrives, `Room::MessagePusher` builds payloads for relevant subscribers and queues them on the shared `WebPush::Pool`, which signs each request using the configured VAPID credentials (`app/models/room/message_pusher.rb`, `lib/web_push/notification.rb`).
+- Administrators can mint or rotate key pairs with `script/admin/create-vapid-key`, which shells into the Rails environment and prints the new values for storage in credentials or environment.

doc/OVERVIEW.md

@@ -0,0 +1,17 @@
+require "test_helper"
+
+class BanEditingTest < ActionDispatch::IntegrationTest 
+  setup do
+    sign_in :banner
+  end
+
+  test "edit" do
+    assert users(:banner).member?
+    assert users(:banner).ban?
+
+    get edit_account_url
+    # if you are banned, you cannot get there
+    assert_response :forbidden
+    
+  end
+end    

test/controllers/accounts_controller_ban_test.rb

@@ -28,3 +28,10 @@ bender:
   name: Bender Bot
   bot_token: <%= User.generate_bot_token %>
   role: bot
+
+banner:
+  name: Bruce Banner
+  email_address: bruce@banner.com
+  password_digest: <%= password_digest %>
+  bio: A banned user
+  ban: true