chore: simplify to single-branch workflow (main only)

Removed development branch — unnecessary for solo/small team.
Release strategy now based on tag type, not branch:
- Pre-release tag (v0.4.0-rc1) → TestPyPI
- Stable tag (v0.4.0) → PyPI

Changes:
- Deleted development branch (remote + local)
- CI triggers: main only (was main + development)
- CONTRIBUTING: PR target back to main, simplified flow
- PR template: removed development branch note
- QMS: PR target back to main

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: cemililik

.github/pull_request_template.md

@@ -1,5 +1,3 @@
-> **Target branch:** Please open PRs against `development`. Only release PRs target `main`.
-
 ## Summary
 
 <!-- What does this PR do? One sentence. -->

.github/workflows/ci.yml

@@ -2,9 +2,9 @@ name: CI
 
 on:
   push:
-    branches: [main, development]
+    branches: [main]
   pull_request:
-    branches: [main, development]
+    branches: [main]
 
 jobs:
   # --- Job 1: Lint (fast, no heavy deps) ---

CONTRIBUTING.md

@@ -29,19 +29,12 @@ python3 -m pip install -e ".[dev]"
 
 ### 3. Create a branch
 
-Always branch from `development`:
-
 ```bash
 git fetch upstream
-git checkout -b feat/my-feature upstream/development
+git checkout -b feat/my-feature upstream/main
 ```
 
-Branch naming convention:
-- `feat/description` — new feature
-- `fix/description` — bug fix
-- `docs/description` — documentation
-- `test/description` — test coverage
-- `chore/description` — CI, deps, tooling
+Branch naming: `feat/`, `fix/`, `docs/`, `test/`, `chore/` + short description.
 
 ### 4. Make your changes
 
@@ -60,13 +53,7 @@ forgelm --config config_template.yaml --dry-run
 
 ### 5. Submit a PR
 
-Push your branch and open a Pull Request against **`development`**.
-
-```
-feature/* ──PR──→ development ──PR──→ main (release only)
-```
-
-> `main` is protected and only receives release PRs from `development`.
+Push your branch and open a Pull Request against `main`.
 
 ## Development Setup
 

docs/qms/sop_change_management.md

@@ -19,14 +19,14 @@ Define the procedure for managing changes to fine-tuned models, training configu
 
 ### 3.1 Propose
 
-1. Create a branch from `development`: `git checkout -b change/description development`
+1. Create a branch: `git checkout -b change/description`
 2. Modify the training config (YAML)
 3. Document the change rationale in the PR description
 4. Run dry-run: `forgelm --config new_config.yaml --dry-run`
 
 ### 3.2 Review
 
-1. Open a Pull Request against `development` (release PRs go to `main`)
+1. Open a Pull Request against `main`
 2. PR must include:
    - [ ] Config diff showing what changed
    - [ ] Rationale for the change