@pixelbyte-software/pixcode 1.54.10 → 1.55.0

package/CODE_OF_CONDUCT.md

@@ -1,41 +1,41 @@
-# Code of Conduct
-
-## Our Pledge
-
-Pixcode is an open-source project for developers who want a practical,
-self-hosted workspace for AI coding agents. We want discussion, issues, reviews,
-and contributions to stay useful, respectful, and focused on improving the
-project.
-
-## Expected Behavior
-
-- Be respectful when discussing bugs, design choices, and tradeoffs.
-- Assume good intent, but be concrete when something is wrong.
-- Keep issues actionable: include reproduction steps, logs, screenshots, or
-  environment details when possible.
-- Respect maintainers' time by keeping pull requests scoped.
-- Avoid sharing private tokens, project paths, customer data, or provider
-  credentials in public threads.
-
-## Unacceptable Behavior
-
-- Harassment, personal attacks, slurs, threats, or targeted abuse.
-- Publishing another person's private information without permission.
-- Repeated off-topic comments that derail issue or pull request discussion.
-- Posting secrets, malware, exploit payloads, or harmful instructions unrelated
-  to a responsible security report.
-- Any behavior that makes the project unsafe for contributors or users.
-
-## Reporting
-
-If you see conduct problems, report them through GitHub by contacting the
-repository maintainers or opening a private security/advisory channel when the
-problem includes sensitive information.
-
-Maintainers may remove comments, close issues, block users, or take other
-reasonable actions to keep the project healthy.
-
-## Scope
-
-This code of conduct applies to the Pixcode repository, issue tracker, pull
-requests, discussions, release threads, and other project-managed spaces.
+# Code of Conduct
+
+## Our Pledge
+
+Pixcode is an open-source project for developers who want a practical,
+self-hosted workspace for AI coding agents. We want discussion, issues, reviews,
+and contributions to stay useful, respectful, and focused on improving the
+project.
+
+## Expected Behavior
+
+- Be respectful when discussing bugs, design choices, and tradeoffs.
+- Assume good intent, but be concrete when something is wrong.
+- Keep issues actionable: include reproduction steps, logs, screenshots, or
+  environment details when possible.
+- Respect maintainers' time by keeping pull requests scoped.
+- Avoid sharing private tokens, project paths, customer data, or provider
+  credentials in public threads.
+
+## Unacceptable Behavior
+
+- Harassment, personal attacks, slurs, threats, or targeted abuse.
+- Publishing another person's private information without permission.
+- Repeated off-topic comments that derail issue or pull request discussion.
+- Posting secrets, malware, exploit payloads, or harmful instructions unrelated
+  to a responsible security report.
+- Any behavior that makes the project unsafe for contributors or users.
+
+## Reporting
+
+If you see conduct problems, report them through GitHub by contacting the
+repository maintainers or opening a private security/advisory channel when the
+problem includes sensitive information.
+
+Maintainers may remove comments, close issues, block users, or take other
+reasonable actions to keep the project healthy.
+
+## Scope
+
+This code of conduct applies to the Pixcode repository, issue tracker, pull
+requests, discussions, release threads, and other project-managed spaces.

package/CONTRIBUTING.md

@@ -1,156 +1,156 @@
-# Contributing to Pixcode
-
-Thanks for your interest in contributing to Pixcode! Before you start, please take a moment to read through this guide.
-
-## Before You Start
-
-- **Search first.** Check [existing issues](https://github.com/alicomert/pixcode/issues) and [pull requests](https://github.com/alicomert/pixcode/pulls) to avoid duplicating work.
-- **Discuss first** for new features. Open an [issue](https://github.com/alicomert/pixcode/issues/new) to discuss your idea before investing time in implementation. We may already have plans or opinions on how it should work.
-- **Bug fixes are always welcome.** If you spot a bug, feel free to open a PR directly.
-
-## Prerequisites
-
-- [Node.js](https://nodejs.org/) 22 or later
-- [Claude Code CLI](https://docs.anthropic.com/en/docs/claude-code) installed and configured
-
-## Getting Started
-
-1. Fork the repository
-2. Clone your fork:
-   ```bash
-   git clone https://github.com/<your-username>/pixcode.git
-   cd pixcode
-   ```
-3. Install dependencies:
-   ```bash
-   npm install
-   ```
-4. Start the development server:
-   ```bash
-   npm run dev
-   ```
-5. Create a branch for your changes:
-   ```bash
-   git checkout -b feat/your-feature-name
-   ```
-
-## Project Structure
-
-```
-pixcode/
-├── src/              # React frontend (Vite + Tailwind)
-│   ├── components/   # UI components
-│   ├── contexts/     # React context providers
-│   ├── hooks/        # Custom React hooks
-│   ├── i18n/         # Internationalization and translations
-│   ├── lib/          # Shared frontend libraries
-│   ├── types/        # TypeScript type definitions
-│   └── utils/        # Frontend utilities
-├── server/           # Express backend
-│   ├── routes/       # API route handlers
-│   ├── middleware/    # Express middleware
-│   ├── database/     # SQLite database layer
-│   └── tools/        # CLI tool integrations
-├── shared/           # Code shared between client and server
-└── public/           # Static assets, icons, PWA manifest
-```
-
-## Development Workflow
-
-- `npm run dev` — Start both the frontend and backend in development mode
-- `npm run build` — Create a production build
-- `npm run server` — Start only the backend server
-- `npm run client` — Start only the Vite dev server
-
-## Making Changes
-
-### Bug Fixes
-
-- Reference the issue number in your PR if one exists
-- Describe how to reproduce the bug in your PR description
-- Add a screenshot or recording for visual bugs
-
-### New Features
-
-- Keep the scope focused — one feature per PR
-- Include screenshots or recordings for UI changes
-
-### Documentation
-
-- Documentation improvements are always welcome
-- Keep language clear and concise
-
-## Commit Convention
-
-We follow [Conventional Commits](https://conventionalcommits.org/) to generate release notes automatically. Every commit message should follow this format:
-
-```
-<type>(optional scope): <description>
-```
-
-Use imperative, present tense: "add feature" not "added feature" or "adds feature".
-
-### Types
-
-| Type | Description |
-|------|-------------|
-| `feat` | A new feature |
-| `fix` | A bug fix |
-| `perf` | A performance improvement |
-| `refactor` | Code change that neither fixes a bug nor adds a feature |
-| `docs` | Documentation only |
-| `style` | CSS, formatting, visual changes |
-| `chore` | Maintenance, dependencies, config |
-| `ci` | CI/CD pipeline changes |
-| `test` | Adding or updating tests |
-| `build` | Build system changes |
-
-### Examples
-
-```bash
-feat: add conversation search
-feat(i18n): add Japanese language support
-fix: redirect unauthenticated users to login
-fix(editor): syntax highlighting for .env files
-perf: lazy load code editor component
-refactor(chat): extract message list component
-docs: update API configuration guide
-```
-
-### Breaking Changes
-
-Add `!` after the type or include `BREAKING CHANGE:` in the commit footer:
-
-```bash
-feat!: redesign settings page layout
-```
-
-## Pull Requests
-
-- Give your PR a clear, descriptive title following the commit convention above
-- Fill in the PR description with what changed and why
-- Link any related issues
-- Include screenshots for UI changes
-- Make sure the build passes (`npm run build`)
-- Keep PRs focused — avoid unrelated changes
-
-## Releases
-
-Releases are managed by maintainers using [release-it](https://github.com/release-it/release-it) with the [conventional changelog plugin](https://github.com/release-it/conventional-changelog).
-
-```bash
-npm run release           # interactive (prompts for version bump)
-npm run release -- patch  # patch release
-npm run release -- minor  # minor release
-```
-
-This automatically:
-- Bumps the version based on commit types (`feat` = minor, `fix` = patch)
-- Generates categorized release notes
-- Updates `CHANGELOG.md`
-- Creates a git tag and GitHub Release
-- Publishes to npm
-
-## License
-
-By contributing, you agree that your contributions will be licensed under the [AGPL-3.0-or-later License](LICENSE), including the additional terms specified in Section 7 of the LICENSE file.
+# Contributing to Pixcode
+
+Thanks for your interest in contributing to Pixcode! Before you start, please take a moment to read through this guide.
+
+## Before You Start
+
+- **Search first.** Check [existing issues](https://github.com/alicomert/pixcode/issues) and [pull requests](https://github.com/alicomert/pixcode/pulls) to avoid duplicating work.
+- **Discuss first** for new features. Open an [issue](https://github.com/alicomert/pixcode/issues/new) to discuss your idea before investing time in implementation. We may already have plans or opinions on how it should work.
+- **Bug fixes are always welcome.** If you spot a bug, feel free to open a PR directly.
+
+## Prerequisites
+
+- [Node.js](https://nodejs.org/) 22 or later
+- [Claude Code CLI](https://docs.anthropic.com/en/docs/claude-code) installed and configured
+
+## Getting Started
+
+1. Fork the repository
+2. Clone your fork:
+   ```bash
+   git clone https://github.com/<your-username>/pixcode.git
+   cd pixcode
+   ```
+3. Install dependencies:
+   ```bash
+   npm install
+   ```
+4. Start the development server:
+   ```bash
+   npm run dev
+   ```
+5. Create a branch for your changes:
+   ```bash
+   git checkout -b feat/your-feature-name
+   ```
+
+## Project Structure
+
+```
+pixcode/
+├── src/              # React frontend (Vite + Tailwind)
+│   ├── components/   # UI components
+│   ├── contexts/     # React context providers
+│   ├── hooks/        # Custom React hooks
+│   ├── i18n/         # Internationalization and translations
+│   ├── lib/          # Shared frontend libraries
+│   ├── types/        # TypeScript type definitions
+│   └── utils/        # Frontend utilities
+├── server/           # Express backend
+│   ├── routes/       # API route handlers
+│   ├── middleware/    # Express middleware
+│   ├── database/     # SQLite database layer
+│   └── tools/        # CLI tool integrations
+├── shared/           # Code shared between client and server
+└── public/           # Static assets, icons, PWA manifest
+```
+
+## Development Workflow
+
+- `npm run dev` — Start both the frontend and backend in development mode
+- `npm run build` — Create a production build
+- `npm run server` — Start only the backend server
+- `npm run client` — Start only the Vite dev server
+
+## Making Changes
+
+### Bug Fixes
+
+- Reference the issue number in your PR if one exists
+- Describe how to reproduce the bug in your PR description
+- Add a screenshot or recording for visual bugs
+
+### New Features
+
+- Keep the scope focused — one feature per PR
+- Include screenshots or recordings for UI changes
+
+### Documentation
+
+- Documentation improvements are always welcome
+- Keep language clear and concise
+
+## Commit Convention
+
+We follow [Conventional Commits](https://conventionalcommits.org/) to generate release notes automatically. Every commit message should follow this format:
+
+```
+<type>(optional scope): <description>
+```
+
+Use imperative, present tense: "add feature" not "added feature" or "adds feature".
+
+### Types
+
+| Type | Description |
+|------|-------------|
+| `feat` | A new feature |
+| `fix` | A bug fix |
+| `perf` | A performance improvement |
+| `refactor` | Code change that neither fixes a bug nor adds a feature |
+| `docs` | Documentation only |
+| `style` | CSS, formatting, visual changes |
+| `chore` | Maintenance, dependencies, config |
+| `ci` | CI/CD pipeline changes |
+| `test` | Adding or updating tests |
+| `build` | Build system changes |
+
+### Examples
+
+```bash
+feat: add conversation search
+feat(i18n): add Japanese language support
+fix: redirect unauthenticated users to login
+fix(editor): syntax highlighting for .env files
+perf: lazy load code editor component
+refactor(chat): extract message list component
+docs: update API configuration guide
+```
+
+### Breaking Changes
+
+Add `!` after the type or include `BREAKING CHANGE:` in the commit footer:
+
+```bash
+feat!: redesign settings page layout
+```
+
+## Pull Requests
+
+- Give your PR a clear, descriptive title following the commit convention above
+- Fill in the PR description with what changed and why
+- Link any related issues
+- Include screenshots for UI changes
+- Make sure the build passes (`npm run build`)
+- Keep PRs focused — avoid unrelated changes
+
+## Releases
+
+Releases are managed by maintainers using [release-it](https://github.com/release-it/release-it) with the [conventional changelog plugin](https://github.com/release-it/conventional-changelog).
+
+```bash
+npm run release           # interactive (prompts for version bump)
+npm run release -- patch  # patch release
+npm run release -- minor  # minor release
+```
+
+This automatically:
+- Bumps the version based on commit types (`feat` = minor, `fix` = patch)
+- Generates categorized release notes
+- Updates `CHANGELOG.md`
+- Creates a git tag and GitHub Release
+- Publishes to npm
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE).