docs: add air-gapped apiops setup walkthroughs for GitHub Actions and Azure DevOps (#77)

* docs: add air-gapped environment walkthroughs for GitHub Actions and Azure DevOps

Add step-by-step guides under docs/walkthrough/ covering:
- Tarball preparation with --cli-package flag
- Lock file strategy for offline npm ci
- Self-hosted runner/agent configuration
- Workflow/pipeline modifications for offline operation
- Upgrade procedures and troubleshooting

Update docs/README.md navigation with new walkthrough section.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: EMaher <9244742+EMaher@users.noreply.github.com>

* docs: merge decision on air-gapped walkthrough documentation pattern

- Merged inbox/docwriter-airgapped-walkthroughs.md into decisions.md
- Established walkthrough pattern for complex multi-step deployment scenarios
- Covers GitHub Actions and Azure DevOps air-gapped deployments
- Pattern: docs/walkthrough/ (scenario-based), docs/ci-cd/ (reference), docs/guides/ (feature-oriented)
- Deleted merged inbox file

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: EMaher <9244742+EMaher@users.noreply.github.com>

* chore: record squad orchestration logs for air-gapped walkthrough task

Agent-Logs-Url: https://github.com/Azure/apiops-cli/sessions/55ca6c66-0c45-4eec-9647-95bcedd33b90

Co-authored-by: EMaher <9244742+EMaher@users.noreply.github.com>

* chore: remove accidental temp commit message file

Agent-Logs-Url: https://github.com/Azure/apiops-cli/sessions/55ca6c66-0c45-4eec-9647-95bcedd33b90

Co-authored-by: EMaher <9244742+EMaher@users.noreply.github.com>

* feat: revise air-gapped Azure DevOps doc per PR feedback

- Make local npm registry (Azure Artifacts) the primary approach
- Demote tarball flow to fallback section
- Remove redundant npm and transfer mechanism prerequisites
- Add official Microsoft docs links (agents, feeds, on-prem, sovereign clouds)
- Replace brittle embedded YAML with edit guidance referencing generated files
- Add sovereign clouds and on-premises section

Closes #44

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: EMaher <9244742+EMaher@users.noreply.github.com>

* updating articles for air-gapped environments

* reverting changes to squad

* modifying doc tree

* updating instructions for 'npm ci --offline'

* removing my name from squad history

* updating docwriter charter

* Updating squad to backup assertions with source URLs

* chore: add local feed npmrc

* updating devcontainer extensions

* revert: remove accidentally committed .npmrc

* update charter for docwriter and code reviewer

* update devops air-gapped doc command.

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: EMaher <9244742+EMaher@users.noreply.github.com>
Co-authored-by: Elizabeth Maher <enewman@microsoft.com>

Author: Copilot

.devcontainer/devcontainer.json

@@ -31,12 +31,12 @@
         "vitest.explorer",
         "GitHub.vscode-pull-request-github",
         "GitHub.copilot-chat",
-        "GitHub.vscode-github-actions",
         "ms-azuretools.vscode-azureresourcegroups",
         "ms-azure-devops.azure-pipelines",
         "vitest.dev",
         "ms-vscode.powershell",
-        "ms-azuretools.vscode-bicep"
+        "ms-azuretools.vscode-bicep",
+        "bierner.markdown-preview-github-styles"
       ]
     }
   },

.squad/agents/codereviewer/charter.md

@@ -110,6 +110,10 @@ These are patterns specific to this codebase. I check every one on every review.
 - ARM URI builders and parsers must handle workspace-scoped resources
 - Workspace context must propagate through extract/publish pipelines
 
+#### Documentation Shell Snippets
+- For Bash heredocs in docs, opener and closing delimiter lines (for example, `<<JSON` and `JSON`) must start at column 1 in the snippet.
+- Indented heredoc delimiters in documentation are a **🟡 Required change** because they can leave Git Bash at a hanging continuation prompt.
+
 ### Severity Levels
 
 - **🔴 Blocker** — Constitution violation, secret leak, untestable design, `any` type, missing `.js` import extension, typed DTO for APIM payload, data mutation of shared state. **PR cannot merge.** I will not approve with open blockers under any circumstances.

.squad/agents/docwriter/charter.md

@@ -30,11 +30,13 @@ Technical Writer specializing in user-facing documentation for API developers.
 ## Output Standards
 
 - All docs in `/docs` unless otherwise specified
