Conflict Ledger and attention rebalancing scaffolds

[Kot141078]

Summary

Adds a conflict-governance layer for the Ester clean-code skeleton.

This PR introduces:

• Conflict Ledger for volition-policy collisions
• review packets for repeated conflicts
• evidence-based resolution as review state
• attention rebalancing scaffolds
• dream/reflection conflict bridge helpers
• dream candidate scoring/seam helpers
• observe-only action/reflection integration hooks
• focused tests for redaction, grouping, provenance, and safety behavior

Safety posture

This PR is designed to be non-authorizing by default.

Key invariants:

• Conflict Ledger records conflicts; it does not authorize actions.
• Evidence resolution is review-only.
• Attention rebalancing is feature-flag gated and defaults off.
• Runtime integration is observe-only / default-off.
• No live provider, Telegram, SYNAPS, oracle, or web behavior is expanded.
• No raw prompts, raw user text, runtime memory, payloads, credentials, or local private state are included.

Validation

Validation performed before PR:

• compile checks passed
• focused test suite passed
• privacy/security gate passed
• committed files are source code and focused tests only
• commits are GPG-signed

Review focus

Please review:

1. Conflict Ledger persistence and redaction behavior.
2. Evidence-resolution semantics.
3. Attention rebalancing default-off behavior.
4. Observe-only action/reflection integration hooks.
5. Runtime provenance metadata and review packet summaries.
6. Focused tests and synthetic redaction sentinels.

Not included

This PR does not include:

• runtime memory/state
• payload dumps
• environment files
• credentials or tokens
• logs or journals
• release/tag changes
• merge to main

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.