docs: permit Jira/EAI ticket IDs in branches, commits, and comments (#110)

* docs: permit Jira/EAI ticket IDs in branches, commits, and comments

The team decided bare Jira/EAI-style ticket IDs (e.g. EAI-1234) are
fine to use in branch names, commit messages, and code/doc comments.
Update the OSS contribution leak-scan guidance to stop flagging them,
while still treating links to internal tracking systems as a leak.

Signed-off-by: Roman Inflianskas <Roman.Inflianskas@amd.com>

* docs: widen ticket-ID permission scope, restore jira leak-scan keyword

- match the bare Jira/EAI ticket ID exemption to the same enforcement
  scope as the rest of the content-restriction rule, instead of a
  narrower explicit surface list
- keep 'jira' in the leak-scan keyword pattern; only ticket-[0-9]+
  needed dropping to stop flagging bare ticket IDs like EAI-1234,
  and jira links to internal tracking hosts should still be caught

Signed-off-by: Roman Inflianskas <Roman.Inflianskas@amd.com>

---------

Signed-off-by: Roman Inflianskas <Roman.Inflianskas@amd.com>

Author: rominf

AGENTS.md

@@ -55,15 +55,16 @@ the full range on push (`verify-commits`), and a blocking CI gate
 Content restrictions for upstream surfaces:
 
 - do not include internal/proprietary names, aliases, URLs, hostnames, gateways, cluster names, or registry paths
-- do not include internal ticket identifiers, links to internal tracking systems, or unrelated internal usernames
+- do not include links to internal tracking systems or unrelated internal usernames
+- bare Jira/EAI-style ticket IDs (e.g. `EAI-1234`) are permitted anywhere this rule applies; do not flag them
 - apply this rule to PR titles/bodies, issue text, comments, review replies, commit messages, branch names, code comments, fixtures, and logs
 
 Use neutral external framing (for example: "backend" or "gateway") rather than internal or vendor-specific ownership phrasing.
 
 Leak scan before each upstream push/PR/comment batch:
 
 ```bash
-INTERNAL_KEYWORDS_PATTERN='internal|confidential|proprietary|private|ticket-[0-9]+|jira|confluence|\.corp|\.internal'
+INTERNAL_KEYWORDS_PATTERN='internal|confidential|proprietary|private|jira|confluence|\.corp|\.internal'
 git diff <upstream-base>..HEAD \
   | grep -inE "$INTERNAL_KEYWORDS_PATTERN" \
   && echo "REVIEW each hit" || echo "diff clean"
@@ -104,7 +105,7 @@ grep -rn "^<<<<<<<\|^=======\|^>>>>>>>" .
 For leak scans, use upstream base `origin/main` (or upstream default branch if different):
 
 ```bash
-INTERNAL_KEYWORDS_PATTERN='internal|confidential|proprietary|private|ticket-[0-9]+|jira|confluence|\.corp|\.internal'
+INTERNAL_KEYWORDS_PATTERN='internal|confidential|proprietary|private|jira|confluence|\.corp|\.internal'
 git diff origin/main..HEAD \
   | grep -inE "$INTERNAL_KEYWORDS_PATTERN" \
   && echo "REVIEW each hit" || echo "diff clean"