It seems only stored procedures have dependencies on that table, so you won't break any FK reference by reseeding that ID.
Also, if you generate the script of dbo.sysjobhistory, you'll see it's not even a PK.
CREATE TABLE [dbo].[sysjobhistory](
[instance_id] [int] IDENTITY(1,1) NOT NULL,
[job_id] [uniqueidentifier] NOT NULL,
[step_id] [int] NOT ...
I recommend you to go through dbatools It contains all the Powershell modules required to manage the SQL Server Always On Availability Group.
1.I require that all jobs on the primary server be in sync with those on the secondary server.
For Object syncing, check this package: Sync-DbaAvailabilityGroup run periodically or schedule it.
2.However, I just ...