ldraney/westside-app
1
0
Fork 0
Code Issues 17 Pull requests Projects Releases Packages Wiki Activity Actions

docs: populate WS-S26 Prospect user story on westside-basketball project page #251

New issue
Closed
opened 2026-04-14 15:55:47 +00:00 by forgejo_admin · 1 comment
forgejo_admin commented 2026-04-14 15:55:47 +00:00
Contributor
Copy link

Type

Feature

Lineage

Surfaced by retroactive scope review of board item #1010 (Forgejo #249). Reviewer note: review-1010-2026-04-14. Traceability convention: feedback_traceability_triangle.md.

Repo

pal-e-docs (project page content only, no westside-app code change)

User Story

As a reviewer validating a westside ticket with story:WS-S26
I want the WS-S26 story defined on project-westside-basketball#prospect
So that I can actually verify the ticket scope traces to a real user need

Context

story:WS-S26 is referenced on many board items (landing-site, public pages, #1010 #405 #354 #382 #588, etc.) but the Prospect subsection on the project page has zero content blocks — the label points to empty content. Every ticket is supposed to trace to a user story per feedback_traceability_triangle.md; right now one of the most-used westside labels traces nowhere.

Reviewer's suggested story copy: "As a prospective family, I want public-site contact links that reach a real inbox so I can inquire about the program."

File Targets

Files to update (via pal-e-docs MCP, NOT filesystem):

  • project-westside-basketball note, section anchor prospect — add a list/table block of prospect user stories

Files NOT to touch:

  • Any code repo (this is docs-only)
  • Other stories sections (superadmin, admin, coach, parent, player)

Acceptance Criteria

  • get_section(slug="project-westside-basketball", anchor_id="prospect") returns a populated stories block containing WS-S26
  • WS-S26 story text is a complete "As a / I want / So that" statement covering public-site contact flow
  • Block links to reference_westside_email.md
  • Pattern/format matches existing stories-* subsections on the same page
  • Only the prospect anchor is modified; other sections untouched

Test Expectations

  • mcp__pal-e-docs__get_section(slug="project-westside-basketball", anchor_id="prospect") returns a populated stories block containing WS-S26
  • Story text matches the reviewer-suggested copy (or clearer equivalent)
  • Block links to reference_westside_email.md
  • No code tests; doc change only

Constraints

  • Use mcp__pal-e-docs__create_block or update_block under anchor prospect — do NOT rewrite the whole project page
  • Keep the format consistent with other stories-* subsections (inspect stories-parent or stories-admin for pattern)
  • Only add WS-S26; additional prospect stories (tryouts inquiry, sponsorship) are out of scope and belong in follow-up tickets

Checklist

  • PR / doc update opened against pal-e-docs
  • Prospect section contains WS-S26 with story text
  • Links to reference_westside_email.md included
  • No edits outside the prospect anchor
  • Board item advanced through validation per feedback_validate_before_done.md

Related

  • Discovered in: review-1010-2026-04-14
  • Convention: feedback_traceability_triangle.md
  • Label usage: #405, #354, #355, #382, #588, #1010 all reference story:WS-S26
### Type Feature ### Lineage Surfaced by retroactive scope review of board item #1010 (Forgejo #249). Reviewer note: `review-1010-2026-04-14`. Traceability convention: `feedback_traceability_triangle.md`. ### Repo pal-e-docs (project page content only, no westside-app code change) ### User Story As a reviewer validating a westside ticket with `story:WS-S26` I want the WS-S26 story defined on `project-westside-basketball#prospect` So that I can actually verify the ticket scope traces to a real user need ### Context `story:WS-S26` is referenced on many board items (landing-site, public pages, #1010 #405 #354 #382 #588, etc.) but the Prospect subsection on the project page has zero content blocks — the label points to empty content. Every ticket is supposed to trace to a user story per `feedback_traceability_triangle.md`; right now one of the most-used westside labels traces nowhere. Reviewer's suggested story copy: *"As a prospective family, I want public-site contact links that reach a real inbox so I can inquire about the program."* ### File Targets Files to update (via pal-e-docs MCP, NOT filesystem): - `project-westside-basketball` note, section anchor `prospect` — add a list/table block of prospect user stories Files NOT to touch: - Any code repo (this is docs-only) - Other stories sections (superadmin, admin, coach, parent, player) ### Acceptance Criteria - [ ] `get_section(slug="project-westside-basketball", anchor_id="prospect")` returns a populated stories block containing `WS-S26` - [ ] WS-S26 story text is a complete "As a / I want / So that" statement covering public-site contact flow - [ ] Block links to `reference_westside_email.md` - [ ] Pattern/format matches existing `stories-*` subsections on the same page - [ ] Only the `prospect` anchor is modified; other sections untouched ### Test Expectations - [ ] `mcp__pal-e-docs__get_section(slug="project-westside-basketball", anchor_id="prospect")` returns a populated stories block containing `WS-S26` - [ ] Story text matches the reviewer-suggested copy (or clearer equivalent) - [ ] Block links to `reference_westside_email.md` - No code tests; doc change only ### Constraints - Use `mcp__pal-e-docs__create_block` or `update_block` under anchor `prospect` — do NOT rewrite the whole project page - Keep the format consistent with other `stories-*` subsections (inspect `stories-parent` or `stories-admin` for pattern) - Only add WS-S26; additional prospect stories (tryouts inquiry, sponsorship) are out of scope and belong in follow-up tickets ### Checklist - [ ] PR / doc update opened against pal-e-docs - [ ] Prospect section contains WS-S26 with story text - [ ] Links to `reference_westside_email.md` included - [ ] No edits outside the `prospect` anchor - [ ] Board item advanced through validation per `feedback_validate_before_done.md` ### Related - Discovered in: `review-1010-2026-04-14` - Convention: `feedback_traceability_triangle.md` - Label usage: #405, #354, #355, #382, #588, #1010 all reference `story:WS-S26`
forgejo_admin commented 2026-04-14 15:58:14 +00:00
Author
Contributor
Copy link

Scope Review: READY

Review note: review-1011-2026-04-14

Scope is tight and template-complete. File target verified: project-westside-basketball anchor prospect exists with zero content blocks, ready to populate. Pattern source stories-parent confirmed as format template. Single MCP create_block call, well under the 5-minute rule.

Traceability notes:

  • story:WS-S26 is self-referential on this ticket — the gap IS the scope. Acceptable.
  • arch:landing-site backing note still absent but tracked in sibling #1012. Not a blocker.

Minor implementation guidance (not a body fix): the AC referencing reference_westside_email.md points to a memory file, not a pal-e-docs note. Render it as a plain inline mention matching the stories-parent pattern, not as an HTML link.

Advance board item #1011 from backlog → todo.

## Scope Review: READY Review note: `review-1011-2026-04-14` Scope is tight and template-complete. File target verified: `project-westside-basketball` anchor `prospect` exists with zero content blocks, ready to populate. Pattern source `stories-parent` confirmed as format template. Single MCP `create_block` call, well under the 5-minute rule. Traceability notes: - `story:WS-S26` is self-referential on this ticket — the gap IS the scope. Acceptable. - `arch:landing-site` backing note still absent but tracked in sibling #1012. Not a blocker. Minor implementation guidance (not a body fix): the AC referencing `reference_westside_email.md` points to a memory file, not a pal-e-docs note. Render it as a plain inline mention matching the `stories-parent` pattern, not as an HTML link. Advance board item #1011 from `backlog` → `todo`.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
251-docs-populate-ws-s26-prospect-user-story
252-docs-create-arch-landing-site-architectu
236-fix-jersey-image-urls
hotfix-jersey-image-urls
232-improve-public-roster-page-accuracy-and
180-fix-jersey-deadline
142-validate-coach-login-and-read-only-roste
139-fix-admin-dashboard-stats-showing-all-ze
129-validate-girls-draft-board-coach-login-a
204-auto-tag-update
deploy-update-image-tag
110-fix-harbor-push-target
No results found.
Labels
Clear labels   
domain:backend

   
domain:devops

   
domain:frontend
No labels
domain:backend
domain:devops
domain:frontend
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ldraney/westside-app#251
No description provided.