Vibecode HitKeep Cloud

You are building a lean indie version of HitKeep Cloud.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# HitKeep Cloud indie build

## Goal

Build the smallest trustworthy replacement for the core HitKeep Cloud workflow for one developer or a tiny team.

## Scope

Deploy the official HitKeep release, point a domain at it, add the tracker to your sites, and keep the data volume backed up.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- managed upgrades and monitoring
- encrypted regional backups
- managed email delivery
- vendor support and incident response

If those capabilities are essential, use HitKeep instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Replace HitKeep Cloud by deploying the real open-source HitKeep, not by rewriting analytics.
Use Docker Compose and the official pascalebeier/hitkeep image; do not build a clone.
Create compose.yml for one HitKeep service with restart: unless-stopped.
Persist the data, retention archive, and backup snapshots in separate named volumes.
Put HITKEEP_PUBLIC_URL and HITKEEP_JWT_SECRET in .env and ship a safe .env.example.
Generate the signing secret locally; never commit it or print it into documentation.
Bind HitKeep to localhost on port 8080 so my existing reverse proxy can terminate TLS.
Document the exact reverse-proxy requirements for the public analytics domain.
Enable automatic local backup snapshots and keep a bounded retention window.
Add backup.sh to copy a consistent snapshot to a second destination and document restore.
Add update.sh to pull the latest image, recreate the service, and show recent logs.
Include a health check that uses the official image's supported health-check command.
Keep optional SMTP, social login, Search Console, MCP, and AI provider settings disabled.
Do not add PostgreSQL, Redis, ClickHouse, Kafka, or a separate queue service.
Do not add accounts, billing, telemetry, or a hosted control plane around HitKeep.
Out of scope: modifying HitKeep, rebuilding its dashboard, or promising managed uptime.
Write a README covering DNS, TLS, first-owner setup, adding a site, and the tracker tag.
Document where every persistent file lives and how to test a restore before trusting backups.
Start the stack, verify the container is healthy, and confirm the dashboard and hk.js load.
Finish by listing the exact verification commands and the remaining operations I now own.

## Required capabilities

- Linux host or Docker
- domain and TLS
- persistent storage
- session signing secret
- backup and update routine

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a lean indie version of HitKeep Cloud.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# HitKeep Cloud indie build

## Goal

Build the smallest trustworthy replacement for the core HitKeep Cloud workflow for one developer or a tiny team.

## Scope

Deploy the official HitKeep release, point a domain at it, add the tracker to your sites, and keep the data volume backed up.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- managed upgrades and monitoring
- encrypted regional backups
- managed email delivery
- vendor support and incident response

If those capabilities are essential, use HitKeep instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Replace HitKeep Cloud by deploying the real open-source HitKeep, not by rewriting analytics.
Use Docker Compose and the official pascalebeier/hitkeep image; do not build a clone.
Create compose.yml for one HitKeep service with restart: unless-stopped.
Persist the data, retention archive, and backup snapshots in separate named volumes.
Put HITKEEP_PUBLIC_URL and HITKEEP_JWT_SECRET in .env and ship a safe .env.example.
Generate the signing secret locally; never commit it or print it into documentation.
Bind HitKeep to localhost on port 8080 so my existing reverse proxy can terminate TLS.
Document the exact reverse-proxy requirements for the public analytics domain.
Enable automatic local backup snapshots and keep a bounded retention window.
Add backup.sh to copy a consistent snapshot to a second destination and document restore.
Add update.sh to pull the latest image, recreate the service, and show recent logs.
Include a health check that uses the official image's supported health-check command.
Keep optional SMTP, social login, Search Console, MCP, and AI provider settings disabled.
Do not add PostgreSQL, Redis, ClickHouse, Kafka, or a separate queue service.
Do not add accounts, billing, telemetry, or a hosted control plane around HitKeep.
Out of scope: modifying HitKeep, rebuilding its dashboard, or promising managed uptime.
Write a README covering DNS, TLS, first-owner setup, adding a site, and the tracker tag.
Document where every persistent file lives and how to test a restore before trusting backups.
Start the stack, verify the container is healthy, and confirm the dashboard and hk.js load.
Finish by listing the exact verification commands and the remaining operations I now own.

## Required capabilities

- Linux host or Docker
- domain and TLS
- persistent storage
- session signing secret
- backup and update routine

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a production product version of HitKeep Cloud.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== PRODUCT.md =====
# HitKeep Cloud product brief

## Problem

The subscription is managed hosting of the same MIT-licensed application, so an agent does not need to reproduce HitKeep. It can deploy the official binary or container in one sitting; the real gap is upgrades, backups, email delivery, monitoring, and being on call for the analytics box.

## Product outcome

Deploy the official HitKeep release, point a domain at it, add the tracker to your sites, and keep the data volume backed up.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Linux host or Docker
- domain and TLS
- persistent storage
- session signing secret
- backup and update routine

## Explicit non-goals for v1

- managed upgrades and monitoring
- encrypted regional backups
- managed email delivery
- vendor support and incident response

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

===== ARCHITECTURE.md =====
# Architecture

## Starting brief

