NJ-Kit 2.3.1

NJ-Kit 2.3.1

Still 27 plugin skills (44 with the kit installer).

Evidence names are Arabic (nj-qa, nj-jira)

Every screenshot and video is named <المشكلة>-<الخدمة>-<التاريخ>-<الوقت>: a short specific Arabic phrase for the defect, the service's Arabic portal name, YYYY-MM-DD, then HH.MM in 24 hours (Windows has no :). At most 150 characters, -2 for a repeat in the same minute, no English except a ticket code such as PROJ-5494 after the issue.

• New nj-qa/scripts/evidence_name.py makes the name (CLI and import) and checks names (--check).
• nj_qa.py report-check and preview-check refuse any other picture or video name. A run from before the rule sets NJQA_LEGACY_EVIDENCE=1 and keeps its old names.
• nj-jira SKILL.md and references/bug-template.md carry the same rule for Bug evidence.
• Forward only: existing files are never renamed.

nj-qa

A blocked or cannot-test note can carry block_cause (data, system or tool). The review check refuses any other value, and refuses it on any other verdict.

agent-halo and nj-chart

Both arrived in 2.3.0. They are unchanged in 2.3.1 and now appear in the website's skill list, which was missing them:

• agent-halo: a coloured border and the agent's type at the top of every browser window an agent opens. Cosmetic; screenshots and page text never see it.
• nj-chart: charts, dashboards and KPI rows that read at a glance, in Arabic or English, light or dark, on Microsoft's Flint chart engine (MIT).

Website

The grouped skill list, its counts and llms.txt are now generated from the plugin's SKILL.md files (site/_build/build.py), so they cannot go stale. The build fails when a plugin skill has no group or no Arabic line, when the kit list differs from nj-kit/bundled, or when a page states a different skill count. CI runs build.py --check. A stale "23 installed by the plugin" now reads 27. The site uses system fonts only.

Release gate

python scripts/publish-check.py reports 0 hits: no credentials, no private project data, no machine paths, no font files.