-- Use GitHub-Flavored Markdown (GFM)
 - Mermaid blocks use ```mermaid fenced code blocks
 - File names: lowercase, hyphen-separated (e.g., `getting-started.md`, `architecture-overview.md`)
 - Include front matter or clear H1 title in every document
 - Cross-reference related docs with relative links
+- Back decisions, notes, and factual assertions with a credible source URL whenever possible
+- REQUIRED: Use GitHub-Flavored Markdown (https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)
+- Bash heredoc safety rule: when examples use heredocs, the opener and closing delimiter (for example, `<<JSON` and `JSON`) must start at column 1 in the snippet. Do not indent heredoc lines.
 
 ## Accuracy Policy — CRITICAL
 

.squad/agents/nodejsdev/charter.md

@@ -105,3 +105,7 @@ After making a decision others should know, write it to `.squad/decisions/inbox/
 ## Voice
 
 Exit codes matter. If a pipeline can't distinguish "publish succeeded" from "publish failed with partial writes" from "auth error," the tool is not CI/CD-ready. I will add distinct exit codes and I will document them. The same goes for `--format json` — structured output is a contract, not a convenience. If the JSON shape changes between versions, that's a breaking change and it needs a semver bump.
+
+## Evidence Standard
+
+- Back decisions, notes, and factual assertions with a credible source URL whenever possible

.squad/agents/ralph/charter.md

@@ -18,3 +18,7 @@ Persistent memory agent that maintains context across sessions.
 - Read project context and team decisions before starting work
 - Communicate clearly with team members
 - Follow established patterns and conventions
+
+## Evidence Standard
+
+- Back decisions, notes, and factual assertions with a credible source URL whenever possible

.squad/agents/scribe/charter.md

@@ -12,9 +12,14 @@ Documentation specialist maintaining history, decisions, and technical records.
 - Collaborate with team members on assigned work
 - Maintain code quality and project standards
 - Document decisions and progress in history
+- Keep updates as terse as possible while preserving critical context
+- Treat all `.squad/` files as public records; never store personally identifiable information (PII)
+- When recording decisions, notes, or technical assertions, include a credible source URL whenever possible
 
 ## Work Style
 
 - Read project context and team decisions before starting work
 - Communicate clearly with team members
 - Follow established patterns and conventions
+- Prefer concise, high-signal summaries over narrative detail
+- Redact names, emails, local user paths, and other personal identifiers in all squad artifacts

.squad/decisions.md

@@ -2,6 +2,19 @@
 
 ## Active Decisions
 
+### 2026-05-28T23:06:01Z: Team-Wide Evidence Standard
+**By:** User directive (anonymized)  
+**Status:** Active directive  
+**What:** All team members should back decisions, notes, and factual assertions with a credible source URL whenever possible.
+**Why:** Strengthens traceability and reviewability across public squad records.
+
+### 2026-05-28T22:55:05Z: DocWriter Uses GitHub-Style Markdown
+**By:** User directive (anonymized)  
+**Status:** Active directive  
+**What:** All documentation and guidance authored by DocWriter must use GitHub-style Markdown.
+**Why:** Ensures consistent rendering, readability, and contribution standards across repository documentation.
+**Source:** [Basic writing and formatting syntax - GitHub Docs](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)
+
 ### 2026-05-14T05:20:00Z: APIM v1 → v2 SKU Migration via apiops-cli
 **By:** ApimExpert + ApiOpsLead (joint research and decision)  
 **Status:** Proposed for team governance review  

.vscode/extensions.json

@@ -4,7 +4,6 @@
     "ms-vscode.vscode-typescript-next",
     "vitest.explorer",
     "GitHub.vscode-pull-request-github",
-    "GitHub.copilot",
     "GitHub.copilot-chat",
     "ms-azuretools.vscode-azureresourcegroups",
     "ms-azure-devops.azure-pipelines"

docs/README.md

@@ -9,6 +9,7 @@
 | [Getting Started](getting-started.md) | Install and run your first extract → publish cycle in 10 minutes |
 | [Command Reference](commands/) | Detailed docs for [extract](commands/extract.md), [publish](commands/publish.md), [init](commands/init.md) |
 | [CI/CD Integration](ci-cd/) | Set up [GitHub Actions](ci-cd/github-actions.md) or [Azure DevOps](ci-cd/azure-devops.md) pipelines |
+| [Walkthroughs](walkthrough/) | Step-by-step guides: [Air-gapped GitHub Actions](walkthrough/air-gapped-github-actions.md) (local registry or offline tarball), [Air-gapped Azure DevOps](walkthrough/air-gapped-azure-devops.md) (local registry or offline tarball) |
 
 ## How It Works
 
@@ -78,6 +79,9 @@ docs/
 ├── architecture/
 │   ├── overview.md                    — System design overview
 │   └── design-principles.md           — Architecture principles
+├── walkthrough/
+│   ├── air-gapped-github-actions.md                    — Using `apiops` in air-gapped CI/CD (GitHub Actions)
+│   ├── air-gapped-azure-devops.md                      — Using `apiops` in air-gapped CI/CD (Azure DevOps)
 └── troubleshooting/
     ├── common-errors.md               — Error messages and solutions
     ├── debugging-guide.md             — Debugging with --log-level