Skip to content

refactor(attribution): move this repository's attribution settings to docs/conventions/attribution.yaml #10540

Description

@kyle-sexton

Slice 2 of #9729, which tracks the move of the attribution settings from .claude/attribution.json to docs/conventions/attribution.yaml. The split and its basis are in the re-triage record on #9729.

Outcome

This repository's attribution settings move to docs/conventions/attribution.yaml, validated by a schema the plugin ships at plugins/attribution/schemas/attribution.schema.json (where scripts/check-convention-yaml.sh:16 looks for it; CI already runs that check). The schema and the YAML land together. .claude/attribution.json stays in place; deleting it is the #5906 cleanup slice.

Blocked by: #10538 (slice 1, the YAML-first reader); before it lands the YAML would be an unread second copy of every value. The parent tracker does not block this slice.

Done when

  • docs/conventions/attribution.yaml carries every value of .claude/attribution.json and scripts/check-convention-yaml.sh --check exits 0 against plugins/attribution/schemas/attribution.schema.json.
  • The PR body lists each migrated setting with its new home and schema.
  • scripts/check-changelog-fragments.sh --check-required origin/main exits 0.

Activity

  1. added theissue type on Oct 27, 2026
  2. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 27, 2026
  3. github-actions commented on Oct 27, 2026

    @github-actions
    Contributor

    Proposed work class: work-class: scoped
    Basis: automated intake triage; the lanes App applied this class.

    Size: Small
    Complexity: Low
    Uncertainty: Known
    Flags: none
    Blocked by: #10538

    Understood: add docs/conventions/attribution.yaml with every value from .claude/attribution.json, and ship plugins/attribution/schemas/attribution.schema.json in the same change so scripts/check-convention-yaml.sh --check passes. .claude/attribution.json stays in place. The issue states its outcome and done-when items exactly, so nothing is missing. It is slice 2 of the parent tracker #9729 (not a duplicate) and depends on #10538, the YAML-first reader.

    Automated triage, applied by the lanes App.

  4. added and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 27, 2026
  5. melodic-automation-lanes commented on Oct 27, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane yet: blocker #10538 is not closed by a listed human or a merge; blocker #9729 is not closed by a listed human or a merge.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.status: readyTriaged, unblocked, and fully specified; eligible to pick up.

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions