Activity Manifest Readability — Step 4: Implementation Summary

Stage 1 - Scannable shared paths

• Changes:

  • Put each non-public-key manifest path in a dedicated block line beneath its status and role.

  • Preserved inline public-key presentation and existing rename/signature context.

• Verification:

  • PHP syntax checks for the shared partial and smoke test passed.

  • php tests/run.php LocalAppSmokeTest passed.

• Notes:

  • Stage 2 will remove only activity-view duplicate source/signature listings.

Stage 2 - Single activity commit listing

• Changes:

  • Show the existing source/signature metadata in Classic and Forte activity only when no commit-file manifest is available.

  • Put the activity item's commit hash at the top of its manifest, immediately below the manifest divider and before the file list.

  • Leave post-page source metadata unchanged.

• Verification:

  • PHP syntax checks passed for the shared manifest and both activity consumers.

  • php tests/run.php LocalAppSmokeTest passed.

  • Git-backed Classic and Forte renders verify the commit is retained and the duplicate Source: block is absent; non-Git Classic and Forte renders retain signature fallback metadata.

• Notes:

  • The manifest continues to be optional: activity from repositories without Git commit data retains the original source metadata presentation.