Repository navigation
Removed Faculty Member Continues to Appear in Published Faculty Directory After Full Site Publish #804
Description
Activity
@vijaya-boddipudi Need steps to reproduce.
- changed the title
[-]8.1.5 Removed Faculty Member Continues to Appear in Published Faculty Directory After Full Site Publish[/-][+]Removed Faculty Member Continues to Appear in Published Faculty Directory After Full Site Publish[/+]on Jun 23, 2026 @natechadwick-intsof Not able to reproduce this issue. Customer is still experiencing the problem. we need to investigate further.
14 remaining items
Status update — all engineering slices landed
Verified slice state as of 2026-08-08:
Slice Issue PR Merged Status 1 - Inventory #2336 #2336 yes closed 2 - Live/customer repro #2334 #2356 yes closed 3 - Minimal product/ops fix #2335 #2357 yes closed Residual verify ops path #2358 n/a open grok operator workflow Disposition (recap)
Slice 2 classification: primary H1 (misunderstood model). The
"stale faculty member after publish" symptom is consistent with how
the Directory widget auto-queries JCR — it is not a product
full-publish defect absent a customer/snapshot reproduction. No
Directory query change was made.Slice 3 fix landed as a docs-only ops runbook (PR #2357)
describing how operators should reconcile the model expectation
(re-associate the role before publish, or use full-publish+incremental
deltas) rather than expecting an algorithmic re-bind.Close gate
This parent stays open until the live-verify residual #2358 runs:
"Customer/snapshot: person non-matching + publish HTML omits name; then
close #804". That residual is owned by the groknight-issue-prs
workflow (requires customer / snapshot env access), so a Kilo
worktree cannot run it.Status update — all engineering slices landed
Verified slice state as of 2026-08-08:
Slice Issue PR Merged Status 1 - Inventory #2336 #2336 yes closed 2 - Live/customer repro #2334 #2356 yes closed 3 - Minimal product/ops fix #2335 #2357 yes closed Residual verify ops path #2358 n/a open grok operator workflow Disposition (recap)
Slice 2 classification: primary H1 (misunderstood model). The
"stale faculty member after publish" symptom is consistent with how
the Directory widget auto-queries JCR — it is not a product
full-publish defect absent a customer/snapshot reproduction. No
Directory query change was made.Slice 3 fix landed as a docs-only ops runbook (PR #2357)
describing how operators should reconcile the model expectation
(re-associate the role before publish, or use full-publish+incremental
deltas) rather than expecting an algorithmic re-bind.Close gate
This parent stays open until the live-verify residual #2358 runs:
"Customer/snapshot: person non-matching + publish HTML omits name; then
close #804". That residual is owned by the groknight-issue-prs
workflow (requires customer / snapshot env access), so a Kilo
worktree cannot run it.Reconcile: Classification and ops-runbook slices are done on
origin/main. Parent stays open.Slice Issue Status PR Notes Updated Inventory publish/cache/stale-query #2336 done #2336 MERGED; issue CLOSED 2026-09-12 Live/customer-env classification #2334 done #2356 MERGED 2026-08-08; issue CLOSED (was stale pr_opened)2026-09-12 Ops runbook (H1) #2335 done #2357 MERGED 2026-08-08; issue CLOSED (was stale pr_opened)2026-09-12 Residual verify ops path #2358 open — Customer/snapshot evidence still required; do not close #804 2026-09-12 C1/C4 fail: open residual #2358. No OPEN covering PR. QA: Failed = 0.
Co-Authored by Grok Build 1.0.25 using grok-4.6 with agent night-issue-prs-reconcile.
Reconcile: Agent progress — classification + ops-runbook slices already shipped; verification residual remains.
Slice Issue Status PR Notes Updated 2 Live/customer-env repro #2334 done #2356 MERGED 2026-08-08; issue CLOSED (body still said pr_opened)2026-09-12 3 Minimal product/ops fix #2335 done #2357 MERGED 2026-08-08; docs-only H1 runbook; issue CLOSED 2026-09-12 Residual verify ops path #2358 open — Customer/snapshot verify still required; agent-unsafe host-install. Do not close #804 until #2358 acceptance is met. 2026-09-12 C1: #804 stays open (open child #2358). No OPEN covering PR.
Co-Authored by Grok Build 1.0.25 using grok-4.6 with agent night-issue-prs-reconcile.
night-issue-prs 2026-09-22: #2358 left blocked. This agent session has no customer snapshot or customer-like publish environment, and the issue forbids inventing Directory query changes unless verification proves an H6/H8 product residual. Parent #804 is already closed; operator procedure shipped in product-docs via PR #4665. Acceptance (pub log + HTML or customer confirmation) still needs a human with that environment. No PR.
Co-Authored by Grok Build 1.0.40 using grok-4.6 with agent night-issue-prs.
night-issue-prs 2026-09-25: #2358 rechecked. Still blocked — no customer or snapshot environment in this session, and the issue forbids inventing Faculty Directory query changes without H6/H8 evidence. Parent #804 is already closed. Operator procedure remains product-docs (PR #4665 /
product-docs/8.2/admin/faculty-directory.md). Acceptance (pub log + published HTML or customer confirmation) needs a human with the customer env. No PR opened. Issue left open and unassigned.Co-Authored by Grok Build 1.0.41 using grok-4.6 with agent night-issue-prs.
night-issue-prs 2026-09-26: #2358 remains blocked. No customer/snapshot env in the agent session, so the ops-path verification (pub log + HTML or customer confirmation) was not run. No product query change. Issue left open and unassigned.
Co-Authored by Grok Build 1.0.41 using grok-4.6 with agent night-issue-prs.
Describe the bug
A faculty member who has been removed from the Faculty Directory asset continues to appear on the published website after a full site publish.
To Reproduce
Steps to reproduce the behaviour:
Observed Result:
The faculty member "Amy Kern" is still displayed on the published Faculty Directory page even though the staff member has been removed from the corresponding asset and a full site publish has been completed.
Expected behaviour
Once a faculty member is removed from the Faculty Directory asset and the site is republished, the faculty member should no longer appear on the published website.
Versions Affected
Screenshots
Additional context
Agent progress (night-issue-prs)