New docs

docs/reference-and-help/cli-reference.md

@@ -1,2 +1,26 @@
 # CLI reference
 
+## Command list
+
+```text
+dcr new <name>
+dcr init
+dcr build [--debug|--release]
+dcr run [--debug|--release]
+dcr clean [--debug|--release]
+dcr --help
+dcr --version
+dcr --update
+```
+
+## Notes on argument parsing
+
+- Most commands parse profile from the first argument.
+- `new` requires exactly one argument.
+- `init` and `--update` do not accept extra arguments.
+- `clean` accepts at most one argument.
+
+## Exit behavior overview
+
+- Successful command execution returns `0`.
+- Validation/build/runtime errors return non-zero status.

docs/reference-and-help/config-reference.md

@@ -1,2 +1,41 @@
 # Config reference
 
+## Full schema
+
+```toml
+[package]
+name = "string"      # required
+version = "string"   # required
+
+[build]
+language = "c|c++|cpp|cxx"     # required
+standard = "string"            # required
+compiler = "string"            # required
+kind = "bin|staticlib"         # required
+target = "string"              # optional
+cflags = ["string", "..."]     # optional
+ldflags = ["string", "..."]    # optional
+
+[dependencies]
+name = {
+  path = "string",              # required for each dependency
+  include = ["string", "..."],  # optional
+  lib = ["string", "..."],      # optional
+  libs = ["string", "..."],     # optional
+}
+```
+
+## Validation rules
+
+- `[package]`, `[build]`, `[dependencies]` must exist.
+- Required string fields must be non-empty.
+- `build.kind` must be `bin` or `staticlib`.
+- Dependency fields `include/lib/libs` must be string arrays when provided.
+
+## Generated defaults (`dcr new` / `dcr init`)
+
+- `package.version = "0.1.0"`
+- `build.language = "c"`
+- `build.standard = "c11"`
+- `build.compiler = "clang"`
+- `build.kind = "bin"`

docs/reference-and-help/contributing-and-bug-reports.md

@@ -1,2 +1,34 @@
 # Contributing & Bug reports
 
+## Contribution workflow
+
+1. Fork `dexoron/dcr` (and `dexoron/dcr-site` if docs website changes are needed).
+2. Make focused changes.
+3. Run checks locally:
+
+```bash
+cargo fmt --all
+cargo clippy --all-targets --all-features -- -D warnings
+cargo check
+```
+
+4. Open a PR with short rationale and behavior impact.
+5. Update docs when CLI behavior changes.
+
+## Bug report checklist
+
+Include:
+
+1. DCR version (`dcr --version`).
+2. OS and compiler/toolchain version.
+3. Reproduction steps.
+4. Expected result.
+5. Actual result and full error output.
+6. Minimal reproducible project.
+
+## Where to report
+
+Use GitHub Issues in the relevant repository:
+
+- <https://github.com/dexoron/dcr>
+- <https://github.com/dexoron/dcr-site>

docs/reference-and-help/faq.md

@@ -1,2 +1,34 @@
 # FAQ
 
+## What commands are available?
+
+`new`, `init`, `build`, `run`, `clean`, `--help`, `--version`, `--update`.
+
+## Is `dcr.toml` mandatory?
+
+Yes, for `build`, `run`, and `clean`.
+
+## What source files are compiled?
+
+DCR scans `src/` recursively:
+
+- for C: `*.c`
+- for C++: `*.cpp`, `*.cxx`, `*.cc`
+
+## Can I switch compiler?
+
+Yes. Set `build.compiler` in `dcr.toml` (for example `gcc`, `clang`, `cl`, `clang-cl`).
+
+## How does incremental rebuild work?
+
+It compares source file mtime with object file mtime. Header dependency tracking is not implemented yet.
+
+## What does `dcr run` do if build fails?
+
+It tries to run an existing binary from the selected profile; if none exists, it reports an error.
+
+## How do I update DCR?
+
+Use `dcr --update` for non-package-managed installs.
+
+If installed through pacman/AUR, update via package manager.