docs: add Person to Brief AF to org profile

[santoshkumarradha]

Summary

• add Person to Brief AF to the Agent-Field organization profile's project directory
• describe its identity resolution, verified public-professional research, and cited brief/PDF output in the existing table tone

Why

The public repository is part of the Agent-Field organization but is missing from the organization profile's Built on AgentField list.

User impact

Visitors to the organization page can discover the installable person-intelligence agent alongside the other production-grade AgentField projects.

Validation

• git diff --check
• verified the repository URL and public metadata

[AbirAbbas]

The red cla check here has nothing to do with your CLA or your commit email — the workflow is misconfigured and has never passed in this repo. All 12 pull_request_target runs since 2026-03-09, across four branches and every author, failed identically.

.github/workflows/cla.yml sets remote-organization-name: Agent-Field / remote-repository-name: .github. That flips contributor-assistant onto its remote-storage path, which requires a PERSONAL_ACCESS_TOKEN env var; only GITHUB_TOKEN is supplied, so getPATOctokit() calls setFailed inside getFileContent() — which runs after the allowlist filter but unconditionally, so being on the allowlist never saves you:

##[error]Please add a personal access token as an environment variable for writing signatures in a remote repository/organization as mentioned in the README.md file
##[error]Could not retrieve repository contents. Status: unknown

Those two inputs point at this very repo, so they aren't needed at all. Removing them and bumping contents: read → contents: write (the action then commits cla-signatures.json to main with the default token) is the whole fix. workflow-templates/cla.yml is byte-identical, so the same bug ships to any repo that adopts the template.

The fix has to land on main before it helps: pull_request_target loads the workflow from the base branch, so it can't be fixed from inside a PR, and re-pushing this branch would just reproduce the same failure.

Content side is clean — branch already contains current main (no rebase needed, no conflicts), table row is well-formed, and all 11 project links resolve 200 including person-to-brief-af.

[AbirAbbas]

One-line README addition, links to a public repo. Approved.