feat: vendor permission system source

2026-08-28 08:35:57 +00:00 · 2026-08-19 14:35:19 +08:00
parent 198584daf8
commit 410c50a3e5
809 changed files with 157793 additions and 139 deletions
@@ -0,0 +1,33 @@
+---
+issue: 98
+issue_title: "Explore a shared permission frontmatter convention for pi-subagent extensions"
+---
+
+# Retro: #98 — Explore a shared permission frontmatter convention for pi-subagent extensions
+
+## Final Retrospective (2026-05-05T23:35:00Z)
+
+### Session summary
+
+Planned, implemented, and shipped a docs-only change for issue #98.
+Delivered two guide documents (`docs/guides/permission-frontmatter-for-subagent-extensions.md` and `docs/guides/upstream-issue-template.md`) plus linking from `README.md` and `docs/architecture/target-architecture.md`.
+Released as v5.3.1 with no rework or corrections.
+
+### Observations
+
+#### What went well
+
+- All four prerequisites (#78, #29, #96, #97) were verified closed in a single parallel `gh issue view` call — efficient context gathering.
+- Existing docs (`docs/subagent-integration.md`, `docs/event-api.md`) were read before writing the guide, so content was grounded in actual implementation rather than invented.
+- The three-step build plan mapped 1:1 to commits with no deviations.
+- CI passed on first push; release-please PR was `MERGEABLE`/`CLEAN` and merged without issues.
+
+#### What caused friction (agent side)
+
+- None observed.
+  The issue was well-scoped, all prerequisites were landed, and the deliverable was unambiguous documentation.
+
+#### What caused friction (user side)
+
+- None observed.
+  The issue body provided clear tasks, explicit prerequisites, and no ambiguous design choices.