Browser editing and verification

Use these rules whenever the task changes LinkedIn.

Preflight

• Use the authenticated browser session supplied by the user.
• Confirm the visible account identity before editing.
• Keep one controlled LinkedIn session when possible.
• Read the current field before opening its editor.
• Keep secrets, cookies, session data, and private browser paths out of logs and reports.

Reliable field replacement

LinkedIn forms often use dynamic dialogs and contenteditable fields. A tool may report success while the UI appends, truncates, or delays the text.

For each field:

1. Focus it and select the complete existing value.
2. Clear it, then insert the replacement once.
3. Read the value back through the strongest available surface: form value, accessible state, rendered text, or direct visual inspection.
4. Compare the read-back value with the intended text.
5. Save only after they match.

If a replacement appears twice, stop before saving. Clear the field and insert one copy.

Saved-state proof

After Save:

1. Wait for the dialog to close and the profile to finish rendering.
2. Reload or reopen the section when the result is ambiguous.
3. Verify the exact text, dates, links, ordering, and visibility on the saved profile.
4. Inspect images directly for crop and quality.

Report an unverified state accurately. A click acknowledgement, browser-tool response, or modal close is insufficient evidence.

Recovery

• Re-read the current page after every browser or tool error.
• Use a fresh control session only when the existing session is genuinely unavailable and the user has authorized the alternative.
• Keep a paste-ready draft when browser control fails.
• Stop and ask the user to complete reauthentication, CAPTCHA, identity, payment, or legal prompts.
• Avoid repeated blind retries. State the exact failed step and preserve completed work.