Replace HitKeep Cloud by deploying the real open-source HitKeep, not by rewriting analytics.
Use Docker Compose and the official pascalebeier/hitkeep image; do not build a clone.
Create compose.yml for one HitKeep service with restart: unless-stopped.
Persist the data, retention archive, and backup snapshots in separate named volumes.
Put HITKEEP_PUBLIC_URL and HITKEEP_JWT_SECRET in .env and ship a safe .env.example.
Generate the signing secret locally; never commit it or print it into documentation.
Bind HitKeep to localhost on port 8080 so my existing reverse proxy can terminate TLS.
Document the exact reverse-proxy requirements for the public analytics domain.
Enable automatic local backup snapshots and keep a bounded retention window.
Add backup.sh to copy a consistent snapshot to a second destination and document restore.
Add update.sh to pull the latest image, recreate the service, and show recent logs.
Include a health check that uses the official image's supported health-check command.
Keep optional SMTP, social login, Search Console, MCP, and AI provider settings disabled.
Do not add PostgreSQL, Redis, ClickHouse, Kafka, or a separate queue service.
Do not add accounts, billing, telemetry, or a hosted control plane around HitKeep.
Out of scope: modifying HitKeep, rebuilding its dashboard, or promising managed uptime.
Write a README covering DNS, TLS, first-owner setup, adding a site, and the tracker tag.
Document where every persistent file lives and how to test a restore before trusting backups.
Start the stack, verify the container is healthy, and confirm the dashboard and hk.js load.
Finish by listing the exact verification commands and the remaining operations I now own.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

===== AGENTS.md =====
# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

===== MILESTONES.md =====
# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

===== OPERATIONS.md =====
# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted HitKeep Cloud capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# HitKeep Cloud indie build

## Goal

Build the smallest trustworthy replacement for the core HitKeep Cloud workflow for one developer or a tiny team.

## Scope

Deploy the official HitKeep release, point a domain at it, add the tracker to your sites, and keep the data volume backed up.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- managed upgrades and monitoring
- encrypted regional backups
- managed email delivery
- vendor support and incident response

If those capabilities are essential, use HitKeep instead of pretending the gap is solved.

# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

# Build plan

## Original build brief

Replace HitKeep Cloud by deploying the real open-source HitKeep, not by rewriting analytics.
Use Docker Compose and the official pascalebeier/hitkeep image; do not build a clone.
Create compose.yml for one HitKeep service with restart: unless-stopped.
Persist the data, retention archive, and backup snapshots in separate named volumes.
Put HITKEEP_PUBLIC_URL and HITKEEP_JWT_SECRET in .env and ship a safe .env.example.
Generate the signing secret locally; never commit it or print it into documentation.
Bind HitKeep to localhost on port 8080 so my existing reverse proxy can terminate TLS.
Document the exact reverse-proxy requirements for the public analytics domain.
Enable automatic local backup snapshots and keep a bounded retention window.
Add backup.sh to copy a consistent snapshot to a second destination and document restore.
Add update.sh to pull the latest image, recreate the service, and show recent logs.
Include a health check that uses the official image's supported health-check command.
Keep optional SMTP, social login, Search Console, MCP, and AI provider settings disabled.
Do not add PostgreSQL, Redis, ClickHouse, Kafka, or a separate queue service.
Do not add accounts, billing, telemetry, or a hosted control plane around HitKeep.
Out of scope: modifying HitKeep, rebuilding its dashboard, or promising managed uptime.
Write a README covering DNS, TLS, first-owner setup, adding a site, and the tracker tag.
Document where every persistent file lives and how to test a restore before trusting backups.
Start the stack, verify the container is healthy, and confirm the dashboard and hk.js load.
Finish by listing the exact verification commands and the remaining operations I now own.

## Required capabilities

- Linux host or Docker
- domain and TLS
- persistent storage
- session signing secret
- backup and update routine

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

# HitKeep Cloud product brief

## Problem

The subscription is managed hosting of the same MIT-licensed application, so an agent does not need to reproduce HitKeep. It can deploy the official binary or container in one sitting; the real gap is upgrades, backups, email delivery, monitoring, and being on call for the analytics box.

## Product outcome

Deploy the official HitKeep release, point a domain at it, add the tracker to your sites, and keep the data volume backed up.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Linux host or Docker
- domain and TLS
- persistent storage
- session signing secret
- backup and update routine

## Explicit non-goals for v1

- managed upgrades and monitoring
- encrypted regional backups
- managed email delivery
- vendor support and incident response

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

# Architecture

## Starting brief

Replace HitKeep Cloud by deploying the real open-source HitKeep, not by rewriting analytics.
Use Docker Compose and the official pascalebeier/hitkeep image; do not build a clone.
Create compose.yml for one HitKeep service with restart: unless-stopped.
Persist the data, retention archive, and backup snapshots in separate named volumes.
Put HITKEEP_PUBLIC_URL and HITKEEP_JWT_SECRET in .env and ship a safe .env.example.
Generate the signing secret locally; never commit it or print it into documentation.
Bind HitKeep to localhost on port 8080 so my existing reverse proxy can terminate TLS.
Document the exact reverse-proxy requirements for the public analytics domain.
Enable automatic local backup snapshots and keep a bounded retention window.
Add backup.sh to copy a consistent snapshot to a second destination and document restore.
Add update.sh to pull the latest image, recreate the service, and show recent logs.
Include a health check that uses the official image's supported health-check command.
Keep optional SMTP, social login, Search Console, MCP, and AI provider settings disabled.
Do not add PostgreSQL, Redis, ClickHouse, Kafka, or a separate queue service.
Do not add accounts, billing, telemetry, or a hosted control plane around HitKeep.
Out of scope: modifying HitKeep, rebuilding its dashboard, or promising managed uptime.
Write a README covering DNS, TLS, first-owner setup, adding a site, and the tracker tag.
Document where every persistent file lives and how to test a restore before trusting backups.
Start the stack, verify the container is healthy, and confirm the dashboard and hk.js load.
Finish by listing the exact verification commands and the remaining operations I now own.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted HitKeep Cloud capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

$ choose a build depth, inspect the files, then open the complete pack in your agent