Implement partner/team section from approved biographies

[iainherd]

Goal

Create the team/partner section using the supplied biographies while preserving compliance review constraints.

Source artefacts

• Lir Capital Team Biogs V1.docx
• Lir_Website_Compliance_Copy_Review_v0.1.md §H

Acceptance criteria

• Bios are structured into a content model.
• Draft web bios are concise, senior, and consistent in voice.
• Unverified or awkward draft phrasing is flagged, not blindly published.
• Third-party references and claims are listed for sign-off where needed.
• Responsive cards/detail pages meet accessibility requirements.

[iainherd]

Agent allocation

Primary profile: agent:frontend-implementer
Required reviewer profiles: agent:content-strategist, agent:compliance-reviewer, agent:design-director, agent:browser-qa-reviewer, agent:code-security-reviewer

Reason: Team section is implementation-led because the issue is to implement the section; content/compliance/design/QA/security review remain required.

Orchestration rules:

• Morwenna/orchestrator retains final repo, PR, deployment, and closeout verification.
• Use fresh bounded subagents for implementation/review slices; do not ask child agents to ingest the full artefact set unless their issue explicitly requires it.
• Spec/brief/content/design compliance review happens before code-quality/security review.
• Subagent reports are evidence, not proof: parent must inspect diff/status and rerun relevant checks before closure.
• Spawn the named Hermes profile only for long-running independent work; otherwise use delegate_task with a self-contained, profile-specific prompt.

[iainherd]

Compliance claim references

This issue cannot close until the relevant claim IDs have an explicit status in docs/compliance/claims-register.md once #18 lands.

Relevant claim IDs: CL-007, CL-010, CL-015

Closeout must state: final status, exact approved/fallback wording used, owner/sign-off or exclusion reason, and agent:compliance-reviewer verdict.