Skip to content

docs: document fork patches 2 and 3 in PATCHES.md - #306

Closed
Cryptoom wants to merge 6 commits into
trypostit:mainfrom
Cryptoom:fix/mvf-patches-doc-nachtrag
Closed

docs: document fork patches 2 and 3 in PATCHES.md#306
Cryptoom wants to merge 6 commits into
trypostit:mainfrom
Cryptoom:fix/mvf-patches-doc-nachtrag

Conversation

@Cryptoom

Copy link
Copy Markdown

Summary

  • PR Workspace wise social account enable/disable #2 (madevisible brand token reskin, resources/css/app.css) and PR Instagram Business Login fails with "400 Session Invalid" due to OAuth popup #3 (sidebar referral/Discord removal, resources/js/components/AppSidebar.vue) were fork deviations from upstream files, but never recorded in PATCHES.md.
  • Without an entry, a future git merge upstream/main could overwrite these two patches silently, since a conflict-free merge on the same lines just takes the upstream version.
  • Added Patch 2 and Patch 3 entries following the existing Patch 1 format: files touched, marker strings for post-merge verification, and the specific break condition for each.

Test plan

  • Verified no code changes outside PATCHES.md
  • Verified marker strings against actual diffs (git show 32fa724, git show 10ed0ad)
  • Checked for em-dashes/en-dashes in the new text (none)

Infrastructure prep, no active patch yet. Same pattern as
Cryptoom/whatsapp-mcp and Cryptoom/telegram-mcp forks.
* feat(mcp): add update-workspace-tool for brand settings

GetWorkspaceTool is read-only; there was no API or MCP path to write a
workspace's brand settings (name, colors, voice traits, font, image
style, content language). Adds UpdateWorkspaceTool mirroring
UpdateWorkspaceRequest's validation with PATCH semantics (only passed
fields change), gated on the same 'update' ability as the settings UI.

Registered as fork Patch 1 in PATCHES.md.

* fix(mcp): coerce brand_voice_traits and rename misleading test

UpdateWorkspaceTool validated brand_voice_traits against the enum but
never ran BrandVoiceTrait::coerce(), so an update could store an
incoherent set (e.g. both formal and casual). This is the first
programmatic/unattended MCP write path, so coerce it here before the
values land in the update payload.

Also rename a test whose name implied a cross-workspace injection
vector that the tool schema does not expose. The tool always resolves
the caller's current workspace; there is no workspace_id parameter to
attack.
…oyed

is_aigc already exists upstream for TikTok (Composer checkbox, meta
rules, publisher, MCP tool) - no patch needed. Also corrects the
stale note about the server checkout still running against upstream;
it now runs against Cryptoom/trypost since Patch 1.
* feat(design): madevisible brand token concept for app.css

Concept-only reskin: swaps the upstream Gumroad-style warm cream +
violet identity for madevisible.io brand tokens (deep teal primary,
navy text, gold accent, soft tinted shadows instead of hard offset
shadows, Geist font stack instead of Figtree/Instrument Serif).
Not pushed, local concept branch only.

* fix(design): darken chart-3 gold for WCAG 3:1 UI-component contrast

Review Round 1 (PR #2) flagged --chart-3 (#c99a5c, same hue as --accent)
against --background (#fbf7f1) at 2.38:1, below the 3:1 threshold for
isolated/meaningful data elements. Darkened to #a67c3f (~3.6:1).
Olli asked to remove the "Earn 30% referral" and "Discord community"
bottom-nav items. Also drops the now-unused IconGift/IconBrandDiscord
imports. Docs link and IconAffiliate (used elsewhere) untouched.
Patch 2 (madevisible brand token reskin, PR #2) and Patch 3 (sidebar
referral/Discord removal, PR #3) modify upstream files but were not
captured in PATCHES.md. A future upstream merge could silently
overwrite them without conflict. Add marker strings and break
conditions for both, following the existing Patch 1 format.
@Cryptoom

Copy link
Copy Markdown
Author

Wrong target repo — this is fork-internal documentation, not meant for upstream. Closing, opening against Cryptoom/trypost instead.

@Cryptoom Cryptoom closed this Aug 28, 2026
@Cryptoom
Cryptoom deleted the fix/mvf-patches-doc-nachtrag branch August 28, 2026 04:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant