chore(unic-archon-dlc): `ticket` is the plugin's word — sweep `work item` and `issue`, rename issues.json to tickets.json, reopen the Issues JSON entry

オープン
  • 何か問題がありますか？
#460 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
リファクタリング
明瞭さ
おおむね明確
活発さ
活発
技術スタック
javascript
領域
developer-experience, tooling

調査の方向性

Start by comparing #439 criterion 13 with the tree at 0b74117 to determine the rename order. Inspect CONTEXT.md and commands/setup.md, then trace the 62 work item and 74 issues.json occurrences across the named files, including the installed tracker contract. Done means the vocabulary and file rename are consistent while preserving dated host-word evidence and updating the Consumer-facing contract.

索引モデルが issue の本文から書いたものです。

説明

app:unic-archon-dlc needs-specs p3 tech-debt

Ruled 2026-09-04 22:30 by the maintainer, in #439's grilling: the word is ticket. work item is Azure DevOps's word, issue is GitHub's and Jira's, and ticket is the one no host in front of us claims. So this is no longer a spike; it is the sweep. Scope, in one set: ticket becomes the plugin's term in CONTEXT.md; the Issues JSON entry is reopened, because it lists tickets under _Avoid_ today; issues.json is renamed tickets.json (74 occurrences in 16 files on 0b74117); the 62 work item occurrences go, including the § Work-item scope heading of the tracker contract /setup installs, which is a Consumer-facing change and must say so. Grill the order against #439, whose criterion 13 changes the same file's shape: one of the two renames it, and the other is written against the tree that one leaves.

What this is

A vocabulary question the maintainer raised in #439's grilling on 2026-09-04, spun out because it reaches every command and Box. His words: "utilizo ticket porque WorkItem es propio de ADO y en este repositorio no tenemos en cuenta la tecnología que utilizan los consumidores."

Measured on 0b74117, plugin tree only: work item 62 occurrences, ticket 285, issue 554. One of the 62 is the § Work-item scope heading of the tracker contract /setup installs into every Consumer, so a sweep there is a Consumer-facing change, not a plugin-only one. issue is as much a host's word as ticket is; CONTEXT.md currently defines Issues JSON and lists tickets under its _Avoid_ line, so renaming issues.json to tickets.json (74 occurrences in 16 files) reverses a recorded decision rather than applying one.

What is left to grill

The word is ruled. Open: the order against #439 (above); whether issue survives anywhere as a host's word in a dated evidence citation, which the staging doctrine allows for tool names; and how the Consumer-facing heading change reaches DXP-DesignSystem's installed contract, which /setup never rewrites.

Related

#439 (source). CONTEXT.md Issues JSON entry. The tracker contract template in commands/setup.md.

主要言語
HTML
スター
1
フォーク
0
平均マージ
49分
マージ済み PR（30日）
20

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

unic/unic-agents-plugins のほかの issue

unic/unic-agents-plugins の issue をすべて見る

似ている issue

DevTools の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。