Reconcile README + wiki with the v0.1.0 code surface

Fixes 14 drift findings from the post-v0.1.0 docs audit:

Critical
- Drop the non-existent `policy --strict` flag from the
  control-and-reproducibility persona path. Default policy is already
  strict; document `--relaxed-permissions` as the opt-out.
- Rename `index.md` to `INDEX.md` in README and Knowledge-Base.md to
  match the actual filename written by knowledge.py (case-sensitive on
  Linux).

Important
- Extend the "What it creates" listing in README and the directory tree
  in Knowledge-Base.md to include every folder write_knowledge_base
  actually emits: decisions/, sessions/, sharing/, plus the layered
  scopes (team/, department/, unit/, company/).
- Mention .coding-scaffold/team/sources/ under optional outputs so
  readers know where team-sync imports land.
- Add Claude Code and Codex to the README installer sentence; both
  install via npm.
- Move twelve delivered items (P1-01..P1-05, P2-01..P2-05, P3-05,
  P3-06, P3-07) out of Review-Backlog Priority sections into a
  Delivered-as-of-v0.1.0 section with cross-references.

Minor
- Document --share and --relaxed-permissions flags in Policy-Packs.md.
- Convert MediaWiki-style [[X]] links in Home.md, _Sidebar.md,
  Policy-Packs.md, and Knowledge-Base.md to relative Markdown links
  so they resolve when browsing docs/wiki/ in the repo.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: JRS1986

README.md

@@ -94,8 +94,8 @@ cd ~/dev/my-project
 
 Setup can run before any model is configured. It validates the selected coding tool and, when
 stdin is interactive, asks before installing a missing tool. OpenCode and Hermes use their official
-install scripts; OpenClaude and Pi use npm packages. It can also configure the knowledge backend
-and optional shared Git remote during setup. Nothing is installed silently.
+install scripts; Claude Code, Codex, OpenClaude, and Pi use npm packages. It can also configure
+the knowledge backend and optional shared Git remote during setup. Nothing is installed silently.
 
 If you already have `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, Azure variables, `GITHUB_TOKEN`, or a
 local runtime installed, the scaffold will detect that. To keep credentials project-local, create an
@@ -353,15 +353,17 @@ Plain Markdown:
 coding-scaffold knowledge create --target ~/dev/my-project
 ```
 
-New knowledge bases include raw inputs and a curated wiki:
+New knowledge bases include raw inputs, a curated wiki, decision records, session notes, and
+optional hierarchical-sharing layers (`team` / `department` / `unit` / `company`). See
+[Knowledge Base](docs/wiki/Knowledge-Base.md) for the full tree. The shorthand:
 
 ```text
 .coding-scaffold/knowledge/
   raw/
   wiki/
   skills/
   agents/
-  index.md
+  INDEX.md
 ```
 
 Create reviewable curated proposals from raw notes:
@@ -512,7 +514,14 @@ as a substitute for better retrieval, smaller task boundaries, or fresh sessions
 - `ORCHESTRATION.md` and `orchestration.json`: agent-role guidance.
 - `skills/README.md` and `SKILLS.md`: project skill guidance.
 - `KNOWLEDGE.md`, `knowledge.json`, and `knowledge/`: optional team memory.
-- `knowledge/raw/`, `knowledge/wiki/`, `knowledge/index.md`: raw inputs and curated wiki pages.
+- `knowledge/INDEX.md`, `knowledge/README.md`, `knowledge/glossary.md`, `knowledge/links.md`,
+  `knowledge/sync.md`: top-level navigation and starter notes.
+- `knowledge/raw/{meetings,decisions,code-notes,incidents}/`: raw input notes by category.
+- `knowledge/wiki/{architecture,setup,testing,deployment,domain-language,decisions}.md`:
+  curated wiki pages with `owner` / `last_reviewed` / `source_refs` frontmatter.
+- `knowledge/{decisions,sessions,skills,agents,sharing}/`: decision records, session notes,
+  reusable skills, agent patterns, and hierarchical-sharing scaffolding.
+- `knowledge/{team,department,unit,company}/`: layered scopes for hierarchical sharing.
 - `.coding-scaffold/policy/`: optional company/unit/department/team policy packs.
 - `.coding-scaffold/team-onboarding.json` and `team-provenance.json`: optional experienced-team onboarding.
 - `GETTING_STARTED.md` and `FIRST_SESSION.md`: first-use walkthroughs.
@@ -524,6 +533,8 @@ Optional commands can also generate:
 - `opencode.json`, `.opencode/agents/`, and `.opencode/commands/`.
 - `CLAUDE.md`, `.claude/settings.json`, `.claude/commands/`, and `.claude/agents/`.
 - `AGENTS.md`, `.codex/config.toml`, and `.codex/skills/`.
+- `.coding-scaffold/team/sources/<kind>/<slug>/`: third-party manifest content imported by
+  `team sync` (cloned repos keep `.git` inside an `_repo/` subdirectory for fast-forward pulls).
 - `.coding-scaffold/ROUTELLM.md` and `routellm.config.yaml`.
 - `.coding-scaffold/OPEN_MULTI_AGENT.md`, `open-multi-agent.team.json`, and a TypeScript example.
 - Obsidian vault files under `.coding-scaffold/knowledge/.obsidian/`.

docs/wiki/Home.md

@@ -35,15 +35,15 @@ call happens later, inside the coding tool, when a developer runs an agent comma
 
 ## Recommended Reading
 
-1. [[Getting Started]]: install, run setup, refresh safely, and complete the first agentic coding session.
-2. [[Core Concepts]]: understand the main ideas before introducing it to a team.
-3. [[Model Selection and Providers]]: local-first routing, Azure/OpenAI/Anthropic abstraction, and auto mode.
-4. [[Skills and Agents]]: how teams turn good workflows into reusable assets.
-5. [[Knowledge Base]]: Markdown, Obsidian, MemPalace, and shared GitHub/GitLab memory.
-6. [[Context Hygiene]]: avoid oversized or stale context and add optional compression.
-7. [[Team Onboarding]]: connect new developers to shared knowledge, skills, agents, and policy.
-8. [[Policy Packs]]: local OpenCode policy defaults for company/unit/team rollout.
-9. [[Team Rollout]]: a practical adoption plan for a team workshop or internal pilot.
+1. [Getting Started](Getting-Started.md): install, run setup, refresh safely, and complete the first agentic coding session.
+2. [Core Concepts](Core-Concepts.md): understand the main ideas before introducing it to a team.
+3. [Model Selection and Providers](Model-Selection-and-Providers.md): local-first routing, Azure/OpenAI/Anthropic abstraction, and auto mode.
+4. [Skills and Agents](Skills-and-Agents.md): how teams turn good workflows into reusable assets.
+5. [Knowledge Base](Knowledge-Base.md): Markdown, Obsidian, MemPalace, and shared GitHub/GitLab memory.
+6. [Context Hygiene](Context-Hygiene.md): avoid oversized or stale context and add optional compression.
+7. [Team Onboarding](Team-Onboarding.md): connect new developers to shared knowledge, skills, agents, and policy.
+8. [Policy Packs](Policy-Packs.md): local OpenCode policy defaults for company/unit/team rollout.
+9. [Team Rollout](Team-Rollout.md): a practical adoption plan for a team workshop or internal pilot.
 
 ## Design Posture
 

docs/wiki/Knowledge-Base.md

@@ -17,28 +17,45 @@ This creates:
 - `.coding-scaffold/knowledge.json`
 - `.coding-scaffold/knowledge/`
 
-The generated knowledge base now separates raw inputs from curated wiki pages:
+The generated knowledge base separates raw inputs from curated wiki pages, and includes
+scaffolding for decision records, session notes, reusable skills and agents, and the optional
+hierarchical-sharing layers:
 
 ```text
 .coding-scaffold/knowledge/
+  INDEX.md                         # entry point — start reading here
+  README.md
+  glossary.md
+  links.md
+  sync.md
   raw/
     meetings/
     decisions/
     code-notes/
     incidents/
-  wiki/
+  wiki/                            # curated, reviewed source of truth
     architecture.md
     setup.md
     testing.md
     deployment.md
     domain-language.md
     decisions.md
-  skills/
-  agents/
-  index.md
+  decisions/                       # ADR-style decision records
+    0001-decision-template.md
+  sessions/                        # captured agent-session notes
+    session-template.md
+  skills/                          # reusable team skills
+  agents/                          # reusable agent patterns
+  sharing/                         # hierarchical-sharing entry point
+  team/                            # hierarchical layer: project facts, local prompts
+  department/                      # hierarchical layer: runbooks, system patterns
+  unit/                            # hierarchical layer: domain vocabulary, reference arch
+  company/                         # hierarchical layer: approved standards
 ```
 
 Raw notes are source material. Curated wiki pages are the reviewable source of truth for agents.
+The layered folders (`team` / `department` / `unit` / `company`) are optional — see
+[Hierarchical Sharing](#hierarchical-sharing) for when to use them.
 
 ## Shared GitHub Or GitLab Memory
 
@@ -108,7 +125,7 @@ The status command counts notes by scope and maturity, and flags missing frontma
 notes. It also distinguishes raw notes from curated wiki pages, flags missing `owner`,
 `last_reviewed`, and `source_refs`, and warns when curated pages have not been reviewed recently.
 The budget command estimates whether the knowledge base is still a healthy size for an agent
-session. See [[Context Hygiene]] before compressing or loading large shared notes.
+session. See [Context Hygiene](Context-Hygiene.md) before compressing or loading large shared notes.
 
 Create reviewable curated proposals from raw notes:
 

docs/wiki/Policy-Packs.md

@@ -2,7 +2,7 @@
 
 Policy packs capture company, unit, department, or team defaults for AI-enabled coding. They are
 reviewable local configuration, not a replacement for identity policy, network controls, or CI.
-See [[Security]] before using policy packs in company repositories.
+See [Security](Security.md) before using policy packs in company repositories.
 
 ## Generate A Policy
 
@@ -42,6 +42,28 @@ Provider IDs and MCP server names should match the effective OpenCode configurat
 team. If organization-wide tooling injects remote MCP servers, disable known servers by name and
 verify the final config in the coding tool.
 
+## Available Flags
+
+- `--scope {company,unit,department,team}` — audience and ownership layer for this policy.
+- `--share {disabled,manual,auto}` — OpenCode share-mode default. `disabled` is the default and
+  matches the recommended posture for company repositories.
+- `--adapter {none,opencode}` — pick which adapter the policy should configure.
+- `--enable-provider <id>` / `--disable-provider <id>` — explicit allow/deny lists, repeatable.
+- `--disable-mcp-server <name>` — block a named MCP server, repeatable.
+- `--mcp {project-empty,inherit}` — start the project's `mcp` config empty or inherit existing.
+- `--relaxed-permissions` — disable the default `permission.edit: ask` / `permission.bash: ask`
+  gate. Pass this only when the team has deliberately decided that ask-before-action is too
+  noisy; the default (strict) is recommended for company and team scopes.
+
+Example with the share mode and permissions explicitly opted out of strict:
+
+```bash
+coding-scaffold policy --target ~/dev/my-project \
+  --scope team \
+  --share manual \
+  --relaxed-permissions
+```
+
 ## Scope Strategy
 
 - `company`: approved standards, approved providers, security and privacy defaults.