[Foundry] Link pushed actors to journal backstory #157

New issue

Open

opened 2026-07-15 22:04:25 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-07-15 22:04:25 +00:00

Contributor

Motivation/Context

Live push v1 (#150, #152, #154, #156) puts backstory only in the actor's biography field, deliberately deferring full journal-based backstory to Phase 3 per the live-push investigation (2026-07-15, §4.2: "Live push v1 should put backstory in the actor biography only and leave journals to #13"). Once #13 (journal_to_entry, v4.3.0) lands full lore-entry-to-Foundry-journal sync, pushed actors should reference that journal page instead of duplicating backstory prose in the biography field, so a GM reading an NPC in Foundry gets the same rich content as the wiki article rather than a stale biography snapshot from whenever it was last pushed.

Approach

When both a foundry_links (#146) actor link and a foundry_links journal link (#13, once it exists) are present for the same source LoreEntry, wire the pushed actor to reference the corresponding JournalEntry page — e.g. actor biography becomes a short summary plus a link/reference to the full journal page, rather than the full backstory text duplicated into the actor. Reuses #13's journal_to_entry output and #146's mapping table; no new document-mapping mechanism is needed, this issue is purely the cross-linking behavior.

Dependencies

Hard dependency: #13 (journal_to_entry, v4.3.0) — nothing to link to until journal push exists.
Hard dependency: #146 (foundry_links) — needed to look up both the actor link and the journal link for the same source entry.
Builds on the live-push actor-creation path from #148/#150/#152 (v4.4.0) — actors created before this issue lands should be handled gracefully (either left as-is or backfilled on next push).

Out of scope

Building journal_to_entry itself (that's #13's job).
Any UI changes beyond what's needed to reflect the linked-journal state (no new GM-facing controls anticipated).
Retroactively migrating previously pushed actors' biography text into journal references (out of scope unless trivial as part of a normal "push update", #156).

Acceptance criteria

Once both an actor and a journal exist for the same LoreEntry (via foundry_links), pushing again links the actor to the journal page rather than duplicating full backstory into the actor biography.
Actors pushed before a journal exists continue to work correctly (graceful degradation, no errors).
Verified against the real Foundry test instance: actor biography references/links to the journal page, and the journal page opens correctly from Foundry's UI.

## Motivation/Context Live push v1 (#150, #152, #154, #156) puts backstory only in the actor's biography field, deliberately deferring full journal-based backstory to Phase 3 per the live-push investigation (2026-07-15, §4.2: "Live push v1 should put backstory in the actor biography only and leave journals to #13"). Once #13 (`journal_to_entry`, v4.3.0) lands full lore-entry-to-Foundry-journal sync, pushed actors should reference that journal page instead of duplicating backstory prose in the biography field, so a GM reading an NPC in Foundry gets the same rich content as the wiki article rather than a stale biography snapshot from whenever it was last pushed. ## Approach When both a `foundry_links` (#146) actor link and a `foundry_links` journal link (#13, once it exists) are present for the same source `LoreEntry`, wire the pushed actor to reference the corresponding `JournalEntry` page — e.g. actor biography becomes a short summary plus a link/reference to the full journal page, rather than the full backstory text duplicated into the actor. Reuses #13's `journal_to_entry` output and #146's mapping table; no new document-mapping mechanism is needed, this issue is purely the cross-linking behavior. ## Dependencies - Hard dependency: #13 (`journal_to_entry`, v4.3.0) — nothing to link to until journal push exists. - Hard dependency: #146 (`foundry_links`) — needed to look up both the actor link and the journal link for the same source entry. - Builds on the live-push actor-creation path from #148/#150/#152 (v4.4.0) — actors created before this issue lands should be handled gracefully (either left as-is or backfilled on next push). ## Out of scope - Building `journal_to_entry` itself (that's #13's job). - Any UI changes beyond what's needed to reflect the linked-journal state (no new GM-facing controls anticipated). - Retroactively migrating previously pushed actors' biography text into journal references (out of scope unless trivial as part of a normal "push update", #156). ## Acceptance criteria - Once both an actor and a journal exist for the same `LoreEntry` (via `foundry_links`), pushing again links the actor to the journal page rather than duplicating full backstory into the actor biography. - Actors pushed before a journal exists continue to work correctly (graceful degradation, no errors). - Verified against the real Foundry test instance: actor biography references/links to the journal page, and the journal page opens correctly from Foundry's UI.

claude-bot added this to the v5.3.0 - FoundryVTT Phase 3: Lore Sync & Deeper Pulls milestone

2026-07-15 22:04:28 +00:00

claude-bot added the

backend

enhancement

labels

2026-07-15 22:04:29 +00:00

claude-bot referenced this issue

2026-09-11 00:02:30 +00:00

[UX] Wiki redesign — design record #593