feat: Perform repository cleanup and hardening

[hexawulf]

Applied standardized cleanup and hardening procedure:

• Removed Replit-specific artifacts
• Deleted obsolete files (backups, old tests, temp assets)
• Ensured secrets are loaded via .env and added .env.example
• Refreshed dependencies and addressed critical vulnerabilities
• Audited and cleaned up console logging
• Reviewed shell script usage and WebSocket security (identified areas for improvement)
• Generated REPO_CLEANUP_REPORT.md summarizing changes.

Note: No automated tests were found or run as part of this process.

TAG: v1.0.0-secure

Summary by CodeRabbit

• Chores

  • Removed Replit-specific configuration files and dependencies.
  • Added an example environment variable configuration file for easier setup.
  • Upgraded and cleaned up several dependencies for improved stability and security.
  • Updated server to support configurable port via environment variable.
  • Removed obsolete backup, asset, and documentation files.
  • Commented out unnecessary debug logging throughout the application.

• Bug Fixes

  • Improved safety check for element removal during PDF export.

• Documentation

  • Deleted outdated and backup documentation files.
  • Added a comprehensive repository cleanup and security report.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update removes Replit-specific configuration and backup files, deletes test and planning documents, adds a new .env.example template for environment variables, upgrades several dependencies, and comments out debug console logs in the client code. The server is updated to use a configurable port via the PORT environment variable.

Changes

Files / Groups	Change Summary
.env.example	Added a template file listing required environment variables with instructions and placeholders for server, database, and Firebase.
.replit, README_backup.md, vite.config.ts.backup	Removed Replit environment config, backup README, and backup Vite config files.
attached_assets/*	Deleted planning, documentation, and color scheme instruction files.
client/src/components/DocumentSidebar.test.tsx,	Deleted test suites for DocumentSidebar and MoveToFolderDialog components.
client/src/components/MoveToFolderDialog.test.tsx
client/index.html	Removed Replit dev banner script and its comment.
client/src/components/DocumentSidebar.tsx,	Commented out debug console.log statements in component logic.
client/src/components/MonacoEditor.tsx,
client/src/contexts/AuthContext.tsx,
client/src/lib/importExportService.ts,	Commented out all logging; added a minor safety check during PDF export error handling.
client/src/pages/Landing.tsx	Commented out a redirect-related console log.
package.json	Upgraded firebase-admin, drizzle-kit, vite; removed Replit-specific devDependencies.
server/index.ts	Server now reads port from PORT environment variable, defaulting to 5004 if unset.
REPO_CLEANUP_REPORT.md	Added a detailed report documenting the cleanup, dependency updates, and outstanding security and configuration concerns.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Server
    Note over Server: On startup
    Server->Server: Read PORT from environment
    alt PORT set
        Server->Server: Use PORT value
    else
        Server->Server: Use default port 5004
    end
    User->Server: Connects to server at configured port

Loading

Possibly related PRs

• hexawulf/MarkdownMate#2: Adds dotenv/config import to server/index.ts for loading environment variables, directly related to the .env.example addition and server port configuration.
• hexawulf/MarkdownMate#17: Introduces the redirect logic in client/src/pages/Landing.tsx; this PR comments out the console log in that same redirect logic.

Poem

A rabbit hopped through files so neat,
Swept away old configs and obsolete,
With .env.example now clear and bright,
And debug logs tucked out of sight.
Ports now dance to env’s sweet tune,
This repo’s ready—spring cleaned by June!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d3bf02e and b532633.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (18)

• .env.example (1 hunks)
• .replit (0 hunks)
• README_backup.md (0 hunks)
• REPO_CLEANUP_REPORT.md (1 hunks)
• attached_assets/Pasted--Create-Complete-Project-Documentation-GitHub-Deployment-Create-a-comprehensive-README-md-file-f-1749250243290.txt (0 hunks)
• attached_assets/Pasted--MarkdownMate-Production-Ready-Collaborative-Markdown-Editor-Create-a-fully-featured-real-time--1749198165674.txt (0 hunks)
• attached_assets/Pasted-Please-update-the-MarkdownMate-application-to-use-a-GitHub-inspired-color-scheme-that-s-more-profess-1749199814106.txt (0 hunks)
• client/index.html (0 hunks)
• client/src/components/DocumentSidebar.test.tsx (0 hunks)
• client/src/components/DocumentSidebar.tsx (2 hunks)
• client/src/components/MonacoEditor.tsx (5 hunks)
• client/src/components/MoveToFolderDialog.test.tsx (0 hunks)
• client/src/contexts/AuthContext.tsx (1 hunks)
• client/src/lib/importExportService.ts (17 hunks)
• client/src/pages/Landing.tsx (1 hunks)
• package.json (2 hunks)
• server/index.ts (1 hunks)
• vite.config.ts.backup (0 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.