# Fortra Automate — T063 Legacy `/node/N` Handoff (2026-05-11)

These are the 46 fixable body-content `/node/N` links carried over from the
April scope, organized in the same shape as the May 6 hand-off so they can be
picked up directly.

## Files

- **HANDOFF_t063_2026_05_11.csv** — 46 link edits across 20 pages.
- **HANDOFF_t063_needs_decision_2026_05_11.csv** — 3 items whose `/node/N`
  target is genuinely deleted (404, no redirect, no native resolution). Need
  a client decision on what to replace each with.

## Why these weren't in the May 6 handoff

Two reasons, both verified by spot-check against the live site:

1. **April's automation marked many `NOT-FOUND`** with the comment
   "likely in auto-generated related-content widget" — but inspection shows
   they're in editable body paragraphs (`paragraph--type--text-with-image`,
   `paragraph--type--cta`, accordions). April's locator wasn't smart enough
   to find them.

2. **April's classifier flagged many `/node/N` references as "broken"** —
   meaning no entry in the redirect table. But Drupal natively resolves
   `/node/NID` to the canonical alias through its router, without needing
   a redirect-table row. 27 of the 29 unique "broken" hrefs actually
   resolve to a live canonical URL — those are now in the fixable list
   with the native-resolution target.

## How to use the CSV

Same as May 6 — each row is one link that needs the href swapped in the
admin UI. Columns:

| Column | Meaning |
|---|---|
| **page_url** | Live page where the bad link appears |
| **admin_edit_url** | `/node/NID/edit` |
| **link_text** | Visible text of the link |
| **link_type** | All "Body Content Link" (no CTA bug here) |
| **current_bad_href** | The `/node/N` to replace |
| **replacement_url** | The canonical URL to swap in |
| **notes** | Source of the replacement (redirect table vs. native resolution) and DOM region |

Rows are sorted by `page_url` so all edits for one page group together.
Several pages have 3–6 edits each — efficient to batch:

- `/blog/how-build-automation-scripts-without-code` — 6 links
- `/integrations/microsoft-automation/sharepoint` — 6 links
- `/solutions/robotic-process-automation/bots` — 5 links
- `/blog/automate-boring-stuff-50-processes-you-can-automate` — 4 links

## A heads-up on link-text mismatches

Three rows have link text that no longer matches the destination:

- *"Watch the Webinar"* now points at a use-case page, not a webinar.
- *"Watch the 2 minute video tutorial"* now points at a blog post.
- *"6 Areas Where a Company Can Leverage RPA"* now points at a different blog post.

You said to swap the href and leave the link text alone — these are the rows
where you may want to revisit the text or kill the link entirely.

## Out of scope

Other findings from the re-audit that I did NOT include here:

- **18 CTA button items** with the same `/node/N`/redirect issue — these hit
  the Drupal CTA autocomplete bug and need the manual entity-autocomplete
  workflow that you've used for the 40+ CTAs already done.
- **76 one-hop redirects** in body content — explicitly deferred by April.
- **352 instances** of the main-menu link to
  `/solutions/automation/robotic-process-automation/hr` — one template-level
  fix, not 352 edits.

Full picture is in `SUMMARY.md` in this directory.

## Why I couldn't do these edits myself

Tried, hit a hard block: this session's browser extension can't inject JS or
click into the Drupal admin form (`/node/NID/edit`) — every call returns
"Cannot access a chrome-extension:// URL of different extension". Likely a
conflict with the Drupal admin toolbar's own extension hooks. Read-only
inspection of the admin form works (I can navigate to it, read the structure,
take screenshots), but interactive automation does not.