feat: SEAM 2 — regime rules as recommendations, the five-knob priors table (#699) by aarontrowbridge · Pull Request #701 · harmoniqs/amicode

aarontrowbridge · 2026-09-01T05:07:59Z

Fixes#699. Part of #679 (the codesign PRD). The Aug-16 campaign core finding becomes recommendations: a committed priors table for the five named calibration knobs (tr_frac, β, y_goal, GLS weighting, min_contrast), keyed by platform family, provenance-stamped with the census (2026-08-31, 12 profiles: 4 spin / 4 transmon / 4 atom) + the public-scale caveat riding every entry, served through the amico_recommend query path (the one recommendation surface — ledger recs keep their cap-to-medium; static priors state confidence explicitly: gls_weighting HIGH from the measurement kinds + PR #36; min_contrast 2.5 HIGH from the #65/#81 + #83/#84 fixture evidence; β and y_goal MEDIUM from the hardware-loop doctrine; tr_frac LOW by design — starting points the flywheel sharpens). The audit (a new amico_recommend action) is F2 sensor: FAILS an off-scope prior without the caveat, PASSES with it, surfaces census staleness. A1 leak guard mechanical: no census-vendor name anywhere (family keying only — and two public-paper vendor designations hand-struck beyond what the guard could catch), no drift-scale/trust-geometry/crossover fields, internal tier unreachable by construction. The dynamic-census contract stated in-schema; regeneration wiring to the freshness cadence = the named follow-up. Evidence chains per value in the table sources. Director gates: 1880 passed + the 3 documented pre-existing env failures, typecheck clean; plugin_exercise end-to-end green by cast run. Overlay untouched.

…us contract (#699)

#699)

…rings (#699)

…#699)

…ough the existing mechanics (#699)

…nternals (#699)

…+ledger priors, audit action lands F2's sensor (#699)

coderabbitai · 2026-09-01T05:08:07Z

Important

🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 09bd711b-9e3c-46e2-b10b-953a6a223eaa

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

…e follow-through on #701) origin/main advanced mid-slice with #701 (SEAM 2 — regime priors): the plugin's amicode_recommend gained the composed query (ledger priors ∪ regime priors via serveRecommendations, platform family scoped from the recorded system), the new audit action (auditRegimePriorApplications — the off-profile sensor with the census-staleness check), the current_census arg, and the four-action description. That body is now in the core VERBATIM (byte-identical to main's plugin text; the two sibling specifiers re-based to ../opencode-plugin/), so both transports serve it: the plugin adapter projects it (behavioral reference — main's own scripts/plugin_exercise.ts passes against the shim), and the MCP server serves it under the bare wire name (recommend). The conflict discipline: rebase resolved opencode-plugin/amicode_tools.ts as the retirement adapter (ours) — main's plugin content lives on through the core; regime_priors.ts/.json, their tests, plugin_exercise.ts, and the packaging list arrived from main untouched (diff vs main on the plugin dir = exactly the four type-fix files from the extraction).

aarontrowbridge · 2026-09-01T05:07:59Z

Fixes#699. Part of #679 (the codesign PRD). The Aug-16 campaign core finding becomes recommendations: a committed priors table for the five named calibration knobs (tr_frac, β, y_goal, GLS weighting, min_contrast), keyed by platform family, provenance-stamped with the census (2026-08-31, 12 profiles: 4 spin / 4 transmon / 4 atom) + the public-scale caveat riding every entry, served through the amico_recommend query path (the one recommendation surface — ledger recs keep their cap-to-medium; static priors state confidence explicitly: gls_weighting HIGH from the measurement kinds + PR #36; min_contrast 2.5 HIGH from the #65/#81 + #83/#84 fixture evidence; β and y_goal MEDIUM from the hardware-loop doctrine; tr_frac LOW by design — starting points the flywheel sharpens). The audit (a new amico_recommend action) is F2 sensor: FAILS an off-scope prior without the caveat, PASSES with it, surfaces census staleness. A1 leak guard mechanical: no census-vendor name anywhere (family keying only — and two public-paper vendor designations hand-struck beyond what the guard could catch), no drift-scale/trust-geometry/crossover fields, internal tier unreachable by construction. The dynamic-census contract stated in-schema; regeneration wiring to the freshness cadence = the named follow-up. Evidence chains per value in the table sources. Director gates: 1880 passed + the 3 documented pre-existing env failures, typecheck clean; plugin_exercise end-to-end green by cast run. Overlay untouched.

…us contract (#699)

#699)

…rings (#699)

…#699)

…ough the existing mechanics (#699)

…nternals (#699)

…+ledger priors, audit action lands F2's sensor (#699)

coderabbitai · 2026-09-01T05:08:07Z

Important

🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 09bd711b-9e3c-46e2-b10b-953a6a223eaa

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

…e follow-through on #701) origin/main advanced mid-slice with #701 (SEAM 2 — regime priors): the plugin's amicode_recommend gained the composed query (ledger priors ∪ regime priors via serveRecommendations, platform family scoped from the recorded system), the new audit action (auditRegimePriorApplications — the off-profile sensor with the census-staleness check), the current_census arg, and the four-action description. That body is now in the core VERBATIM (byte-identical to main's plugin text; the two sibling specifiers re-based to ../opencode-plugin/), so both transports serve it: the plugin adapter projects it (behavioral reference — main's own scripts/plugin_exercise.ts passes against the shim), and the MCP server serves it under the bare wire name (recommend). The conflict discipline: rebase resolved opencode-plugin/amicode_tools.ts as the retirement adapter (ours) — main's plugin content lives on through the core; regime_priors.ts/.json, their tests, plugin_exercise.ts, and the packaging list arrived from main untouched (diff vs main on the plugin dir = exactly the four type-fix files from the extraction).

aarontrowbridge · 2026-09-01T05:07:59Z

Fixes#699. Part of #679 (the codesign PRD). The Aug-16 campaign core finding becomes recommendations: a committed priors table for the five named calibration knobs (tr_frac, β, y_goal, GLS weighting, min_contrast), keyed by platform family, provenance-stamped with the census (2026-08-31, 12 profiles: 4 spin / 4 transmon / 4 atom) + the public-scale caveat riding every entry, served through the amico_recommend query path (the one recommendation surface — ledger recs keep their cap-to-medium; static priors state confidence explicitly: gls_weighting HIGH from the measurement kinds + PR #36; min_contrast 2.5 HIGH from the #65/#81 + #83/#84 fixture evidence; β and y_goal MEDIUM from the hardware-loop doctrine; tr_frac LOW by design — starting points the flywheel sharpens). The audit (a new amico_recommend action) is F2 sensor: FAILS an off-scope prior without the caveat, PASSES with it, surfaces census staleness. A1 leak guard mechanical: no census-vendor name anywhere (family keying only — and two public-paper vendor designations hand-struck beyond what the guard could catch), no drift-scale/trust-geometry/crossover fields, internal tier unreachable by construction. The dynamic-census contract stated in-schema; regeneration wiring to the freshness cadence = the named follow-up. Evidence chains per value in the table sources. Director gates: 1880 passed + the 3 documented pre-existing env failures, typecheck clean; plugin_exercise end-to-end green by cast run. Overlay untouched.

…us contract (#699)

#699)

…rings (#699)

…#699)

…ough the existing mechanics (#699)

…nternals (#699)

…+ledger priors, audit action lands F2's sensor (#699)

coderabbitai · 2026-09-01T05:08:07Z

Important

🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 09bd711b-9e3c-46e2-b10b-953a6a223eaa

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

…e follow-through on #701) origin/main advanced mid-slice with #701 (SEAM 2 — regime priors): the plugin's amicode_recommend gained the composed query (ledger priors ∪ regime priors via serveRecommendations, platform family scoped from the recorded system), the new audit action (auditRegimePriorApplications — the off-profile sensor with the census-staleness check), the current_census arg, and the four-action description. That body is now in the core VERBATIM (byte-identical to main's plugin text; the two sibling specifiers re-based to ../opencode-plugin/), so both transports serve it: the plugin adapter projects it (behavioral reference — main's own scripts/plugin_exercise.ts passes against the shim), and the MCP server serves it under the bare wire name (recommend). The conflict discipline: rebase resolved opencode-plugin/amicode_tools.ts as the retirement adapter (ours) — main's plugin content lives on through the core; regime_priors.ts/.json, their tests, plugin_exercise.ts, and the packaging list arrived from main untouched (diff vs main on the plugin dir = exactly the four type-fix files from the extraction).

aarontrowbridge · 2026-09-01T05:07:59Z

Fixes#699. Part of #679 (the codesign PRD). The Aug-16 campaign core finding becomes recommendations: a committed priors table for the five named calibration knobs (tr_frac, β, y_goal, GLS weighting, min_contrast), keyed by platform family, provenance-stamped with the census (2026-08-31, 12 profiles: 4 spin / 4 transmon / 4 atom) + the public-scale caveat riding every entry, served through the amico_recommend query path (the one recommendation surface — ledger recs keep their cap-to-medium; static priors state confidence explicitly: gls_weighting HIGH from the measurement kinds + PR #36; min_contrast 2.5 HIGH from the #65/#81 + #83/#84 fixture evidence; β and y_goal MEDIUM from the hardware-loop doctrine; tr_frac LOW by design — starting points the flywheel sharpens). The audit (a new amico_recommend action) is F2 sensor: FAILS an off-scope prior without the caveat, PASSES with it, surfaces census staleness. A1 leak guard mechanical: no census-vendor name anywhere (family keying only — and two public-paper vendor designations hand-struck beyond what the guard could catch), no drift-scale/trust-geometry/crossover fields, internal tier unreachable by construction. The dynamic-census contract stated in-schema; regeneration wiring to the freshness cadence = the named follow-up. Evidence chains per value in the table sources. Director gates: 1880 passed + the 3 documented pre-existing env failures, typecheck clean; plugin_exercise end-to-end green by cast run. Overlay untouched.

…us contract (#699)

#699)

…rings (#699)

…#699)

…ough the existing mechanics (#699)

…nternals (#699)

…+ledger priors, audit action lands F2's sensor (#699)

coderabbitai · 2026-09-01T05:08:07Z

Important

🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 09bd711b-9e3c-46e2-b10b-953a6a223eaa

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

…e follow-through on #701) origin/main advanced mid-slice with #701 (SEAM 2 — regime priors): the plugin's amicode_recommend gained the composed query (ledger priors ∪ regime priors via serveRecommendations, platform family scoped from the recorded system), the new audit action (auditRegimePriorApplications — the off-profile sensor with the census-staleness check), the current_census arg, and the four-action description. That body is now in the core VERBATIM (byte-identical to main's plugin text; the two sibling specifiers re-based to ../opencode-plugin/), so both transports serve it: the plugin adapter projects it (behavioral reference — main's own scripts/plugin_exercise.ts passes against the shim), and the MCP server serves it under the bare wire name (recommend). The conflict discipline: rebase resolved opencode-plugin/amicode_tools.ts as the retirement adapter (ours) — main's plugin content lives on through the core; regime_priors.ts/.json, their tests, plugin_exercise.ts, and the packaging list arrived from main untouched (diff vs main on the plugin dir = exactly the four type-fix files from the extraction).

aarontrowbridge · 2026-09-01T05:07:59Z

Fixes#699. Part of #679 (the codesign PRD). The Aug-16 campaign core finding becomes recommendations: a committed priors table for the five named calibration knobs (tr_frac, β, y_goal, GLS weighting, min_contrast), keyed by platform family, provenance-stamped with the census (2026-08-31, 12 profiles: 4 spin / 4 transmon / 4 atom) + the public-scale caveat riding every entry, served through the amico_recommend query path (the one recommendation surface — ledger recs keep their cap-to-medium; static priors state confidence explicitly: gls_weighting HIGH from the measurement kinds + PR #36; min_contrast 2.5 HIGH from the #65/#81 + #83/#84 fixture evidence; β and y_goal MEDIUM from the hardware-loop doctrine; tr_frac LOW by design — starting points the flywheel sharpens). The audit (a new amico_recommend action) is F2 sensor: FAILS an off-scope prior without the caveat, PASSES with it, surfaces census staleness. A1 leak guard mechanical: no census-vendor name anywhere (family keying only — and two public-paper vendor designations hand-struck beyond what the guard could catch), no drift-scale/trust-geometry/crossover fields, internal tier unreachable by construction. The dynamic-census contract stated in-schema; regeneration wiring to the freshness cadence = the named follow-up. Evidence chains per value in the table sources. Director gates: 1880 passed + the 3 documented pre-existing env failures, typecheck clean; plugin_exercise end-to-end green by cast run. Overlay untouched.

…us contract (#699)

#699)

…rings (#699)

…#699)

…ough the existing mechanics (#699)

…nternals (#699)

…+ledger priors, audit action lands F2's sensor (#699)

coderabbitai · 2026-09-01T05:08:07Z

Important

🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 09bd711b-9e3c-46e2-b10b-953a6a223eaa

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

…e follow-through on #701) origin/main advanced mid-slice with #701 (SEAM 2 — regime priors): the plugin's amicode_recommend gained the composed query (ledger priors ∪ regime priors via serveRecommendations, platform family scoped from the recorded system), the new audit action (auditRegimePriorApplications — the off-profile sensor with the census-staleness check), the current_census arg, and the four-action description. That body is now in the core VERBATIM (byte-identical to main's plugin text; the two sibling specifiers re-based to ../opencode-plugin/), so both transports serve it: the plugin adapter projects it (behavioral reference — main's own scripts/plugin_exercise.ts passes against the shim), and the MCP server serves it under the bare wire name (recommend). The conflict discipline: rebase resolved opencode-plugin/amicode_tools.ts as the retirement adapter (ours) — main's plugin content lives on through the core; regime_priors.ts/.json, their tests, plugin_exercise.ts, and the packaging list arrived from main untouched (diff vs main on the plugin dir = exactly the four type-fix files from the extraction).

aarontrowbridge · 2026-09-01T05:07:59Z

Fixes#699. Part of #679 (the codesign PRD). The Aug-16 campaign core finding becomes recommendations: a committed priors table for the five named calibration knobs (tr_frac, β, y_goal, GLS weighting, min_contrast), keyed by platform family, provenance-stamped with the census (2026-08-31, 12 profiles: 4 spin / 4 transmon / 4 atom) + the public-scale caveat riding every entry, served through the amico_recommend query path (the one recommendation surface — ledger recs keep their cap-to-medium; static priors state confidence explicitly: gls_weighting HIGH from the measurement kinds + PR #36; min_contrast 2.5 HIGH from the #65/#81 + #83/#84 fixture evidence; β and y_goal MEDIUM from the hardware-loop doctrine; tr_frac LOW by design — starting points the flywheel sharpens). The audit (a new amico_recommend action) is F2 sensor: FAILS an off-scope prior without the caveat, PASSES with it, surfaces census staleness. A1 leak guard mechanical: no census-vendor name anywhere (family keying only — and two public-paper vendor designations hand-struck beyond what the guard could catch), no drift-scale/trust-geometry/crossover fields, internal tier unreachable by construction. The dynamic-census contract stated in-schema; regeneration wiring to the freshness cadence = the named follow-up. Evidence chains per value in the table sources. Director gates: 1880 passed + the 3 documented pre-existing env failures, typecheck clean; plugin_exercise end-to-end green by cast run. Overlay untouched.

…us contract (#699)

#699)

…rings (#699)

…#699)

…ough the existing mechanics (#699)

…nternals (#699)

…+ledger priors, audit action lands F2's sensor (#699)

coderabbitai · 2026-09-01T05:08:07Z

Important

🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 09bd711b-9e3c-46e2-b10b-953a6a223eaa

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

…e follow-through on #701) origin/main advanced mid-slice with #701 (SEAM 2 — regime priors): the plugin's amicode_recommend gained the composed query (ledger priors ∪ regime priors via serveRecommendations, platform family scoped from the recorded system), the new audit action (auditRegimePriorApplications — the off-profile sensor with the census-staleness check), the current_census arg, and the four-action description. That body is now in the core VERBATIM (byte-identical to main's plugin text; the two sibling specifiers re-based to ../opencode-plugin/), so both transports serve it: the plugin adapter projects it (behavioral reference — main's own scripts/plugin_exercise.ts passes against the shim), and the MCP server serves it under the bare wire name (recommend). The conflict discipline: rebase resolved opencode-plugin/amicode_tools.ts as the retirement adapter (ours) — main's plugin content lives on through the core; regime_priors.ts/.json, their tests, plugin_exercise.ts, and the packaging list arrived from main untouched (diff vs main on the plugin dir = exactly the four type-fix files from the extraction).

aarontrowbridge · 2026-09-01T05:07:59Z

Fixes#699. Part of #679 (the codesign PRD). The Aug-16 campaign core finding becomes recommendations: a committed priors table for the five named calibration knobs (tr_frac, β, y_goal, GLS weighting, min_contrast), keyed by platform family, provenance-stamped with the census (2026-08-31, 12 profiles: 4 spin / 4 transmon / 4 atom) + the public-scale caveat riding every entry, served through the amico_recommend query path (the one recommendation surface — ledger recs keep their cap-to-medium; static priors state confidence explicitly: gls_weighting HIGH from the measurement kinds + PR #36; min_contrast 2.5 HIGH from the #65/#81 + #83/#84 fixture evidence; β and y_goal MEDIUM from the hardware-loop doctrine; tr_frac LOW by design — starting points the flywheel sharpens). The audit (a new amico_recommend action) is F2 sensor: FAILS an off-scope prior without the caveat, PASSES with it, surfaces census staleness. A1 leak guard mechanical: no census-vendor name anywhere (family keying only — and two public-paper vendor designations hand-struck beyond what the guard could catch), no drift-scale/trust-geometry/crossover fields, internal tier unreachable by construction. The dynamic-census contract stated in-schema; regeneration wiring to the freshness cadence = the named follow-up. Evidence chains per value in the table sources. Director gates: 1880 passed + the 3 documented pre-existing env failures, typecheck clean; plugin_exercise end-to-end green by cast run. Overlay untouched.

…us contract (#699)

#699)

…rings (#699)

…#699)

…ough the existing mechanics (#699)

…nternals (#699)

…+ledger priors, audit action lands F2's sensor (#699)

coderabbitai · 2026-09-01T05:08:07Z

Important

🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 09bd711b-9e3c-46e2-b10b-953a6a223eaa

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

…e follow-through on #701) origin/main advanced mid-slice with #701 (SEAM 2 — regime priors): the plugin's amicode_recommend gained the composed query (ledger priors ∪ regime priors via serveRecommendations, platform family scoped from the recorded system), the new audit action (auditRegimePriorApplications — the off-profile sensor with the census-staleness check), the current_census arg, and the four-action description. That body is now in the core VERBATIM (byte-identical to main's plugin text; the two sibling specifiers re-based to ../opencode-plugin/), so both transports serve it: the plugin adapter projects it (behavioral reference — main's own scripts/plugin_exercise.ts passes against the shim), and the MCP server serves it under the bare wire name (recommend). The conflict discipline: rebase resolved opencode-plugin/amicode_tools.ts as the retirement adapter (ours) — main's plugin content lives on through the core; regime_priors.ts/.json, their tests, plugin_exercise.ts, and the packaging list arrived from main untouched (diff vs main on the plugin dir = exactly the four type-fix files from the extraction).

aarontrowbridge · 2026-09-01T05:07:59Z

Fixes#699. Part of #679 (the codesign PRD). The Aug-16 campaign core finding becomes recommendations: a committed priors table for the five named calibration knobs (tr_frac, β, y_goal, GLS weighting, min_contrast), keyed by platform family, provenance-stamped with the census (2026-08-31, 12 profiles: 4 spin / 4 transmon / 4 atom) + the public-scale caveat riding every entry, served through the amico_recommend query path (the one recommendation surface — ledger recs keep their cap-to-medium; static priors state confidence explicitly: gls_weighting HIGH from the measurement kinds + PR #36; min_contrast 2.5 HIGH from the #65/#81 + #83/#84 fixture evidence; β and y_goal MEDIUM from the hardware-loop doctrine; tr_frac LOW by design — starting points the flywheel sharpens). The audit (a new amico_recommend action) is F2 sensor: FAILS an off-scope prior without the caveat, PASSES with it, surfaces census staleness. A1 leak guard mechanical: no census-vendor name anywhere (family keying only — and two public-paper vendor designations hand-struck beyond what the guard could catch), no drift-scale/trust-geometry/crossover fields, internal tier unreachable by construction. The dynamic-census contract stated in-schema; regeneration wiring to the freshness cadence = the named follow-up. Evidence chains per value in the table sources. Director gates: 1880 passed + the 3 documented pre-existing env failures, typecheck clean; plugin_exercise end-to-end green by cast run. Overlay untouched.

…us contract (#699)

#699)

…rings (#699)

…#699)

…ough the existing mechanics (#699)

…nternals (#699)

…+ledger priors, audit action lands F2's sensor (#699)

coderabbitai · 2026-09-01T05:08:07Z

Important

🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 09bd711b-9e3c-46e2-b10b-953a6a223eaa

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

…e follow-through on #701) origin/main advanced mid-slice with #701 (SEAM 2 — regime priors): the plugin's amicode_recommend gained the composed query (ledger priors ∪ regime priors via serveRecommendations, platform family scoped from the recorded system), the new audit action (auditRegimePriorApplications — the off-profile sensor with the census-staleness check), the current_census arg, and the four-action description. That body is now in the core VERBATIM (byte-identical to main's plugin text; the two sibling specifiers re-based to ../opencode-plugin/), so both transports serve it: the plugin adapter projects it (behavioral reference — main's own scripts/plugin_exercise.ts passes against the shim), and the MCP server serves it under the bare wire name (recommend). The conflict discipline: rebase resolved opencode-plugin/amicode_tools.ts as the retirement adapter (ours) — main's plugin content lives on through the core; regime_priors.ts/.json, their tests, plugin_exercise.ts, and the packaging list arrived from main untouched (diff vs main on the plugin dir = exactly the four type-fix files from the extraction).

aarontrowbridge added 10 commits September 1, 2026 00:56

feat(seam2): regime priors table — schema, census stamp, dynamic-cens…
5058a1c
…us contract (#699)

test(seam2): provenance schema validation — malformed provenance fails (
18707a0
#699)

feat(seam2): the five-knob serving selection + composed provenance st…
dd07009
…rings (#699)

feat(seam2): platform→family scoping on the interview's platform axis (…
e12bed9
…#699)

feat(seam2): serving path — regime priors composed with ledger priors (…
3748f3a
…#699)

feat(seam2): audit query — F2's off-profile sensor + census staleness (…
8fc109d
…#699)

feat(seam2): workspace audit — prior-application events read back thr…
d134784
…ough the existing mechanics (#699)

test(seam2): the A1 leak guard — attribution-free table, no profile i…
9e95cf7
…nternals (#699)

feat(seam2): the serving seam — amico_recommend query composes regime…
5534939
…+ledger priors, audit action lands F2's sensor (#699)

test(seam2): A1 import-surface guard + the vsix packaging pin (#699)
ad15465

aarontrowbridge merged commit 6abe71d into mainSep 1, 2026
9 checks passed

aarontrowbridge deleted the 699-seam2-regime-priors branch September 1, 2026 05:12

aarontrowbridge mentioned this pull request Sep 1, 2026
feat(extension): A3 — the MCP tool floor: one amicode_* implementation, two transports (#700) #702
Merged