Community presence: README, oasis vision, CI, tags checklist

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,26 @@
+---
+name: Bug report
+about: Something broken in the runtime, store, policy, or API
+title: "[bug] "
+labels: bug
+---
+
+## What happened
+
+## What you expected
+
+## Repro
+
+```bash
+cargo run -p agentos-cli -- ...
+```
+
+## Environment
+
+- OS:
+- `rustc --version`:
+- AgentOS commit / tag:
+
+## Journal / logs
+
+Paste relevant journal event types or errors (redact secrets).

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Vision & oasis movement
+    url: https://github.com/new-world-coder/agentos/blob/main/VISION.md
+    about: Why AgentOS exists and how we grow as a community
+  - name: Good first issues guide
+    url: https://github.com/new-world-coder/agentos/blob/main/docs/GOOD_FIRST_ISSUES.md
+    about: Starter tasks before you open a large PR
+  - name: Lifecycle (honest phases)
+    url: https://github.com/new-world-coder/agentos/blob/main/LIFECYCLE.md
+    about: What is done vs not claimed yet

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,16 @@
+---
+name: Feature request
+about: Propose work aligned with LIFECYCLE.md
+title: "[feat] "
+labels: enhancement
+---
+
+## Problem
+
+## Proposal
+
+## Lifecycle phase
+
+Which phase does this belong to? (0–4) Link exit criteria if extending them.
+
+## Alternatives considered

.github/ISSUE_TEMPLATE/good_first_issue.md

@@ -0,0 +1,20 @@
+---
+name: Good first issue
+about: Mentored starter task for new contributors
+title: "[good first] "
+labels: good first issue, help wanted
+---
+
+## Task
+
+## Why it’s a good first issue
+
+## Acceptance criteria
+
+- [ ]
+- [ ]
+- [ ] `cargo test --workspace` and clippy `-D warnings` pass
+
+## Mentorship notes
+
+Point to crates/files to touch. Link [docs/GOOD_FIRST_ISSUES.md](../../docs/GOOD_FIRST_ISSUES.md).

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,14 @@
+## Summary
+
+## Lifecycle / ADR impact
+
+- [ ] No phase claim change
+- [ ] Updates LIFECYCLE.md / ADR (linked)
+
+## Test plan
+
+- [ ] `cargo test --workspace`
+- [ ] `cargo clippy --workspace --all-targets -- -D warnings`
+- [ ] (if runtime/store) crash-resume or journal verify covered
+
+## Notes

.github/repository-meta.md

@@ -0,0 +1,43 @@
+# Repository About metadata
+
+GitHub Apps used by cloud agents often **cannot** PATCH description/topics (403).
+A maintainer should copy this into the GitHub UI once.
+
+## Settings → General → About
+
+**Description** (short):
+
+```text
+Durable Rust agent runtime: hash-chained effect journal, policy-before-effect, HITL, crash-resume. Apache-2.0 oasis for auditable agents.
+```
+
+**Website** (optional):
+
+```text
+https://github.com/new-world-coder/agentos
+```
+
+**Topics** (add as tags):
+
+```text
+rust
+agents
+ai-agents
+llm
+agent-runtime
+durable-execution
+crash-recovery
+sqlite
+axum
+hitl
+policy-engine
+apache-2
+open-source
+```
+
+Check: ☑ Issues · ☑ Preserve this repository | Discussions (optional, recommended later)
+
+## Releases
+
+Tags `v0.1.0` (Phase 0) and `v0.2.0` (Phase 1) should appear under **Releases**.
+If a tag exists without a Release, click **Draft a release** → choose the tag → publish using notes in `docs/RELEASE_NOTES.md`.

.github/workflows/ci.yml

@@ -0,0 +1,38 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+env:
+  CARGO_TERM_COLOR: always
+  RUSTFLAGS: -D warnings
+
+jobs:
+  test:
+    name: test + clippy
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install Rust toolchain
+        uses: dtolnay/rust-toolchain@master
+        with:
+          toolchain: "1.85.0"
+          components: clippy, rustfmt
+
+      - uses: Swatinem/rust-cache@v2
+
+      - name: fmt
+        run: cargo fmt --all -- --check
+
+      - name: clippy
+        run: cargo clippy --workspace --all-targets -- -D warnings
+
+      - name: test
+        run: cargo test --workspace
+
+      - name: doctor
+        run: cargo run -p agentos-cli -- doctor

