Skip to content

[Task] Document current-state project-meta-sync contract #506

Closed

Description

@ashleyshaw

Deliverable

Document current project-meta-sync behaviour as-is, including preflight requirements and Status/Priority/Type field sync boundaries.

Scope Boundary

  • In scope: documentation of current behaviour.
  • Out of scope: extending synced fields or workflow refactors.

Acceptance Checklist

  • Preflight requirements are documented (LS_PROJECT_URL, LS_APP_ID, LS_APP_PRIVATE_KEY).
  • Synced fields explicitly limited to Status, Priority, Type.
  • Close/merge status handling and defaults are documented.
  • References point to canonical workflow and field mapping YAML.

Branch Prefix Expectation

  • Use docs/.

Validation Commands

npx markdownlint-cli2 "docs/ISSUE-FIELDS.md" "docs/GITHUB_PROJECT_OPERATIONS_SPEC.md"
node scripts/validation/validate-issue-fields.cjs

Touched Paths

  • docs/ISSUE-FIELDS.md
  • docs/GITHUB_PROJECT_OPERATIONS_SPEC.md
  • .github/workflows/project-meta-sync.yml
  • .github/issue-fields.yml

Activity

  1. linear-code commented on May 28, 2026

    @linear-code
  2. self-assigned this
    on Aug 4, 2026
  3. github-actions commented on Aug 4, 2026

    @github-actions
    Contributor

    ⏱️ Aging and SLA annotation

    • Age: 68 day(s)
    • SLA state: SLA breached
    • Thresholds: warn at 7 days, breach at 14 days
    • Last updated: 2026-08-04T16:55:13.212Z

    Maintained by project-meta-sync workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions