chore: make project OSS-friendly (license, CI, layout, source rename)

- Add MIT LICENSE, CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, CHANGELOG.md.
- Add .editorconfig and .clang-format (extracted from the .vscode style pref).
- Add CI workflow building on Ubuntu + macOS plus a curl smoke test,
  GitHub issue templates, and a PR template.
- Move conf/grammar.md  -> docs/grammar.md.
- Move conf/servio.conf -> examples/servio.conf, add examples/minimal.conf
  (non-privileged port; used by CI).
- Add docs/architecture.md describing the module tour and request lifecycle.
- Rewrite README with badges, quick start, directive cheatsheet, layout map.
- Rewrite Makefile: wildcard source discovery, build/ tree, MODE=
  asan/debug/release, install/uninstall, dependency files via -MMD -MP.
- Drop the redundant sio_ filename prefix throughout src/ (the directory
  already namespaces files). A few files renamed for clarity:
    http_codes   -> status_codes
    http_range   -> range
    request_body -> body
    cmdline_opts -> options
    servio       -> server     (top-level core module)
- Rename the static sio_sendfile helper to sendfileTo for consistency.
- Update the CLI -h text (was advertising the wrong default config path).
- Untrack runtime log placeholders (logs/*.log), add logs/.gitkeep.
- Broaden .gitignore (.vscode/, .idea/, .dSYM/, build/, OS files).

Author: awbx

.clang-format

@@ -0,0 +1,19 @@
+---
+BasedOnStyle: Google
+Standard: c++03
+IndentWidth: 4
+TabWidth: 4
+UseTab: ForIndentation
+IndentCaseLabels: false
+AlignConsecutiveDeclarations: true
+ColumnLimit: 0
+AllowShortFunctionsOnASingleLine: Inline
+AllowShortIfStatementsOnASingleLine: false
+AllowShortLoopsOnASingleLine: false
+PointerAlignment: Right
+SortIncludes: false
+SpaceAfterCStyleCast: false
+SpaceBeforeParens: ControlStatements
+BreakBeforeBraces: Attach
+NamespaceIndentation: None
+...

.editorconfig

@@ -0,0 +1,22 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.{cpp,hpp,tpp,c,h}]
+indent_style = tab
+indent_size = 4
+
+[Makefile]
+indent_style = tab
+
+[*.{md,yml,yaml,json}]
+indent_style = space
+indent_size = 2
+
+[*.conf]
+indent_style = space
+indent_size = 4

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Report something that is not working as expected
+labels: bug
+---
+
+## Description
+
+A clear, concise description of what the bug is.
+
+## Steps to reproduce
+
+1. Run `./servio -c ...`
+2. Issue request `curl ...`
+3. Observe `<actual behavior>`
+
+## Expected behavior
+
+What you expected to happen instead.
+
+## Environment
+
+- OS / version (e.g. Ubuntu 22.04, macOS 14.4)
+- Compiler / version (`c++ --version`)
+- ServIO commit (`git rev-parse HEAD`)
+- Build flags (default debug+ASan? `make release`? other?)
+
+## Relevant configuration
+
+```nginx
+# paste the smallest config snippet that reproduces the issue
+```
+
+## Logs / output
+
+```
+# server stderr, curl -v output, ASan/UBSan reports, etc.
+```

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security report
+    url: https://github.com/BlaanTeam/serv-io/security/advisories/new
+    about: Please report security vulnerabilities privately, not as a public issue.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,29 @@
+---
+name: Feature request
+about: Suggest a new directive, protocol feature, or improvement
+labels: enhancement
+---
+
+## Summary
+
+One or two sentences describing the feature.
+
+## Motivation / use case
+
+What are you trying to do? What's the workflow that this feature would
+enable or simplify?
+
+## Proposed behavior
+
+How would the feature work end-to-end? If it adds a new configuration
+directive, sketch the syntax and where it would live (HTTP / server /
+location block).
+
+## Prior art
+
+NGINX (or another server) directive name, RFC section, or related projects —
+anything that helps establish the expected semantics.
+
+## Alternatives considered
+
+What workarounds are available today, and why are they insufficient?

.github/pull_request_template.md

@@ -0,0 +1,22 @@
+## Summary
+
+<!-- 1-3 bullet points describing what changes and why. -->
+
+## Test plan
+
+<!--
+- [ ] `make re` succeeds (debug + ASan)
+- [ ] `make release` succeeds
+- [ ] `./servio -t -c examples/servio.conf` reports success
+- [ ] Smoke check: GET, range, upload all behave as expected
+-->
+
+## Checklist
+
+- [ ] Branched off the right base (`master` for stable, `v2` for the active
+      development branch)
+- [ ] Commit messages follow Conventional Commits (`feat:`, `fix:`,
+      `refactor:`, `chore:`, `docs:`)
+- [ ] `make format` was run (no whitespace-only churn introduced)
+- [ ] No `Co-Authored-By` trailer for AI assistants
+- [ ] CI is green

.github/workflows/ci.yml

@@ -0,0 +1,48 @@
+name: ci
+
+on:
+  push:
+    branches: [master, v2]
+  pull_request:
+    branches: [master, v2]
+
+jobs:
+  build:
+    name: build (${{ matrix.os }})
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install Linux build deps
+        if: runner.os == 'Linux'
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y build-essential
+
+      - name: Build (debug + ASan)
+        run: make -j$(getconf _NPROCESSORS_ONLN)
+
+      - name: Syntax-check example config
+        run: ./servio -t -c examples/minimal.conf
+
+      - name: Smoke test (background server + curl)
+        run: |
+          ./servio -c examples/minimal.conf &
+          SERVIO_PID=$!
+          sleep 1
+          set -e
+          curl -sS -o /tmp/index.html  -w "GET / -> %{http_code}\n"          http://localhost:8081/        | grep -q 200
+          curl -sS -o /tmp/range.bin   -H "Range: bytes=0-99"                http://localhost:8081/        | true
+          echo "hello-ci" > /tmp/ci.txt
+          curl -sS -F file=@/tmp/ci.txt http://localhost:8081/upload | grep -qi "201\|Upload"
+          kill $SERVIO_PID || true
+
+      - name: Build (release)
+        run: |
+          make fclean
+          make release

.gitignore

@@ -1,46 +1,38 @@
-# Created by https://www.toptal.com/developers/gitignore/api/c++
-# Edit at https://www.toptal.com/developers/gitignore?templates=c++
-
-### C++ ###
-# Prerequisites
+# Compiled output
 *.d
-
-# Compiled Object files
-*.slo
-*.lo
 *.o
 *.obj
-
-# Precompiled Headers
 *.gch
 *.pch
-
-# Compiled Dynamic libraries
 *.so
 *.dylib
 *.dll
-
-# Fortran module files
-*.mod
-*.smod
-
-# Compiled Static libraries
-*.lai
-*.la
 *.a
 *.lib
-
-# Executables
+*.lai
+*.la
 *.exe
 *.out
 *.app
+*.dSYM/
 servio
 
-# End of https://www.toptal.com/developers/gitignore/api/c++
+# Build directories
+build/
 
-# ignore prefixed files with ign_*
-ign_*
+# Editor / IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+
+# OS
+.DS_Store
+Thumbs.db
 
+# Logs (runtime-generated)
+logs/*.log
 
-# ignore the html folder
-html/*
+# Project convention: ignore prefixed scratch files
+ign_*

CHANGELOG.md

@@ -0,0 +1,50 @@
+# Changelog
+
+All notable changes to ServIO are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and the project tries to follow [Semantic Versioning](https://semver.org/).
+
+## [Unreleased] — v2 branch
+
+### Added
+- `StreamSearch` — a streamsearch-inspired needle scanner used to find
+  multipart boundaries across `recv()` chunks without per-byte stream reads.
+- `sendfile(2)` path for static file responses (Darwin + Linux, with a
+  `pread + send` fallback for other platforms). Range responses pass the
+  kernel an offset directly.
+- OSS scaffolding: `LICENSE` (MIT), `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`,
+  `SECURITY.md`, `CHANGELOG.md`, `.editorconfig`, `.clang-format`,
+  GitHub issue and pull request templates, CI workflow.
+- `docs/architecture.md` and `docs/grammar.md` (moved from `conf/`).
+- `examples/servio.conf` (sample configuration).
+
+### Changed
+- Request parser is now `(const char*, size_t)`-driven instead of being fed
+  from a `queue<stringstream*>`. The first-line and header parsers are a
+  small byte-oriented state machine with length-bounded URI and header
+  lines and CRLF/LF tolerance.
+- Body parsers (lengthed / chunked / multipart) share a single
+  bytes-consumed contract. Multipart writes part data straight from the
+  recv buffer to per-part tmp files.
+- `recv()` buffer bumped from 1 KiB to 16 KiB.
+- Source files dropped the redundant `sio_` prefix (the directory already
+  namespaces them); a handful were renamed for clarity
+  (`http_codes` → `status_codes`, `request_body` → `body`,
+  `cmdline_opts` → `options`, `utils` → `time_utils`,
+  `servio.cpp` → `server.cpp`).
+- Build artifacts now land in `build/` instead of polluting `src/`.
+
+### Fixed
+- Replaced the deprecated `sprintf` in `Content-Range` formatting with
+  `snprintf`, restoring the `-Werror` build on recent toolchains.
+- Self-referential `Body`/`Request` state no longer dangles when these
+  objects are copied through `ClientMap` (`Body` is now its own
+  `StreamSearch::Sink`).
+
+## [1.0.0] — initial release
+
+- HTTP/1.1 server inspired by NGINX configuration syntax.
+- Static file serving, CGI, file uploads, redirects, virtual hosts, range
+  requests, directory listings, custom error pages.
+- `poll(2)`-driven non-blocking I/O.

CODE_OF_CONDUCT.md

@@ -0,0 +1,47 @@
+# Contributor Covenant Code of Conduct
+
+## Our pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic
+status, nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our standards
+
+Examples of behavior that contributes to a positive environment:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior:
+
+- The use of sexualized language or imagery, and sexual attention or advances
+- Trolling, insulting or derogatory comments, and personal or political
+  attacks
+- Public or private harassment
+- Publishing others' private information without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the maintainers at the email address listed in the project's
+GitHub profile. All complaints will be reviewed and investigated promptly and
+fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the
+[Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).