docs: revamp CONTRIBUTING.md with proposal workflow and PR template

Restructure contribution guidelines to clarify expectations:
- Issues are the primary entry point for all contributions
- PRs are for small fixes; features require issue + proposal first
- Implementation is handled by maintainer after proposal approval
- All development must use devcontainer (make devc)

Add PR template to surface checklist when contributors open PRs.
Add proposals/ directory with TEMPLATE.md for feature proposals.

Author: runkids

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+<!-- Thanks for contributing! Please read CONTRIBUTING.md before submitting. -->
+
+## Type
+
+- [ ] Bug fix
+- [ ] Small improvement (docs, typo, minor refactor)
+- [ ] Feature proposal (`proposals/` only — see [CONTRIBUTING.md](../CONTRIBUTING.md))
+
+## Linked Issue
+
+<!-- Recommended for bug fixes. Required for proposals. -->
+
+Closes #
+
+## Checklist
+
+- [ ] I've read [CONTRIBUTING.md](../CONTRIBUTING.md)
+- [ ] Tests included and passing (`make check`) — for code changes
+- [ ] No unrelated changes in the diff
+- [ ] Scope is focused — one concern per PR

.gitignore

@@ -30,6 +30,7 @@ docs/superpowers/
 !.skillshare/registry.yaml
 !.skillshare/.gitignore
 /specs/
+!/proposals/
 .pnpm-store/
 .feature-radar/
 .cache/

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## [0.19.1] - 2026-04-13
+
+### Bug Fixes
+
+- **Structured output no longer corrupted by update notices** — `--json`, `-j`, and `--format json/sarif/markdown` modes could emit a trailing human-readable update notification into stdout, producing invalid JSON for downstream consumers. The update check is now skipped entirely in structured-output modes, and the notification itself writes to stderr as a safety net. Refs: #129
+
 ## [0.19.0] - 2026-04-11
 
 ### New Features

CONTRIBUTING.md

@@ -2,76 +2,74 @@
 
 Thanks for your interest in contributing! This guide helps you get started.
 
-## How to Contribute
+## Start with an Issue
 
-### 1. Open an Issue First
+The best way to contribute is to [open an issue](https://github.com/runkids/skillshare/issues/new). Issues are where ideas, feature requests, and design discussions happen. This helps us:
 
-Before writing code, [open an issue](https://github.com/runkids/skillshare/issues/new) to describe what you'd like to change and why. This helps us:
+- Align on whether the change fits the project direction
+- Agree on scope and approach before any code is written
+- Avoid investing time in work that may not be merged
 
-- Align on the scope and approach
-- Avoid duplicate effort
-- Discuss alternative solutions early
+**Please open an issue before writing code**, even if you're confident in the approach. Skipping this step is the most common reason contributions can't be accepted.
 
-Even small changes benefit from a quick issue — it gives context for reviewers and future contributors.
+## Pull Requests
 
-### 2. Submit a Draft PR
+### What PRs are good for
 
-If you'd like to propose an implementation, open a [draft pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests) and link it to the issue. Draft PRs let us:
+PRs work best for **small, focused changes**:
 
-- Collaborate on the approach before investing time in polish
-- Catch design mismatches early
-- Provide incremental feedback
+- Bug fixes with a clear reproduction
+- Typo and documentation corrections
+- Small improvements (a few files, under ~200 lines of meaningful change)
 
-> **Note:** Due to the nature of this project, most PRs won't be merged directly — but every contribution is valuable. Your draft PR serves as a concrete reference that shapes the final implementation.
+These can go straight to a PR (still link to an issue if one exists).
 
-### 3. Include Tests
+### Feature Ideas
 
-PRs with test coverage are much easier to review and merge. skillshare has both unit and integration tests:
+For new features or large changes:
 
-- **Unit tests**: alongside source files (`*_test.go`)
-- **Integration tests**: `tests/integration/` using `testutil.Sandbox`
+1. **Open an issue** to describe the idea and the problem it solves
+2. **Submit a proposal** — copy [`proposals/TEMPLATE.md`](proposals/TEMPLATE.md), fill it in, and open a PR to `proposals/`
 
-Run the full check before submitting:
+Approved proposals will be added to the roadmap. Implementation is handled by the maintainer to ensure consistency with the project's architecture and codebase conventions.
 
-```bash
-make check          # format + lint + unit + integration tests
-```
-
-## Development Setup
+> **Note:** Due to the nature of this project, most feature PRs won't be merged directly — but every contribution is valuable. Your PR serves as a concrete reference that shapes the final implementation.
 
-### Option A: Dev Containers (Recommended)
+### PR Checklist
 
-Open in [Dev Containers](https://containers.dev/) — Go toolchain, Node.js, pnpm, and demo content are pre-configured.
+- [ ] Linked to an issue (required for features, recommended for bug fixes)
+- [ ] Tests included and passing (`make check`)
+- [ ] No unrelated changes in the diff
+- [ ] Commit messages explain "why", not just "what"
+- [ ] Scope is focused — one concern per PR
 
-### Option B: Local
+## Development Setup
 
-Requirements: Go 1.23+
+All development and testing should be done inside the **devcontainer**. This ensures a consistent environment (Go toolchain, Node.js, pnpm, and demo content are pre-configured).
 
 ```bash
 git clone https://github.com/runkids/skillshare.git
 cd skillshare
-make build          # build binary
-make check          # format + lint + test
+make devc            # start devcontainer + enter shell (one step)
 ```
 
-### Useful Commands
+Once inside the devcontainer:
 
 ```bash
-make build          # build binary → bin/skillshare
-make test           # unit + integration tests
-make test-unit      # unit tests only
-make lint           # go vet
-make fmt            # gofmt
-make check          # fmt + lint + test (must pass before PR)
-make ui-dev         # Go API server + Vite HMR for Web UI
+make build           # build binary → bin/skillshare
+make test            # unit + integration tests
+make check           # fmt + lint + test (must pass before PR)
+make ui-dev          # Go API server + Vite HMR for Web UI
 ```
 
-## PR Checklist
+Other devcontainer commands:
 
-- [ ] Linked to an issue
-- [ ] Tests included and passing (`make check`)
-- [ ] No unrelated changes in the diff
-- [ ] Commit messages explain "why", not just "what"
+```bash
+make devc-down       # stop devcontainer
+make devc-restart    # restart devcontainer
+make devc-reset      # full reset (remove volumes)
+make devc-status     # show devcontainer status
+```
 
 ## Questions?
 

README.md

@@ -253,6 +253,7 @@ Thanks to everyone who helped shape skillshare.
 <a href="https://github.com/jessica-engel"><img src="https://github.com/jessica-engel.png" width="50" style="border-radius:50%" alt="jessica-engel"></a>
 <a href="https://github.com/AlimuratYusup"><img src="https://github.com/AlimuratYusup.png" width="50" style="border-radius:50%" alt="AlimuratYusup"></a>
 <a href="https://github.com/thor-shuang"><img src="https://github.com/thor-shuang.png" width="50" style="border-radius:50%" alt="thor-shuang"></a>
+<a href="https://github.com/bishopmatthew"><img src="https://github.com/bishopmatthew.png" width="50" style="border-radius:50%" alt="bishopmatthew"></a>
 
 ---
 

proposals/TEMPLATE.md

@@ -0,0 +1,29 @@
+# Feature Proposal: [Title]
+
+## Problem
+
+What problem does this solve? Who is affected?
+
+## Proposed Solution
+
+Describe your approach at a high level. Include:
+
+- What changes are needed (CLI, UI, internal packages)
+- How it interacts with existing features
+- Any new dependencies
+
+## Alternatives Considered
+
+What other approaches did you consider? Why did you choose this one?
+
+## Scope
+
+Estimate the scope of changes:
+
+- [ ] Small (1-3 files, < 200 lines)
+- [ ] Medium (3-10 files, 200-500 lines)
+- [ ] Large (10+ files, 500+ lines)
+
+## Open Questions
+
+List anything you're unsure about or would like feedback on.

website/src/pages/changelog.md

@@ -9,6 +9,12 @@ All notable changes to skillshare are documented here. For the full commit histo
 
 ---
 
+## [0.19.1] - 2026-04-13
+
+### Bug Fixes
+
+- **Structured output no longer corrupted by update notices** — `--json`, `-j`, and `--format json/sarif/markdown` modes could emit a trailing human-readable update notification into stdout, producing invalid JSON for downstream consumers. The update check is now skipped entirely in structured-output modes, and the notification itself writes to stderr as a safety net. Refs: #129
+
 ## [0.19.0] - 2026-04-11
 
 ### New Features