CODE_OF_CONDUCT.md

@@ -0,0 +1,31 @@
+# Code of Conduct
+
+## Our pledge
+
+We pledge to make participation in AgentOS a harassment-free experience for everyone,
+regardless of age, body size, visible or invisible disability, ethnicity, sex
+characteristics, gender identity and expression, experience level, education,
+socio-economic status, nationality, personal appearance, race, caste, color, religion,
+or sexual identity and orientation.
+
+## Our standards
+
+Examples of behavior that contributes to a positive environment:
+
+- Demonstrating empathy and kindness
+- Giving and gracefully accepting constructive feedback
+- Focusing on what is best for the community and the runtime’s invariants
+- Crediting others’ ideas
+
+Examples of unacceptable behavior:
+
+- Harassment, trolling, insulting or derogatory comments
+- Publishing others’ private information
+- Sexualized language or imagery, or unwanted sexual attention
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement
+
+Report issues to the maintainers via GitHub (private security contact in [SECURITY.md](SECURITY.md)
+for sensitive matters). Maintainers may warn, limit, or ban contributors who violate
+this Code. This project follows the spirit of the [Contributor Covenant](https://www.contributor-covenant.org/) v2.1.

CONTRIBUTING.md

@@ -1,21 +1,26 @@
 # Contributing to AgentOS
 
-Thanks for helping build a durable agent runtime.
+Thanks for helping grow the [oasis](VISION.md)—a durable, auditable agent runtime.
+
+## Before you code
+
+1. Skim [VISION.md](VISION.md) and [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md).
+2. Prefer a [good first issue](docs/GOOD_FIRST_ISSUES.md) or file one with the template.
+3. Keep phase claims honest per [LIFECYCLE.md](LIFECYCLE.md).
 
 ## Development
 
 ```bash
 cargo test --workspace
 cargo clippy --workspace --all-targets -- -D warnings
-cargo fmt --all
+cargo fmt --all -- --check
 cargo run -p agentos-cli -- doctor
 ```
 
-Use a SQLite path when testing crash-resume:
+Durable resume smoke:
 
 ```bash
 cargo run -p agentos-cli -- --db /tmp/agentos.db run "goal"
-# kill -9 the process mid-run in real tests, then:
 cargo run -p agentos-cli -- --db /tmp/agentos.db resume <run_id>
 ```
 
@@ -28,12 +33,12 @@ cargo run -p agentos-cli -- --db /tmp/agentos.db resume <run_id>
 
 ## Pull requests
 
-- Keep PRs focused; prefer small crates-scoped changes.
+- Use the PR template; keep changes focused.
 - Include tests for journal, policy, and resume paths you touch.
-- Follow Apache-2.0; do not add incompatible licenses.
-- Link any ADR updates in `docs/adr/`.
+- Apache-2.0 only—no incompatible licenses.
+- Link ADR updates under `docs/adr/`.
 
 ## Code of conduct
 
-Be respectful. No harassment, personal attacks, or gatekeeping. Maintainers may
-moderate discussions and reject contributions that violate these norms.
+See [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md). Maintainers may moderate and reject
+contributions that violate community standards.

Cargo.toml

@@ -16,7 +16,7 @@ default-members = [
 ]
 
 [workspace.package]
-version = "0.1.0"
+version = "0.2.0"
 edition = "2021"
 license = "Apache-2.0"
 authors = ["AgentOS Contributors"]

LIFECYCLE.md

@@ -59,7 +59,9 @@ application, journal a hash chain, pause for HITL, and expose a mock-backed CLI
 | Tag | Meaning |
 |-----|---------|
 | `v0.1.0` | Phase 0 complete |
-| `v0.2.0` | Phase 1 complete |
+| `v0.2.0` | Phase 1 complete (+ community presence) |
 | `v0.3.0+` | Later phases |
 
 Phase numbers in docs must stay honest: never claim Phase 2–4 done until exit criteria land.
+
+Release narrative for humans: [docs/RELEASE_NOTES.md](docs/RELEASE_NOTES.md).