| File: |
docs/PRD.md |
| Role: |
Auxiliary data |
| Content type: |
text/markdown |
| Description: |
Auxiliary data |
| Class: |
Angell EYE PayPal Payments Pro and Adaptive Payments Library
Process Web site payments using Paypal API |
| Author: |
By Andrew Angell |
| Last change: |
docs: v4.0 prep — PRD revision, 52 plan files, GitHub issues (#285)
* docs: revise PRD based on brainstorming session
Resolves 16 design decisions and codebase-validation findings.
Auto-fallback replaces opt-in passthrough (AC1.3 rewritten, drops
the classic_methods_passthrough config key). WebhookVerifier locked
to PayPal verify-webhook-signature API only. ButtonHelper moves to
the Support namespace. Phase 6 split into Phase 6 (verification +
RC bake) and Phase 7 (release + brand cutover). Resource handler
count corrected 13 -> 14 (13 resources + WebhookVerifier helper).
Mapper count corrected to 30 + FieldMap (DoCaptureMapper duplicate
removed). Phase 0 gains GitHub Actions CI workflow and PHPStan
config as explicit deliverables. PRD copy corrected throughout to
reflect that APIButtonSource is currently empty on main, not the
'AngellEYELLC_Ecom_PHPCatalog' literal that earlier drafts claimed.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: add v4.0 plan-file tree (52 plans + README index)
Builds the iteration-friendly plan/handoff structure under
docs/v4-plans/ matching the 16 decisions baked into the PRD
revision. Each plan file is one focused session's scope of
work; each will map 1:1 to a GitHub issue under the v4.0
milestone (created in a follow-up commit).
Phase breakdown (52 plans):
- Phase 0 (Cleanup & Foundation): 5 plans
- Phase 1 (Core REST Plumbing): 6 plans
- Phase 2 (REST Resource Handlers): 14 plans (one per resource)
- Phase 3 (Legacy Adapter & Upgrade): 13 plans
- Phase 4 (Templates / Samples / Demos / Helper): 6 plans
- Phase 5 (Documentation): 4 plans
- Phase 6 (Verification & RC Bake): 2 plans
- Phase 7 (Release & Brand Cutover): 2 plans
README.md is the navigation index. Each plan file follows
the same structured template: Context, Scope, Files affected,
Acceptance criteria, Verification, References.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: add v4.0 plan-handoff issue template
Mirrors the plan-file template at docs/v4-plans/. Used when
opening follow-up issues mid-flight so they match the existing
pattern (context, scope, files affected, acceptance criteria,
verification, references).
The v4.0 milestone and the 14 phase/scope labels (phase-0..7,
rest, legacy, support, docs, ci, brand) were created via gh CLI
in this same session.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: wire 52 GitHub issue links into v4-plans README + script
The issue-creation script (scripts/create-v4-issues.sh) creates
one GitHub issue per plan file under docs/v4-plans/, applies
phase + scope labels, and assigns the v4.0 milestone. The TSV map
(scripts/v4-issue-map.tsv) records the plan-file → issue-number
correspondence so the README can be regenerated.
Issues created: #286 through #337 (52 total) under milestone v4.0.
README updated with one clickable issue link per row.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
| Date: |
4 days ago |
| Size: |
71,290 bytes |
|
|
|
