feat(specs): add bounded worker strategy and Flow bootstrap

[szmyty]

Why

Long worker sessions combine implementation, tests, documentation, CI, and cleanup before leaving a usable checkpoint. This draft captures the requested strategy for small, resumable jobs with explicit completion work and a live roadmap report at startup.

What changed

• Added worker-strategy v0.1.0 under canonical methodology specs: one primary role per job, a 5–10-minute scope target, issue mini sprints, bounded discovery, and finite loop-back batches.
• Defined a committed sprint handoff and explicit deferred checks, composing the existing repository-continuity and local-validation-evidence contracts.
• Kept implementation completion, validation, local evidence, remote CI, and parent-issue closure distinct.
• Added a copyable Flow suite bootstrap and follow-on execution prompt in docs/worker-strategy-guide.md.
• Regenerated the specification distribution and first-party catalog; updated README navigation/count and the Unreleased changelog.

The spec remains draft and opt-in. No consumer repository, live Flow roadmap, workflow settings, release behavior, or organization policy was changed.

Validation

Passed locally against the exact content tree 3118adf6e78277c8d8a65c4e2389621fc18d5d29:

• ./aether validate --specifications --graph --catalog --links --format "text" — 0 diagnostics.
• ./aether catalog generate --check.
• python3 catalog/validate_catalog.py — fixtures, schema, coverage, relationships, and digests valid.
• python3 library/organization/specs/build-distributions.py --check — all 32 spec distributions current.
• git diff --cached --check.

The API-published commit uses the same tree as the locally reviewed candidate. The broader ./aether test suite and full CI reproduction are deferred for this spec-only checkpoint, consistent with the requested workflow. No behavioral evaluation of the worker strategy or credit savings is claimed. No remote workflow was manually dispatched or rerun; the repository's existing pull-request trigger may run automatically.

Decisions and next checkpoint

• ADR not required: reversible, explicitly requested draft guidance composing existing contracts; no deployed policy or public runtime interface changes.
• Related: Add an agent catalog and Copilot cost-control specification #41 and Add canonical prompt and instruction libraries #40. This change does not close either broader issue.
• Source: explicit owner request on 2026-10-02 to capture this strategy in Aether and try it in a fresh Flow suite chat.
• Next: use the pinned bootstrap guide with the pinned spec. Report the live Flow roadmap and proposed next checkpoint before implementation.
• Trial questions: checkpoint sizing, checklist versus sub-issue clarity, and measured recovery/rework. These remain empirical and do not block trying the draft.