Feat ja translation skill

[HARDIK-WEB-OSS]

Description

closes: #61997
related: #61984

Defined translation agent skills for the Japanese (ja) locale according to #62059.

• Terminology: Cross-linked translation.json for Katakana consistency (e.g., タスク for Task, トリガー for Triggerer).
• Noise Reduction: Removed i18n policy links per feedback in add SKILL.md and zh-CN agent skill instruction #62059 to narrow the agent context window.
• Token Efficiency: Using short SPDX license header to reduce overhead as proposed in Allow to use short SPDX licence identifier for selected files #62073.
• Linguistic Rules: Instructed agent to use polite 'Desu/Masu' form and noted that Japanese does not use plural suffixes.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  Generated-by: [Gemini] following the guidelines

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[HARDIK-WEB-OSS]

Hi @shahar1 and @Dev-iL, I have reverted the unrelated BigQuery changes as suggested. I have also updated the license header to include the URL per the feedback. My branch is now clean and only contains the Japanese locale translation agent skill. Ready for another look!

[Dev-iL]

I have also updated the license header to include the URL per the feedback.

I still don't see it.

[HARDIK-WEB-OSS]

Hi @Dev-iL and @shahar1, I've fixed the license header to the minimal 3-line format as per the feedback. I've also squashed the commits and cleaned the branch history. Re-opened and ready for a final review.

[HARDIK-WEB-OSS]

Hi @jason810496 and @shahar1, I have updated the branch. All feedback from @rsanda has been fully incorporated, and the technical structure has been approved by @Dev-iL.
Looking forward to the final review from @uranusjr or @sekikn so we can get this merged. Thanks for your time!

[HARDIK-WEB-OSS]

Hi @jason810496 @shahar1, just a quick update: the branch is synced. Ready for review.
I'm happy to help with any further polish for the Japanese locale or agent skills if needed. Cheers!

[shahar1]

Hi @jason810496 @shahar1, just a quick update: the branch is synced. Ready for review.
I'm happy to help with any further polish for the Japanese locale or agent skills if needed. Cheers!

Static checks seem to fail, please fix.
Also, please refrain from tagging me or Jason in every message - we already get notified about this PR since the first tagging.
Since I'm on a low availability these days, please consider that it might take me a while until I'll be able to review it properly.
Thank you!

[jason810496]

Hi @rsanda,

Could you please do a final check of the translation skill terminology when you have time before I merge it? Thanks!

[rsanda]

Thanks a lot!

All looks good except for the following:

queued | キュー待ち |

I need to check the code for the current translation. I think it should be "キュー済み."
Please give me sometime to double check it as I'm traveling and I don't have my PC with me.

[HARDIK-WEB-OSS]

Thanks a lot!

All looks good except for the following:

queued | キュー待ち |

I need to check the code for the current translation. I think it should be "キュー済み." Please give me sometime to double check it as I'm traveling and I don't have my PC with me.

Confirmed in common.json that the existing standard for 'queued' is '待機中'. I have updated ja.md to ensure 100% consistency with the current UI. Ready for final review and re-assignment.

[rsanda]

@HARDIK-WEB-OSS
Could you please change the following translations as below as common.json?

deferred": "延期済"
"failed": "失敗した"
"backfill": "過去分の再実行"
upstream_failed": "上流が失敗しました"

Also, put a space after English words as the Spacing rule states:

| Dag Run | Dag実行 | |

[HARDIK-WEB-OSS]

@HARDIK-WEB-OSS Could you please change the following translations as below as common.json?

deferred": "延期済"
"failed": "失敗した"
"backfill": "過去分の再実行"
upstream_failed": "上流が失敗しました"

Also, put a space after English words as the Spacing rule states:

| Dag Run | Dag実行 | |

All terminology and spacing updates are live. Updated deferred → 延期済, failed → 失敗した, backfill → 過去分の再実行, upstream_failed → 上流が失敗しました. Half-width spacing rule applied consistently across all Triggerer and Dag entries. JSON structure verified. Ready for final review

[rsanda]

Thanks Hardik.
LGTM.

[choo121600]

Technically approved from my side.
Since @rsanda has approved it, I think we can merge this 🙌