Improve contributor guidance and clarify hosting reality

- CONTRIBUTING.md: replace JS-toolchain template residue (npm/standard
  linter) with actual Python/MkDocs/JSON-Schema dev setup; add Code of
  Conduct link, security disclosure path via GitHub PVR, branch naming
  convention, DCO sign-off instruction, explicit MIT contribution
  license clause, and spec-change discussion guidance.
- CLAUDE.md: correct hosting description — this repo is the spec source
  of truth; the live site at agentcontrolstandard.ai is built from a
  separate repo and does not deploy from here.
- Delete .github/workflows/deploy_mkdocs.yml — was failing on every
  push (Pages not enabled, stack mismatch with the real Next.js site)
  and served no purpose.

Author: rocklambros

.github/workflows/deploy_mkdocs.yml

@@ -89,8 +89,10 @@ The documentation follows this hierarchy:
 ### Development Setup
 This is a documentation-focused project built with:
 - **UV** for Python dependency management (replaces pip)
-- **MkDocs Material** for documentation generation
-- **GitHub Pages** for hosting at agentcontrolstandard.org
+- **MkDocs Material** for local documentation preview
+
+### Hosting (decoupled from this repo)
+This repository is the **source of truth for the ACS spec** (schema, hooks, events, AgBOM definitions, written specification). The marketing and docs site at **agentcontrolstandard.ai** is built and deployed independently from a separate repository — changes here do not propagate automatically. The `.org` and `.com` domains redirect to `.ai`.
 
 ### Roadmap Context
 - **v0.1** (Current): Documentation, schemas, and requirements

CLAUDE.md

@@ -6,6 +6,10 @@ We're building trustworthy AI agents together. Your contributions make the futur
 
 Search existing issues and pull requests to avoid duplicating efforts.
 
+## Code of Conduct
+
+This project follows our [Code of Conduct](./CODE_OF_CONDUCT.md). By participating, you agree to uphold it.
+
 ## How to Contribute
 
 **Ideas**: Join issue discussions or start new ones. Your voice shapes ACS direction.
@@ -18,23 +22,28 @@ Search existing issues and pull requests to avoid duplicating efforts.
 
 **Standards**: Help Improve ACS, extend CycloneDX, SPDX, SWID for agent components.
 
-## Development Process
+## Local Development
+
+```bash
+uv pip install -e .          # install dependencies
+uv run mkdocs serve          # preview docs at http://localhost:8000
+uv run mkdocs build          # build static docs
+```
 
-1. **Fork the repository** - Create your own copy
-2. **Sync branches** - Keep up-to-date with latest changes  
-3. **Create feature branch** - Work in isolation
-4. **Make your changes** - Implement improvements
-5. **Test thoroughly** - Ensure everything works
-6. **Submit pull request** - Request merge to `main` branch
-7. **Address feedback** - Collaborate on refinements
+For prose contributions, follow the [editorial style guide](./STYLE.md). For schema contributions, validate `specification/ACS/acs_schema.json` against the JSON Schema spec before submitting.
 
-## Code Standards
+All submissions go through GitHub pull request review. See [GitHub's PR guide](https://docs.github.com/en/pull-requests) if you're new to the workflow.
 
-We use [`standard`][standard-url] for consistent code style. Run `npm test` to check automatically.
+## Development Process
 
-All submissions require review via GitHub pull requests. Consult [GitHub Help](https://help.github.com/articles/about-pull-requests/) for guidance.
+1. **Fork the repository** and clone your fork
+2. **Create a feature branch** — use `feature/<short-description>` or `fix/<short-description>`
+3. **Make your changes** following the style guide
+4. **Sign your commits** with `git commit -s` (required by the DCO below)
+5. **Open a pull request** against `main`
+6. **Address review feedback** to land your change
 
-[standard-url]: https://github.com/standard/standard
+For changes to the spec itself (`acs_schema.json`, hooks, events), open a [Discussion](https://github.com/Agent-Control-Standard/ACS/discussions) before submitting a PR — these affect downstream implementers and warrant a longer conversation.
 
 ## What We Need
 
@@ -51,6 +60,10 @@ Look for unassigned [Open Issues](https://github.com/Agent-Control-Standard/ACS/
 
 Project maintainers handle formal releases. Focus on contributing great features and fixes.
 
+## Reporting Security Issues
+
+**Do not file public issues for security vulnerabilities.** Use GitHub's [private vulnerability reporting](https://github.com/Agent-Control-Standard/ACS/security/advisories/new) to disclose privately. We'll acknowledge within 72 hours and coordinate a fix and disclosure timeline with you.
+
 ## Developer's Certificate of Origin 1.1
 
 By making a contribution to this project, I certify that:
@@ -72,11 +85,13 @@ By making a contribution to this project, I certify that:
   including my sign-off) is maintained indefinitely and may be redistributed consistent
   with this project or the open source license(s) involved.
 
+By contributing, you agree that your contributions will be licensed under the [MIT License](./LICENSE.txt) — the same license that covers the rest of the project.
+
 This guide is based on [github-contributing](https://raw.githubusercontent.com/standard/.github/refs/heads/master/CONTRIBUTING.md).
 
 ## Community
 
 - **[GitHub Discussions](https://github.com/Agent-Control-Standard/ACS/discussions)**: Ask questions, share ideas
 - **[Issues](https://github.com/Agent-Control-Standard/ACS/issues)**: Report bugs, request features
 
-We're building the future of AI agent observability and control. Join us.
+We're building the future of AI agent observability and control. Join us.