[docs] Consolidate developer specifications (v9.3)

[github-actions]

Developer Documentation Consolidation

Maintenance pass on scratchpad/dev.md — bumps the consolidated developer instructions file to v9.3 (2026-05-08).

Summary

• Tone scan: 0 tone issues found across all 63 spec files.
• Documented 1 new feature from PR Render engine.mcp.tool-timeout as numeric gateway toolTimeout seconds #31007 in the Workflow Patterns section.
• Contrasted session-timeout (string) and tool-timeout (numeric seconds) gateway config rendering.

Files Modified

• scratchpad/dev.md — added a subsection under Workflow Patterns documenting the new engine.mcp.tool-timeout numeric rendering behaviour, bumped version 9.2 → 9.3, added v9.3 entry to Document History.

Feature Note Added

engine.mcp.tool-timeout rendered as numeric toolTimeout seconds (PR #31007):
The engine.mcp.tool-timeout frontmatter value is now parsed from a Go duration string and rendered as a numeric toolTimeout seconds field in the MCP gateway config JSON. Previously the value was emitted verbatim as a string. The frontmatter still accepts duration strings (e.g., 30s, 2m, 1h); the compiler converts them to integer seconds before writing the gateway config. Empty value falls back to the gateway built-in default of 60 seconds.

Validation

• Markdown syntax validated.
• Mermaid diagrams unchanged (no new diagrams added).
• Consistent technical tone preserved.
• No spec source files needed tone fixes this cycle.

Review Notes

Please confirm:

1. The new feature note correctly summarises PR Render engine.mcp.tool-timeout as numeric gateway toolTimeout seconds #31007 (pkg/workflow/mcp_renderer.go lines 201–208 use durationStringToSeconds and emit numeric).
2. The example YAML accurately reflects the contrast between session-timeout (string) and tool-timeout (integer seconds).

Generated by Developer Documentation Consolidator · ● 15.1M · ◷

• expires on May 10, 2026, 2:09 PM UTC

---

Note

This was originally intended as a pull request, but the git push operation failed.

Workflow Run: View run details and download bundle artifact

The bundle file is available in the agent artifact in the workflow run linked above.

To create a pull request with the changes:

# Download the artifact from the workflow run
gh run download 25559828014 -n agent -D /tmp/agent-25559828014

# Fetch the bundle into a local branch
git fetch /tmp/agent-25559828014/aw-docs-consolidation-2026-05-08.bundle refs/heads/docs-consolidation-2026-05-08:refs/heads/docs-consolidation-2026-05-08-d95b057d7fe3b3e2
git checkout docs-consolidation-2026-05-08-d95b057d7fe3b3e2

# Push the branch to origin
git push origin docs-consolidation-2026-05-08-d95b057d7fe3b3e2

# Create the pull request
gh pr create --title '[docs] Consolidate developer specifications (v9.3)' --base main --head docs-consolidation-2026-05-08-d95b057d7fe3b3e2 --repo github/gh-aw