📖 docs: review Symphony positioning and spec alignment

[mendezr]

Summary

• Add Symphony to the maintained landscape comparison, with docs/landscape.md as an entry point.
• Review all 18 SPEC.md sections and Appendix A against pinned Symphony revision be10a1b79df723d6d7612b5651c8522704dafb2e, linking Hive evidence and distinguishing overlap from conformance gaps.
• Record the Linear decision: reuse the adapter already in v5; defer workflow/app-server interoperability to a separate scoped proposal.
• Provide optional proof-of-work headings and outreach copy without changing runtime behavior or posting externally.

Corrects two issue premises: Symphony already includes pre-dispatch validation, and Hive already supports Linear. Explicitly avoids spec-conformance and universal run-isolation claims.

Fixes #10626

Validation

Not run (docs only; repository instructions reserve tests and documentation guards for CI). Read the full upstream specification and README, inspected local provider/runner contracts and supporting tests, and checked referenced local files exist. No runtime or policy changes.

— hive: backend=pi model=openai-codex/gpt-6.1-sol

---

🐝 Hive Agent: contributor | SHA: 1ed86d986

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign danathar for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

Open PR overlap check

Base branch: v5

Conflicts are checked with every PR merged onto the current tip of v5, so a PR that only needs a rebase is not reported as conflicting with its siblings.

PR	Title	Relation	Files
#10636	📖 docs: align Goose integration with AAIF upstream	same files	src/docs/landscape.md
#10631	📖 docs: add gh-aw on-ramp and agentics gallery entry	CONFLICT	src/docs/landscape.md

[hivecommons-hive]

Check report (fork branch — hive cannot push here): every failing check on this PR is the v5 baseline fingerprint tracked in #10623 (RE2 (?= regexp panic → docker (hive)/overlayfs-exec-guard/golangci-lint/test shards; TestOpenAPISpecCoversEveryRegisteredRoute; TestAgentsCollapsedSummaryRendersPerAgentTiles; TestStableNextPromotionAtUnknownWhenNothingQueued hitting live GitHub, stubbed by #10587), none of it from this docs diff. The fix landed on v5 at 6552932 (#10612).

Fix: sync your branch with v5 and push — git fetch upstream v5 && git merge upstream/v5 && git push (a merge commit keeps your DCO sign-offs intact; no force-push needed). CI will re-run on the green base.

---

🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Docs-only; checked the parts a link checker and a reader would trip on. Looks correct to me.

• All 23 relative links in docs/design/symphony-spec-alignment.md resolve at this head (including ../../src/pkg/worksource/{linear,factory,worksource}.go, ../../src/pkg/agent/sandbox_executor.go, ../outreach-antispam.md), as do work-sources.md and integrations/work-source-providers.md from src/docs/landscape.md.
• The claim that Hive's planning adapters include GitHub Issues/Projects, Linear and Jira matches src/pkg/worksource/{github_issues,github_projects,linear,jira}.go.
• The Fullsend wording change ("most directly comparable" → "a closely comparable", src/docs/landscape.md:22) is the only edit to existing text and is consistent with adding a second peer entry.
• Changelog fragment uses a valid added- prefix.

No runtime files touched. Ready for a maintainer's read on the positioning language itself, which is editorial rather than something I can verify.

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

[clubanderson]

Reviewed after rebase onto current v5. Docs-only change; Symphony facts match the pinned OpenAI README/SPEC, links are pinned, and no CI/security behavior changes are introduced.

[kubestellar-prow]

LGTM label has been added.

Details

Git tree hash: 9dfa9f6fd73447f7f2a46c20061901215732d386

[hivecommons-hive]

Mechanical review done; the positioning content needs a maintainer's eye.

What I verified at c20d4ef:

• All 22 relative links in docs/design/symphony-spec-alignment.md (the E1–E6 evidence map plus ../outreach-antispam.md) resolve to files in the tree, including the Go symbols' files (src/pkg/worksource/worksource.go, src/pkg/agent/sandbox_executor.go, etc.).
• New docs/landscape.md is a 7-line pointer to the maintained src/docs/landscape.md, so the two copies don't diverge.
• changelog.d/added-symphony-positioning.md uses the added-<slug> form the fragment guard accepts.

What I could not verify: every "Diverges / Satisfies" row cites the Symphony SPEC at a pinned external revision. I don't read third-party repos, so I have not checked those section numbers or the claims about what the spec requires. The one question for a human: is the "shares the operating model, not spec-conformant" framing the positioning you want published in src/docs/landscape.md? That is a product statement, not a code-correctness one. @clubanderson seems best placed to decide.

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88